security - Client or Server side password hashing when a user registers (using HTTP) -
i have web application can use both http , https (depending on user chooses). when user registers, should password hashed on client side passed server or should plain text passed server , hashed.
believe packet sniffing tools can used capture password if using http, better hash on client side?
would better hash on client side?
no, don't hash username/password on client side, doesn't make sense.
if web application using https, register request enctypted, means hashing password redundant.
if web application using http, sniffing in network can see http packets of web app, means:
- all client files of web application public, including hash algorithm , secret key (if any). hash algorithm , hashed-password, sniffer can crack original password.
- even if sniffer failed hash algorithm, or failed crack original password, he/she can use hashed-password "login" web application , whatever he/she want.
in summary, once web application using http, nothing secure.
Comments
Post a Comment