Timeline for How should a user's death be handled?
Current License: CC BY-SA 2.5
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 1, 2018 at 21:30 | comment | added | wizzwizz4 | @AdamDavis I meant in the OAuth provider having a breach. | |
| Apr 1, 2018 at 19:38 | comment | added | Pollyanna | @wizzwizz4 Sure. At which point we can burn that bridge if we need to by locking all accounts that don’t update to new password when Stack Overflow implements whatever the latest encryption is at the time quantum computers are able to break current encryption. And if Stack overflow has a breach the dormant account are the least of our worries. | |
| Apr 1, 2018 at 19:28 | comment | added | wizzwizz4 | @AdamDavis Breaches and quantum computers. | |
| Feb 8, 2010 at 22:15 | comment | added | Pollyanna | @Chas - if you choose to use an OpenID provider or password that is susceptible to brute forcing, then your account deserves to be hacked posthumously. If you use a random alphanumeric string longer than 8 characters with an OpenID provider that blocks repeat attempts, then it would take centuries to crack. It would probably be easier to break into SO itself, or spoof the DNS servers SO uses, at which point does it really matter? | |
| Feb 8, 2010 at 22:15 | history | edited | dmckee --- ex-moderator kitten | CC BY-SA 2.5 |
added 2 characters in body
|
| Feb 8, 2010 at 22:03 | comment | added | dmckee --- ex-moderator kitten | Well, number one item for policy on dead users: ability to lock the account. See, we're about half way there. | |
| Feb 8, 2010 at 21:52 | comment | added | Chas. Owens | Given that you are no longer around to change the password, it is only a matter of time before someone brute forces your password. Having some method of marking a user as no longer able to log in would prevent this. | |
| Feb 8, 2010 at 21:27 | history | answered | dmckee --- ex-moderator kitten | CC BY-SA 2.5 |