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.

Since this is a community of developers, thought I'd share something I wrote recently on the UX of shell scripting: https://codeburst.io/13-tips-tricks...

Thoughts are welcome!

Today I created my first shell script for automation.

I have a git repository I use for backing up documents at the training centre I'm at for work. Not a specific project, just all of the documents and miscellaneous stuff. The need for this came about because they re-image the computers every month with a new version of windows (Because they're too cheap to register windows). And I can't risk forgetting to copy all the files onto my USB drive the day before they re-image.

So at the end of each day I open a git bash and type:
git add .
git commit -m "Backup - dd/mm/yy"
git push

Not a particularly laborious task but repetitive and time consuming.
So I decided to create a .sh script to automate the process
(The idea originally occurred because of this post: https://devrant.com/rants/329221/...)

So after about half an hour fiddling about with dates and $ signs, I came up with GitBackup.sh:
git add .
today=$(date '+%d-%m-%y')
commitMsg="Backup - "$today
git commit -m "$commitMsg"
git push origin master

Not much but proud to call it my first automation script.

Remember /dev/rant for devrant (https://devrant.com/rants/1569303) ? :)

Here's the first version of it: https://gitlab.com/netikras/... . read-only, with some hacks.

Oh, and if anyone needs a pure-shell library for json -- feel free to use it :) Bear in mind it might still be buggy.

I am programming a site where developers can share shell scripts and other users can execute it via a CLI.

I decided to add a little joke into it: the page where users can view a shell script is https://mukodik.com/scriptid.sh

I use Express, so I just use app.get('/:id.sh') to get the scriptid.

How would someone possibly bug out this page? (the uploaded shell script is not actually stored in a file, it's stored in a mysql database(using connection.escape to escape chars))