News for hackers. Stuff that matters.
Re:Basic Cryptography Concepts for Developers by nickpsecurity on Tuesday October 06, 2015 @08:54PM (#10343498)
Funny thing is I did BASE64 a password. Sort of. I used to run strong passwords + random stuff on paper through SHA-2 with result encoded in BASE64. Optionally an extra iteration or two for SHA-2. Used BASE64 because it fit the max number of characters for TrueCrypt passwords: my use case for this method. Had a tool to make this easier.

Idea was to obfuscate a strong password to make cracking more difficult. Plus, it was relatively easy to implement on arbitrary computers. These days I just memorize them or write them on paper.

Re:Basic Cryptography Concepts for Developers by paragon_init on Tuesday October 06, 2015 @09:09PM (#10343547)
If you use bcrypt (which we recommend), you're technically using a variant of BASE64 too.

The title is a reference to a meme ("You wouldn't download a car!") and also a reference to some absurdly bad cryptography, e.g. http://www.cryptofails.com/post/87697461507/46esab-high-qual...

Re:Basic Cryptography Concepts for Developers by gabriel34 on Tuesday October 06, 2015 @09:09PM (#10343549)
I've actually seen production code that BASE64 the password of a service account a script needed. Spotted it because the password ended in "==" and, sure enough, the script only decoded the BASE64, no cypher needed. Advised the client and chown + chmod the file. Client wanted the BASE64 encode still...