News for hackers. Stuff that matters.
Re:Hoping to avert “collision” with disaster, Microsoft reti... by chris_wot on Tuesday November 12, 2013 @09:30PM (#6722958)
Internet Explorer is the first browser to implement SSL/TLS 1.2? What about Firefox and Chrome - anyone know their status?
Re:Hoping to avert “collision” with disaster, Microsoft reti... by nezza-_- on Tuesday November 12, 2013 @09:57PM (#6723041)
I think they mean that they're the first to retire the cipher suits, not the first who implemented TLS1.2.

Quote from here: http://en.wikipedia.org/wiki/Transport_Layer_Security#Dealin...

  Chrome 30 and Opera 17 support TLS 1.1 and 1.2 enabled by default. Firefox 25 and 24
  ESR, and Internet Explorer 6-10 have support for TLS 1.1 and 1.2 but disabled by default
  (Firefox 28 Nightly and IE 11 supports TLS 1.1 and 1.2 enabled by default).
  Safari 6 for Mac OS X 10.8 and 10.7, and Safari 5 for Windows and support only
  TLS 1.0 (Safari for iOS, and Safari 7 for Mac OS X 10.9 support TLS 1.1 and 1.2
  enabled by default).
Re:Hoping to avert “collision” with disaster, Microsoft reti... by yuhong on Tuesday November 12, 2013 @10:55PM (#6723250)
I just made a correction to the part on Internet Explorer on Wikipedia.
Re:Hoping to avert “collision” with disaster, Microsoft reti... by XEKEP on Tuesday November 12, 2013 @10:35PM (#6723182)
They said IE11 is the first to make TLS 1.2 default. And it is apparently true.
Re:Hoping to avert “collision” with disaster, Microsoft reti... by yuhong on Tuesday November 12, 2013 @10:17PM (#6723126)
I think Opera was the first browser to do so, but Windows SChannel implemented it in the original Win7 RTM release so was not far behind.