Hello all,
Yesterday I called 1and1.com's customer service to change my hosting package (I am moving off of their servers and only using them as registrar). To complete my transaction they needed my account password, which I could not remember as I use LastPass.com to setup website passwords.
1and1 therefore sent me an email that contained my full password in plaintext, which means that their servers must store my password either in plain text, or with a reversibly decryptable storage scheme. This was not a reset request.
Storing the plain text of a password, or an encrypted variant of it, is not considered good security policy, as that renders those passwords accessible in the event of an attack on the servers storing the passwords.
If you use 1and1 hosting, make sure that your customer login password is a unique string that reveals nothing about your other passwords on any other website. Also be aware that in the event 1and1's password storage was ever compromised, an attacker would be able to log into your 1and1 account looking like you and using your real password.
--
The best practices method for login authentication is using a "salted hash." A "salt" is random characters that are appended to your core password, and a "hash" is a one way mathematical function that produces a fixed length string from calculations on your salt+password. The common hashes are MD5, SHA1, and SHA256.
The server then stores the value of the hash, and when you login, the hashed value of your salted password is passed to the server, which checks if the hashes match. Most major internet frameworks, like vBulletin here, Wordpress, Drupal, Joomla, etc. use salted hashes.
No site admin should ever be able to send you your password, they should only be able to reset it (i.e. clear the expected hash value). Any site that can send you your password is also storing it, and you are then unfortunately dependent on the server's security to protect that password.
Also, choose long, strong passwords that include as many character classes as a website will allow. There are "rainbow tables" that allow lookup of hash values for common words/phrases/known passwords.
Yesterday I called 1and1.com's customer service to change my hosting package (I am moving off of their servers and only using them as registrar). To complete my transaction they needed my account password, which I could not remember as I use LastPass.com to setup website passwords.
1and1 therefore sent me an email that contained my full password in plaintext, which means that their servers must store my password either in plain text, or with a reversibly decryptable storage scheme. This was not a reset request.
Storing the plain text of a password, or an encrypted variant of it, is not considered good security policy, as that renders those passwords accessible in the event of an attack on the servers storing the passwords.
If you use 1and1 hosting, make sure that your customer login password is a unique string that reveals nothing about your other passwords on any other website. Also be aware that in the event 1and1's password storage was ever compromised, an attacker would be able to log into your 1and1 account looking like you and using your real password.
--
The best practices method for login authentication is using a "salted hash." A "salt" is random characters that are appended to your core password, and a "hash" is a one way mathematical function that produces a fixed length string from calculations on your salt+password. The common hashes are MD5, SHA1, and SHA256.
The server then stores the value of the hash, and when you login, the hashed value of your salted password is passed to the server, which checks if the hashes match. Most major internet frameworks, like vBulletin here, Wordpress, Drupal, Joomla, etc. use salted hashes.
No site admin should ever be able to send you your password, they should only be able to reset it (i.e. clear the expected hash value). Any site that can send you your password is also storing it, and you are then unfortunately dependent on the server's security to protect that password.
Also, choose long, strong passwords that include as many character classes as a website will allow. There are "rainbow tables" that allow lookup of hash values for common words/phrases/known passwords.
Last edited: