security - ajax login procedure - is using salt and hash is really neccessary? -


I am sending a password which informs the user without any ambiguity. I have read the following suggestions before sending the data. :

  Ask the server for a seed value (a salt) using an AJAX request password + seed using sha 1 amount  

Do these steps actually implement security in any way? The salt is not going to be unique, so everyone can get it. Salting algorithm is available to everyone because it applies to a customer, Sha1 Amount Algorithm is also available so that no one can use it to use the password. So what's the benefit?

As far as I know these steps () salt is unique to every session, therefore Every login attempt will get its own, separate salt. Please consult your sources if this is the case, even then.

The customer sends the hash of the password after reading the salt for the current logging process and sends the server to the server which compares it to the password is muted + salt


Comments

Popular posts from this blog

ios - How do I use CFArrayRef in Swift? -

eclipse plugin - Run java code error: Workspace is closed -

c - Error on building source code in VC 6 -