Timeline for Does using the same encryption algorithm multiple times make a difference?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 29, 2014 at 2:59 | history | edited | SecurityAndPrivacyGuru | CC BY-SA 3.0 |
Integrating additional detail given in comment below into the full answer
|
| May 28, 2014 at 7:21 | comment | added | user | You really should edit your post to include additional information, rather than responding in comments. (Although using a reply comment to draw the attention of whomever asked for the additional information to the edit is usually a good idea.) Comments are supposed to be ephemeral, and are second-class citizens on Stack Exchange; they can be (and many times are) deleted for almost any reason. | |
| May 28, 2014 at 3:45 | comment | added | SecurityAndPrivacyGuru | Thx for the ? Michael. Given that there's no practical diff between encrypting 1x or more than once, I did not assume the original question meant 3 diff keys. Doing so would cost 200% additional computational resources to perform, but produce no practical gain to the confidentialiity of the data being encrypted. Brute force on a 128-bit key requires a billion-billion years (1.02 x 10^18) to exhaust the key space, which means it's practically impossible. 3 diff keys would be impossible^3 (aka still impossible), but cost 2x more CPU resources. Hope that assumption was right. :-) | |
| May 27, 2014 at 11:52 | comment | added | user | "using the same encryption algorithm and key multiple times to encrypt data will not change the outcome of the attack" Well, obviously; it will slow down each test a bit, but it won't buy you any significant additional security. Could you perhaps elaborate on what reason you have for stating that the same key is used multiple times? | |
| May 26, 2014 at 23:49 | review | First posts | |||
| May 27, 2014 at 0:00 | |||||
| May 26, 2014 at 23:28 | history | answered | SecurityAndPrivacyGuru | CC BY-SA 3.0 |