Timeline for AES 256 Encryption - Is it really easy to decrypt if you have the key?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 6, 2017 at 23:54 | comment | added | Maybe_Factor | If the attacked has stolen both databases, they will likely steal your code base also. In which case, tracking down the correct details of your encryption scheme is a trivial afternoon browsing through your code. As an aside: Your IV should be random and public, and wouldn't a static salt be a pepper? My understanding was that with a good random IV, you don't need to salt your data anyway. | |
| S Jul 23, 2013 at 6:43 | history | suggested | e-sushi | CC BY-SA 3.0 |
Made the question sound less *"hacky"* and corrected some typos and formatting while I was at it.
|
| Jul 23, 2013 at 3:40 | review | Suggested edits | |||
| S Jul 23, 2013 at 6:43 | |||||
| Jul 19, 2013 at 11:52 | answer | added | Mayank Varia | timeline score: 5 | |
| Jul 18, 2013 at 8:58 | vote | accept | SteveB | ||
| Jul 18, 2013 at 8:22 | history | tweeted | twitter.com/#!/StackCrypto/status/357777275187507200 | ||
| Jul 18, 2013 at 4:54 | answer | added | user7576 | timeline score: 0 | |
| Jul 17, 2013 at 17:09 | comment | added | Paŭlo Ebermann | What is the unknown part? The initialization vector? The mode of operation? Something else? | |
| Jul 17, 2013 at 11:38 | comment | added | hunter | If the encryption mode (CBC) isn't known to the attacker, then ciphertext(s) of round block size lengths (16, 32, 64, etc) should be a pretty good clue. | |
| Jul 17, 2013 at 11:08 | answer | added | rath | timeline score: 10 | |
| Jul 17, 2013 at 10:12 | review | First posts | |||
| Jul 17, 2013 at 11:52 | |||||
| Jul 17, 2013 at 9:56 | history | asked | SteveB | CC BY-SA 3.0 |