Timeline for 2FA: Difference between Storing Backup Codes & Secret Key
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 11, 2019 at 3:00 | history | tweeted | twitter.com/StackSecurity/status/1104940162629419009 | ||
| Mar 11, 2019 at 0:21 | history | edited | AlienBoy | CC BY-SA 4.0 |
fixed grammar and made description slightly easier to read
|
| Jun 8, 2016 at 0:06 | vote | accept | AlienBoy | ||
| Jun 8, 2016 at 0:06 | vote | accept | AlienBoy | ||
| Jun 8, 2016 at 0:06 | |||||
| Jun 8, 2016 at 0:06 | vote | accept | AlienBoy | ||
| Jun 8, 2016 at 0:06 | |||||
| Jun 8, 2016 at 0:05 | vote | accept | AlienBoy | ||
| Jun 8, 2016 at 0:06 | |||||
| May 4, 2016 at 13:18 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 8, 2016 at 6:38 | comment | added | AlienBoy | @SEJPM, to my understanding/experience, backup codes only let you login for one time, they won't necessarily reveal the secret key to you. But once you logged in, you can regenerate a new secret key if you want. And yeah, they serve the same purpose in terms of logging you in, except backup codes are one-time use. So I assume storing backup codes should somewhat safer then storing secret keys, since you can pass the security check in unlimited times once you have the secret key. | |
| Mar 5, 2016 at 12:41 | comment | added | SEJPM | My guess is that the backup code is some sort of password the system gives you to allow you to see the secret key again. By this logic, it is functionally equivalent to the secret key although not identical. | |
| Jan 5, 2016 at 11:55 | answer | added | Mike Scott | timeline score: 6 | |
| Jan 5, 2016 at 11:44 | history | edited | AlienBoy | CC BY-SA 3.0 |
fixed grammar & wording
|
| Jan 4, 2016 at 8:34 | review | First posts | |||
| Jan 4, 2016 at 9:19 | |||||
| Jan 4, 2016 at 8:30 | history | asked | AlienBoy | CC BY-SA 3.0 |