Timeline for What's the issue with Apple's backdoor?
Current License: CC BY-SA 3.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 10, 2020 at 10:51 | comment | added | SEJPM | This is more of a question for Information Security, however it can no longer be migrated and was apparently accepted here back in early 2016. I have thus locked it for historical significance. | |
S Nov 10, 2020 at 10:51 | history | notice added | SEJPM | Historical significance | |
S Nov 10, 2020 at 10:51 | history | locked | SEJPM | ||
Feb 18, 2016 at 19:18 | vote | accept | David | ||
Feb 18, 2016 at 2:32 | history | tweeted | twitter.com/StackCrypto/status/700145823636701184 | ||
Feb 18, 2016 at 0:42 | answer | added | Gilles 'SO- stop being evil' | timeline score: 3 | |
Feb 18, 2016 at 0:18 | answer | added | mandragore | timeline score: 0 | |
Feb 17, 2016 at 20:54 | history | edited | otus | CC BY-SA 3.0 |
added 2 characters in body
|
Feb 17, 2016 at 19:46 | comment | added | mikeazo | In short, the judge told apple to make it easier to brute force the PIN. This would be done by disabling (non-cryptographic) security features and adding some additional capability (the ability to use hardware to type the PIN as opposed to a finger). So no backdoors in encryption algorithms. But, security of encryption is only as secure as security of the key. So by making the key easy to get, you are giving, in some sense, a "universal key". | |
Feb 17, 2016 at 19:42 | comment | added | mikeazo | Have you read this article? | |
Feb 17, 2016 at 19:39 | review | First posts | |||
Feb 17, 2016 at 20:55 | |||||
Feb 17, 2016 at 19:36 | history | asked | David | CC BY-SA 3.0 |