News for hackers. Stuff that matters.
Re:The DROWN Attack by Natanael_L on Tuesday March 01, 2016 @07:23PM (#11207302)
Re:The DROWN Attack by Gibbon1 on Tuesday March 01, 2016 @07:50PM (#11207414)
Thanks that would be the one. I get this feeling that encryption protocols and standards often end up and all sorts of dank corners of the web infrastructure and finding and updating all of these is really messy task. And I suspect service providers and their customers haven't been really good at keeping track of everything.
Re:The DROWN Attack by Nimi on Tuesday March 01, 2016 @08:29PM (#11207550)
Fascinating. I still feel I'm missing something basic here: If Microsoft, Google and Mozilla announce they're not going to accept any particular crypto primitive two years from now, and this time there won't be any exceptions, CAs and websites just have to abide, don't they?
Re:The DROWN Attack by nl on Wednesday March 02, 2016 @07:26AM (#11209510)
The browsers say what they accept, the server says what it provides and something in the intersecting set will be used.

If (as a random example that didn't annoy me at all for 2 years) a website also needs to support SmartTV devices which only accept obsolete certificates then your server has to either break them or not.

Re:The DROWN Attack by Natanael_L on Wednesday March 02, 2016 @03:49AM (#11208821)
Then a bunch of big companies announce they'll use another browser to be able to keep using it
Re:The DROWN Attack by Nimi on Wednesday March 02, 2016 @06:37AM (#11209328)
Another browser beside Chrome, Firefox and IE? OK, so Symantec announces that they will only use Opera. Even then, they have to deal with their customers, website operators who need a certificate trusted by the big 3 browsers, leaving. In fact, now that Let's Encrypt certificates are free, it seems like this is the Symantec CA's worst nightmare.
Re:The DROWN Attack by Natanael_L on Wednesday March 02, 2016 @09:22AM (#11210046)
Not CA:s, but clients like banks