Timeline for Generating passwords using Password-Based Key Derivation Function
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2020 at 8:17 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jul 21, 2016 at 10:26 | comment | added | otus | @tylo, sure, but hopefully it's at least designed to be secure from the cryptographic point of view, when using established software. (I.e. it becomes "just" a problem of keeping the key/password/what have you safe.) | |
| Jul 21, 2016 at 10:24 | comment | added | tylo | You're right, there are more options for recovery. But that recovery method also has to be considered in the evaluation of the security. If the recovery method isn't secure, you got a problem. | |
| Jul 21, 2016 at 10:13 | comment | added | otus | @tylo, as discussed in the comments to the linked question, with password managers you have alternatives for backup: for example, a key you keep secure may be used for recovery, or an alternative, longer password can be used. (Options depend on the particular software, of course.) | |
| Jul 21, 2016 at 9:38 | comment | added | tylo | Considering the last point: Even with a password manager, you should use a programm which has a master password to access the password database. So in case you loose your master passords, that database is gone as well, this isn't changing. But that is kind-of what you want: Without master passwords, no one has access to the individual saved passwords. If there is any recovery method, that is a security weakness. | |
| Jul 21, 2016 at 7:39 | vote | accept | maowtm | ||
| Jul 21, 2016 at 7:39 | comment | added | maowtm | Looks like scrypt makes GPU attacks impractical which is better than PBKDF2. Thanks. | |
| Jul 21, 2016 at 7:21 | history | answered | otus | CC BY-SA 3.0 |