Timeline for Do the BEAST and CRIME attacks apply to an IMAP service?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 17, 2017 at 10:46 | history | edited | CommunityBot |
replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
|
|
| Jan 22, 2015 at 8:24 | history | tweeted | twitter.com/#!/StackSecurity/status/558178314775711744 | ||
| Dec 24, 2014 at 23:28 | history | edited | Gilles 'SO- stop being evil' |
edited tags
|
|
| Jul 23, 2014 at 19:34 | answer | added | fel1x | timeline score: 4 | |
| Feb 15, 2014 at 15:12 | comment | added | Adi | I think you should be allowing only TLSv1.1 and up anyway. I'm not a crypto wizard, but think that CRIME is, practically speaking, only relevant when it comes to things like HTTP headers, and both attacks (CRIME and BEAST) depend on malicious code being executed on the client. I don't see how you can do that under IMAP using a mail client. With my shallow knowledge, I'd say that CRIME and BEAST do not apply in this situation. | |
| Feb 15, 2014 at 11:07 | history | asked | Lekensteyn | CC BY-SA 3.0 |