cross-posted from: https://lemmy.world/post/12516311
Or maybe introduce them to Little Bobby Tables
(skeletor is leading by example by adding that unnecessary apostrophe…)
Too small scale. Set your password as an eicar test string.
This way if your password is decrypted or stored as clear text the host AV will block the file.
$up,erSecr3t’P4ssword\b\n"; DROP TABLE USER;–\b\n\r
This comes to mind
Is that because it was referenced in the title?
It’s because it was referenced in the title, but to be fair GP only wanted to add context for Bobby Tables.
Haha! Your comment reminded me of this.
Have you heard of it?
It’s good we’re not some kind of scripted entities that publish that xkcd strip at every mention of Bobby Tables
I was reminded of this
And add some non-ASCII characters. If the commas did not kill their database, adding unicode will.
I once had problems unpacking an archive I definitely knew the password for. Turns out, zip made on an Android phone had non ASCII letters in the password in some other encoding than the one PC used
Add some extra apostrophe’s to keep the comma’s company
My password is just a buffer overflow and reverse shell. The nop sled takes forever to type tho.
Yes, it’s generally a good idea to annoy the people who now have your data.
I’d hope places aren’t storing your password in plain text. Though I guess I wouldn’t be super surprised if some were.
One of my first projects I took over stored hashed passwords, but only unsalted MD5s, in the process of upgrading the hashing algorithm I discovered the plaintext passwords were logged on any sign in, sign up, or password change…
