network profile
| bio | website | lambdor.net |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 5 months |
| seen | Aug 6 '12 at 12:38 | |
| stats | profile views | 2 |
|
Jan 13 |
awarded | Nice Question |
|
Dec 7 |
comment |
How to guarantee that password is hashed on server-side? "You could give the server your public key, and have it verify who you are by encrypting a nonce with the private key. You can use SSL for this, with client certificates." interesting. Is this actually used at authentication for webservices and how can I verify this scheme? But I assume this can't be done when on-the-go as you don't have acces to the private key. |
|
Dec 7 |
comment |
How to guarantee that password is hashed on server-side? "require your providers to hash passwords, and include penalty clauses." this unrealistic for free services |
|
Dec 7 |
comment |
How to guarantee that password is hashed on server-side? "simply use a password manager with a generated password": what if you're on the go? "checking the password recovery method" thx for tip :) a black-list of sites would be nice |
|
Dec 7 |
revised |
How to guarantee that password is hashed on server-side? added 94 characters in body |
|
Dec 7 |
awarded | Editor |
|
Dec 7 |
comment |
How to guarantee that password is hashed on server-side? yes, I know, but I think it's simply an unrealistic requirement to remember a password for all the 100 sites you're registered on. password store? okay, but what if you're on the go. use your in-the-head hasing, like adding the domain? okay, but actually insecure as the pattern can easily be uncovered. |
|
Dec 7 |
revised |
How to guarantee that password is hashed on server-side? actual situation |
|
Dec 7 |
awarded | Student |
|
Dec 7 |
asked | How to guarantee that password is hashed on server-side? |
