Timeline for Login system using authenticated encryption without storing user password
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 17, 2017 at 10:46 | history | edited | CommunityBot |
replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
|
|
| Jun 10, 2013 at 20:03 | comment | added | niea | Thanks peterph for pointing out that I was thinking about the exactly the same thing as the hashed password and your suggestion of bcrypt. Also, I'm not developing anything right now but I was just thinking too hard... | |
| Jun 10, 2013 at 19:22 | vote | accept | niea | ||
| Jun 10, 2013 at 14:16 | comment | added | Joshua | I'd like to point out that Microsoft's Encrypting File System uses the same concept as LUKS at a file level (not disk level!). Each file is encrypted using a randomly generated symmetric key and the symmetric key is then encrypted using the user's EFS certificate (and any other recovery agents, allowing administrators to access the contents) and stored along side the file in an alternate data stream. | |
| Jun 10, 2013 at 12:50 | history | answered | peterph | CC BY-SA 3.0 |