Date: Thu, 3 May 2012 11:21:24 -0400 From: Robert Simmons <rsimmons0@gmail.com> To: freebsd-security@freebsd.org Subject: Re: OpenSSL and Heimdal Message-ID: <CA%2BQLa9AkeMnwwW_wVMy%2BbQB9zTCLoLXe9sp%2BmQAY8Jrkeg9FLA@mail.gmail.com> In-Reply-To: <op.wdqiybsx34t2sn@tech304> References: <CA%2BQLa9Asg0GkKKihhXLwpwOGz1T3u%2BJWhqo66L0M1denkeBq_Q@mail.gmail.com> <201205022201.50506.matt@chronos.org.uk> <op.wdpb2rip34t2sn@tech304> <201205022345.27904.matt@chronos.org.uk> <op.wdqiybsx34t2sn@tech304>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 3, 2012 at 9:40 AM, Mark Felder <feld@feld.me> wrote: > On Wed, 02 May 2012 17:45:27 -0500, Matt Dawson <matt@chronos.org.uk> wrote: > >> >> IE might be the only client with support for those protocols right now >> but somebody has to lead the way on the server side or you end up with >> a mutual apathy loop (AKA positive can't be arsed feedback loop). > > > Actually Opera is the only browser on the market that supports TLS 1.2, > unless Firefox or Chrome added support within the last 6 months. I doubt it > though because FF and Chrome tend to use already existing open source > infrastructure and Opera forged ahead and wrote their own TLS 1.2 code. TLS 1.1 and 1.2 support are at different stages as far as Firefox is concerned. Actually, the implementation is in the nss library specifically. Once this is finished, unless I'm way off the mark, both Chrome/Chromium and Firefox will both support whatever the nss library supports. There are two bugs open, and it looks like 1.1 is making recent progress, and 1.2 is basically flooded with the usual "Hey, when is this happening" comments rather than patches: TLS 1.1: https://bugzilla.mozilla.org/show_bug.cgi?id=565047 TLS 1.2: https://bugzilla.mozilla.org/show_bug.cgi?id=480514
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BQLa9AkeMnwwW_wVMy%2BbQB9zTCLoLXe9sp%2BmQAY8Jrkeg9FLA>