security - Best way to handle user account authentication and passwords -
what best way handle user account management in system, without having employees have access database, have access accounts.
examples:
storing username/password in database. bad idea because has access database can see username , password. , hence use it.
storing username/password hash. better method, account can accessed replacing password hash in database hash of account know auth info for. after access granted reverting in database.
how windows/*nix handle this?
this common issue in unix many years ago, , resolved separating user identity components (username, uid, shell, full name, etc.) authentication components (password hash, password hash salt). identity components can globally readable (and in fact must be, if uids mapped usernames), authentication components must kept inaccessible users. authenticate user, have trusted system accept username , password, , return simple result of "authenticated" or "not authenticated". system should application access authentication database, , should wait random amount of time (perhaps between 0.1 , 3 seconds) before replying avoid timing attacks.
Comments
Post a Comment