News for hackers. Stuff that matters.
Re:Why Android SSL was downgraded from AES256-SHA to RC4-MD5... by driverdan on Monday October 14, 2013 @02:43PM (#6548864)
Weak cyphers should be disabled on the server entirely, not just re-ordered.
Re:Why Android SSL was downgraded from AES256-SHA to RC4-MD5... by tptacek on Monday October 14, 2013 @03:05PM (#6548988)
Knee-jerk disabling of RC4 because it's "weak" would almost certainly reduce the security of the Internet, because you can't simply evaluate TLS ciphersuites based on the strength of their core cipher; there are lots of deployed TLS clients that can't do block cipher crypto securely right now.
Re:Why Android SSL was downgraded from AES256-SHA to RC4-MD5... by maaku on Monday October 14, 2013 @04:54PM (#6549573)
Examples please?
Re:Why Android SSL was downgraded from AES256-SHA to RC4-MD5... by tptacek on Monday October 14, 2013 @05:03PM (#6549627)
RC4 was first used as a mitigation for the BEAST blockwise-adaptive attack on CBC-with-chained-IVs from SSL 3.0 and TLS 1.0, and then again as a mitigation for the "Lucky 13" timing-based CBC padding oracle that remains a problem in TLS 1.2 when block ciphersuites are used.
Re:Why Android SSL was downgraded from AES256-SHA to RC4-MD5... by maaku on Monday October 14, 2013 @07:31PM (#6550360)
Ok, thank you. I misread - I thought you meant that there were clients which weren't capable of handling block cipher suites (e.g. for performance reasons). You made me look into "Lucky 13" though, so at least I learned something!