Laides and Gentelmen! It my pleasure to present to you the next level in the Linux desktop! MATERIAL SHELL!!!

https://github.com/PapyElGringo/...

Demo video: https://i.imgur.com/2UVZTnk.mp4

!rant
A rather long(it's 8 hrs long to be precise) story

So I just finished an amazing homework assignment. The goal was to open a new shell on Linux using a C program. We were asked to follow instructions from http://phrack.org/issues/49/14.html . However the instructions given were for 32 bit processors and we had to do same for 64 bit machines. In a nutshell we had to write a 64 bit shell code and use buffer-overflow technique to change the return address if the function to our shell code.

I was able to write my own shellcode within 1hr and was able to confirm that it's working by compiling with nasm and all. Also the "show-off-dev" inside me told me to execute "/bin/bash" instead of "/bin/sh"(which everyone else was going to do). After my assembly code was properly executing shellcode, I was excited to put it in my C code.
For that, I needed opcodes of assembly code in a string. Following again the "show-off-dev" inside me, I wrote a shell script which would extract the exact opcodes out of objdump output. After this I put it in my C code, call my friend and tell him that "hell yeah bro, I did it. Pretty sure sir is gonna give me full marks etc etc etc". I compiled the code and BOOM, IT SEGFAULTS RIGHT IN FRONT OF MY FRIEND. Worst, friend had copied a "/bin/sh" code from shellstorm and already had it working.

Really burned my ego, I sat continuously for 8 hrs in front of my laptop and didn't talk to anyone. I was continuously debugging the code for 8 hrs. Just a few minutes ago, I noticed that the shellcode which I'm actually putting in my C code is actually 2 bytes shorter than actual code length. WHAT THE F. I ran objdump manually and copied the opcodes one by one into the string (like a noob) and VOILA ! IT WORKED !!!

TURNS OUT I DIDN'T CUT THE LAST COLUMN OF OPCODES IN MY SHELL SCRIPT. I FIXED THAT AND IT WORKED !!
THE SINGLE SHITTY NUMBER MADE ME STRUGGLE 8 HRS OF MY LIFE !! SMH

Lessons learnt :
1)Never have such an ego that makes you think you're perfect, cuz you're retarded not perfect
2)Examine your scripts properly before using them
3)Never, I repeat NEVER!! brag about your code before compiling and testing it.

That's it!
If you've read this long story, you might as well press the "++" button.

Spent the last 15 days deep into Golang and suddenly I stumbled upon Buffalo (https://github.com/gobuffalo)

Damn, it is fucking awesome.

Just wanted to share it.

Just realized that I'm at page 508 of
http://clientsfromhell.net ... what am I doing with my life 😓

So... After this bullshit https://devrant.com/rants/1523838/...

Me: hey boss, so.. I made a list out of those PowerPoint's on Trello ( more than 50 cards ) , can we sit later to priorize them?

Boss: well.. We can but for me all those are important. And we are gonna have those other requests (THIS IS THE HUGE ONE) next week.

Me inside: aaaaahhhh... Scream to your faceeeee!!! I'm gonna kill you and use your skull as a fucking mug!!! Motherfucker!!!

Me: ok.

Our deadline is end of this month :)

Apparently I'm surrounded by morons...

For the past 7 days since I was ordered to learn react wich originated this rant https://devrant.io/rants/805055/...

I somehow know more of it then my team that is on it for the past month or more.

Looks like the "standard" is to pass refs everywhere instead of proper props/state utilization.

At first I was confused by the usefulness and credibility of it but after a literal 1 fucking minute google search I found it to be a bad practice discouraged even by official docs.

Wtf? No one read the docs?

Network manager: administration just canceled our domain registration 2 months before schedule.

Boss: uh.. OK... but can't we make a script to route traffic from www.canceled.com to our server?

Me: that's not how DNS works ( proceed to explain how DNS works )

PS: boss is lead developer... wtf?