So I set my password to
sudo rm -rf --no-preserve-root /
So the other day, I saved a big object to a file during a debugger session with a path like
~/debug.jsononly to find out later that the debugger didn’t support shell expansions and instead of saving to the home directory it had literally saved the file under a directory called~inside my project. Now at that point I didn’t need the file anymore anyway, so you never guess what I proceed to do next, and mind you now I was in my regular terminal: I ranrm -rf ~. Lost a bunch of dot files, but thankfully all the permission errors I got made me realize what was going on and I cancelled the operation quickly before any bigger damages were done.The leading
./to operate on a file in thecwdhas saved me a lot of headaches, I’m sure.It’s a sad day when you realize your biggest enemy is yourself.
I wonder though: is
elogindor any other session manager hackable/crashable/injectable from the login prompt on a Linux system using only a keyboard 🤔 physical violence disallowed!
This picture is definitely AI right? Like the the name of the keyboard has a question mark in it and the switches look weird and are different colors.
I wonder if base64’ing something like this makes it safe for input, but dangerous for some backends?
c3VkbyBybSAtcmYgLS1uby1wcmVzZXJ2ZS1yb290IC8=It would have to be a really strange situation where the backend would be decoding and then running just the password field as a bash command. Very likely not to be the case.
To make it more likely to work, you want to take a page from SQL injection and make sure you include something at the start of the command to terminate whatever was there first and end with a comment character to ignore anything after.
In addition you probably want to drop the ‘sudo’ in this case, as it’s far more likely that whatever is running this would be running as root rather than a user account with sudo with password disabled.
You’d want something more like
&& rm -rf --no-preserve-root / #JiYgcm0gLXJmIC0tbm8tcHJlc2VydmUtcm9vdCAvICMKinda reminds me of this: https://xkcd.com/1700/
Or they’re tryna send it out of a reverse shell and forget to put the command name as the 0ᵗʰ argument
Only one way to find it out


