Timeline for Is Triple DES still considered safe to use?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2021 at 7:24 | history | edited | CommunityBot |
replaced https://tools.ietf.org/html/draft with https://datatracker.ietf.org/doc/html/draft
|
|
| Sep 21, 2017 at 7:01 | comment | added | fgrieu♦ | @Maarten Bodewes: attacks that reduce two-key 3DES to 80-bit security either are well-guarded secrets, or require so ludicrously many accesses to so much fast RAM as to be currently impractical; see this. In today's practice, two-key 3DES remains common. It is more endangered by side channels, other leaks or fault attacks, its small block size, slowness, lack of long term assurance of confidentiality, and non-conformance to security recommendations, than by likelihood of a successful key search compromising its short-term operational security. | |
| Sep 19, 2017 at 22:35 | comment | added | Jon Callas | What he said. The major issue with any cipher with a 64-bit block is that block size and birthday-bounds attacks like Sweet32. There are lots of these around like 3DES, Blowfish, IDEA, and so on. AES is faster and more secure than any of them. If you don't like AES, look at Twofish or Serpent. If you have a project using 3DES, updating it should be on your list at priority 2, along with cleaning out the junk drawer in the kitchen. You should do it, it doesn't matter if it's today. If you have a new project, don't. Just don't. | |
| Sep 19, 2017 at 17:34 | comment | added | Lery | @MaartenBodewes Very true, I should have mentioned that 2 keys 3DES has even been deprecated since December 2015 by NIST SP800-131A. Regarding the weak keys and the rest, it can't hurt to mention those, thanks. | |
| Sep 19, 2017 at 16:44 | comment | added | Maarten Bodewes♦ | Two key 3DES provides something like $2^{80}$ security, which is way too close to the limits of brute force attacks to be used in modern designs. Note that 3DES is slower than AES while providing less security and, indeed, only half the block size, weak keys, parity bits and more mumbo-jumbo that you can really do without... (excellent answer, by the way) | |
| S Sep 19, 2017 at 16:17 | history | suggested | chrki | CC BY-SA 3.0 |
Fixed a small typo and moved link
|
| Sep 19, 2017 at 14:58 | review | Suggested edits | |||
| S Sep 19, 2017 at 16:17 | |||||
| Sep 19, 2017 at 14:20 | history | edited | poncho | CC BY-SA 3.0 |
added 4 characters in body
|
| Sep 19, 2017 at 14:18 | history | answered | Lery | CC BY-SA 3.0 |