Timeline for Emergency method to erase all data off a machine within seconds
Current License: CC BY-SA 4.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 25, 2020 at 18:13 | comment | added | vikarjramun | I don't understand why this answer has been downvoted so much... to me it seems like the answerer proposed some really good non-hardware solutions. | |
Jul 25, 2020 at 13:44 | comment | added | wizzwizz4 | @ManfP “A lot of key”, plus those 256 bits, seems a better strategy than those 256 bits alone. You wipe the 256 (or 4096) bits, and it's almost certainly impossible to recover the data… and then you manage to destroy ⅛ of the one-time pad, making it even harder. | |
Jul 24, 2020 at 9:38 | history | edited | Josiah | CC BY-SA 4.0 |
added 186 characters in body
|
Jul 24, 2020 at 9:33 | comment | added | Josiah | This is true. I also favour normal encryption, and mention in this context that it also contributes valuable interdependence. Even so the context given in this particular question is explicitly against a computationally unbounded adversary, and so although "Just use AES and forget about it" is probably the right answer in the real world (and much more so than a OTP) it's explicitly not a valid answer to the question. | |
Jul 24, 2020 at 2:08 | comment | added | Mark | @Josiah, in practice, any key larger than about 80 bits can't be cracked by current technology, and 128 bits is sufficient for the foreseeable future (barring quantum computing). Also in practice, avoiding key-management mistakes is generally easier the smaller the key is. | |
Jul 22, 2020 at 22:54 | comment | added | Josiah | In theory any key smaller than the data can be cracked by an adversary with unlimited compute capacity. Only OTP scale keys can guarantee that destruction of the key is as effective as destruction of the ciphertext at making the ciphertext unreadable. As I said, it only really comes into its own in combination with the "Shard the data" back-up bomb option. | |
Jul 22, 2020 at 22:47 | comment | added | ManfP | Why would you intrinsically want to "use a lot of key"? It seems much simpler to destroy 256 bits on a small chip than something the size of your data. | |
Jul 22, 2020 at 22:46 | history | edited | Josiah | CC BY-SA 4.0 |
added 60 characters in body
|
Jul 22, 2020 at 22:41 | history | answered | Josiah | CC BY-SA 4.0 |