The need for hashing the password client-side, while the https connection is used
There is a reason to hash the password on the client side, if you are using a secure connection (https)?
I understand that if you use https, then all traffic is encrypted ... and password are also passed to the encrypted.
Or am I wrong?
yeah; if you're DB gets hacked, you are facing a lot more liability if you store clear-text passwords than hashes. You should never let a password enter your building; it becomes your liability at that point.
Originally Posted by CrazySurfer
If you form is using GET the password can show up in logs and history. I once saw terribly-written embed code that changed the action of whatever was the first form in the dom. If that happens to you and you send passwords to lord know where, people are going to complain loudly.
Create, Share, and Debug HTML pages and snippets with a cool new web app I helped create: pagedemos.com
I know it's bad practice to store clear-text passwords. But i can hash password on the server-side, not client.
Originally Posted by rnd me
Client-side hashing isn't "necessary" over SSL, so long as you transmit the password in POST data, as opposed to GET data.
ADDENDUM: In fact, I think it's actually quite uncommon that web apps will perform client-side password hashing. If you open Firebug or inspector in chrome/safari and log into facebook, for instance, you'll see that your credentials are provided plainly in the POST data. The only transit security is the SSL.
Last edited by svidgen; 06-08-2012 at 02:25 PM.
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Tags for this Thread