Mysql - No Password Encryption.. RISKS?

[lorenzokid]

Can someone tell/explain me the risks if i am not having any security on the passwords in my Mysql Server Database....

('".sql_sanitize($username)."','".sha1($password)."','".sql_sanitize($birth)."','".sql_sanitize($email)."','".sql_sanitize($ipaddress)."')") or die(mysql_error());.......

cuz the owner.. me.. will only be able to see the passwords right.. so why the security :tongue: ????????

Thank You.:closedeyes:

 

[EliteGM]

I suppose that if someone gets their way into your database you wouldn't want them to be able to read the passwords..?

 

[Bloodraven]

Well, There are a lot of risks, If you secure your server/software enough I suppose its fine but you should just encrypt them, Much more secure, If someone gets hold of the database, Your users and you are fucked pretty much unless you can get them all to reset their passwords, Just use MD5 imo

 

[lorenzokid]

hmm ok .. but yeah i cant make a function now like sending the password back to the owners e-mail because of the SHA1 security.. and i also cant help with the account problems without any unsecured information.. i just hope my server is secure enough .. and hope nobody gets into my computer lol

 

[TimeBomb]

hmm ok .. but yeah i cant make a function now like sending the password back to the owners e-mail because of the SHA1 security.. and i also cant help with the account problems without any unsecured information.. i just hope my server is secure enough .. and hope nobody gets into my computer lol

Non-encrypted passwords are a huge security risk. Don't just assume your server and website are secure enough that your database is completely safe. That's impossible.

To have the user reset their password when the database is using an encrypted password, all you do is send them an email with a link. That link brings them to a page that then has them enter their new password twice. They hit a button, and the new password is encrypted and goes straight in to the database. No one is ever able to get that specific password from the database if it is ever lost, but they are still able to reset it if need be.

 

[Henry]

...
To have the user reset their password...
...

Or generate a new password when requested, email it to the user and store it encrypted in the database.

 

[Justei]

hmm ok .. but yeah i cant make a function now like sending the password back to the owners e-mail because of the SHA1 security.. and i also cant help with the account problems without any unsecured information.. i just hope my server is secure enough .. and hope nobody gets into my computer lol

Well in the register script, at the same time as you insert it into the db you just send it to them via mail, not very hard.

Ofcourse you can help with account problems without PW, why wouldn't you, if you want to login without PW that's a very simple thing to do with a few lines of PHP to make a seperate login script for your admin panel so you can log in as any user without PW.

Never assume your script/server is secure ENOUGH, all websites can be hacked in some way, so if the right people want to they can always get in in some way, in this case I don't think they would have much of a problem with doing that.


NOT hashing the passwords is very stupid, and for that reason alone I would never register at your website because I don't want you, or anyone else to have my password, oh and don't just MD5 the password, at least use a salt, if you use MD5 or sha1 you can just not do anything at all, if you just use md5 or sha1 the hacker can just use a rainbow table and decrypt the passwords.

 

[s-p-n]

Or generate a new password when requested, email it to the user and store it encrypted in the database.

Not exactly.. That brings up a new security risk.. A malicious user can go in and reset user's passwords without the user's consent.

Whether they need to know the username or email address or the user's birthday, or even some security question- don't matter.. Well at least I wouldn't put my users at risk like that... More annoying than not.. I imagine you'd send the new pass to the user's email, right? Of course you would.

 

[Chris]

You included in the example in the op using a "sanitize" function.

I hope you aren't planning on not sanitizing your information, because that's open ground for injection.

even a simple mysql_escape_string() is better than nothing.

always sanitize and always encrypt. no exceptions.

-Chrisdothtml

 

[holthelper]

let me ask you this as a real life question.

you have a credit card. why have a pin if your the only person with that card? that pin is unique to you and you only (if you dont tell others). also too if you lose your card (people get into your database) they dont have a direct access to what ever they want...