There is one known regression. Also, the BEAST workaround is an incompatible change for some applications. Otherwise, I expect it to be drop-in compatible.
- Brian ----- Original Message ----- > From: "Julien Pierre" <julien.pie...@oracle.com> > To: "Brian Smith" <bsm...@mozilla.com> > Cc: "mozilla's crypto code discussion list" > <dev-tech-crypto@lists.mozilla.org> > Sent: Monday, October 17, 2011 6:02:35 PM > Subject: Re: NSS 3.12.* maintanence after the NSS 3.13 release? > Brian, > > On 10/17/2011 15:55, Brian Smith wrote: > > NSS release announcements are made on the Mozilla dev-tech-crypto > > mailing list: > > > > http://groups.google.com/group/mozilla.dev.tech.crypto/browse_thread/thread/28c9fd2d65f7bd55# > Thanks, I wasn't on the list then. > > It looks like there is one binary incompatible change, SSL 2.0 > disabled by default. I'm not sure yet if this will be a problem. > > Other than this change, do we expect this release to be a binary > compatible drop-in replacement for 3.12.x ? > > Julien -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
