Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "my life in a nutshell"
-
My life in a nutshell.
I've been stuck in this timeless loop for 10 years, anyone that relates?
1. Set alarm before going to bed.
2. Alarm rings, I turn it off.
3. Wakes up late.
4. Work from 08 AM to 4 PM.
5. Take the train back home
6. Plan what to do for the rest of the day.
7. Come home, do everything except what was initially planned.
8. Watching time goes by while doing non-productive things.
9. I feel alone, watch porn to fill this void.
10. I get depressed and unhappy afterward
11. Set the alarm for the next day.
12. Repeat.11 -
My life in a nutshell:
Page 1:
- dress heavy clothes ➡️ it's hot out there.
- dress light clothes ➡️ it's freezing out there
Page 2:
- buy Bitcoin ➡️ its price fell
- sell Bitcoin ➡️ its price is on the sky3 -
Fucking School, when I'm home I'll finish that personal project. Or at least work on it.
Later that day:
God, school's exhausting.. I only wanna play games (League/GW2) with my girlfriend now -
!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.6 -
My life in a nutshell
⛅ morning = sleep 😴
☀️ day = coding job 🖥️
🌆 evening = coding job 🖥️
🌘 night = play videogames 🕹️
Weekend
⛅ morning = sleep 😴
☀️ day = sleep 😴
🌆 evening = cycling 🚲
🌘 night = play videogames 🎮
always alone11 -
My Life in a nutshell
[ CMD + S ]
[ CMD + TAB ]
[ CMD + R ]
( Oh crap! not again 😤)
[ CMD + TAB ]
console.log( 'im here');
[ CMD + S ]
and on and on and on....3