Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That is annoying, and is a bad security practice, but not the end of the world as a customer. It's actually slightly less horrifying at Namecheap, because as your registrar you should be using crazy good passwords anyways, which means they're never re-used.

Three recommendations:

* head /dev/random | md5 # very annoying to type, though

* ruby -e 'puts rand(1<<128).to_s(32)' # less annoying to type

* Keychain Access password helper at "memorable, 31 long"

Note that FedEx has the same bad behavior.

The real risk here is to Namecheap, who is utterly exposed in the event of a database leak. If they're keeping online plaintext passwords, they'll have nothing to say to mitigate the catastrophic damage of giving up many of their customer's most sensitive credentials.



I'm probably missing something, but why md5 the output of /dev/random - won't it have the same entropy it started with?


/dev/random is random bytes, so in order to make it typable, it's useful to convert it into characters. md5 is good for that.

Alternatively, strings /dev/random|head gives some stuff that you can concatenate into a password.


For a single process bit of typeable entropy from our OpenBSD friends, try:

openssl -rand base64 12

On your favorite Unix.


You mean "openssl rand -base64 12".




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: