[ANNOUNCE] NSS 3.53 release

[JC Jones]

The NSS team released Network Security Services (NSS) 3.53 on 29 May 2020. NSS 3.53 will be a long-term support release, supporting Firefox 78 ESR.


The NSS team would like to recognize first-time contributors:

Jan-Marek Glogowski
Jeff Walden


The HG tag is NSS_3_53_RTM. NSS 3.53 requires NSPR 4.25 or newer.

NSS 3.53 source distributions are available on ftp.mozilla.org for secure HTTPS download:

Source tarballs:
https://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_53_RTM/src/


Notable Changes in NSS 3.53

* When using the Makefiles, NSS can be built in parallel, speeding up those builds to more similar performance as the build.sh/ninja/gyp system. (Bug 290526)

* SEED is now moved into a new freebl directory freebl/deprecated (Bug 1636389).

- SEED will be disabled by default in a future release of NSS. At that time, users will need to set the compile-time flag (Bug 1622033) to disable that deprecation in order to use the algorithm.

- Algorithms marked as deprecated will ultimately be removed.

* Several root certificates in the Mozilla program now set the CKA_NSS_SERVER_DISTRUST_AFTER attribute, which NSS consumers can query to further refine trust decisions. (Bug 1618404, Bug 1621159) If a builtin certificate has a CKA_NSS_SERVER_DISTRUST_AFTER timestamp before the SCT or NotBefore date of a certificate that builtin issued, then clients can elect not to trust it.
- This attribute provides a more graceful phase-out for certificate authorities than complete removal from the root certificate builtin store.


Bugs fixed in NSS 3.53

* Bug 1640260 - Initialize PBE params (ASAN fix)
* Bug 1618404 - Set CKA_NSS_SERVER_DISTRUST_AFTER for Symantec root certs
* Bug 1621159 - Set CKA_NSS_SERVER_DISTRUST_AFTER for Consorci AOC, GRCA, and SK ID root certs
* Bug 1629414 - PPC64: Correct compilation error between VMX vs. VSX vector instructions
* Bug 1639033 - Fix various compile warnings in NSS
* Bug 1640041 - Fix a null pointer in security/nss/lib/ssl/sslencode.c:67
* Bug 1640042 - Fix a null pointer in security/nss/lib/ssl/sslsock.c:4460
* Bug 1638289 - Avoid multiple definitions of SHA{256,384,512}_* symbols when linking libfreeblpriv3.so in Firefox on ppc64le
* Bug 1636389 - Relocate deprecated SEED algorithm
* Bug 1637083 - lib/ckfw: No such file or directory. Stop.
* Bug 1561331 - Additional modular inverse test
* Bug 1629553 - Rework and cleanup gmake builds
* Bug 1438431 - Remove mkdepend and "depend" make target
* Bug 290526 - Support parallel building of NSS when using the Makefiles
* Bug 1636206 - HACL* update after changes in libintvector.h
* Bug 1636058 - Fix building NSS on Debian s390x, mips64el, and riscv64
* Bug 1622033 - Add option to build without SEED


This Bugzilla query returns all the bugs fixed in NSS 3.53:

https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&classification=Components&query_format=advanced&product=NSS&target_milestone=3.53

NSS 3.53 shared libraries are backward compatible with all older NSS 3.x
shared libraries. A program linked with older NSS 3.x shared libraries will
work with NSS 3.51 shared libraries without recompiling or relinking.
Furthermore, applications that restrict their use of NSS APIs to the
functions listed in NSS Public Functions will remain compatible with future
versions of the NSS shared libraries.

Bugs discovered should be reported by filing a bug report with
bugzilla.mozilla.org (product NSS).

Please refer to the release notes for the complete list of changes:
https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.53_release_notes

[Robert Relyea]

On 6/1/20 5:18 PM, JC Jones wrote:
> The NSS team released Network Security Services (NSS) 3.53 on 29 May 2020. NSS 3.53 will be a long-term support release, supporting Firefox 78 ESR.

Looks like we updated certdata.txt without updating the version number
in nssckbi.h. This caused some problems because I pulled the 3.52
certdata.txt, but with 3.53 coming out I verified that version number
didn't change and didn't pick up the 3.53 change.

We need to make sure we bump the version number when we make changes.
Just a reminder for the future...

Fortunately our QA tests found this, and I had already pushed our
version number because I removed a bunch of expired certs (that weren't
explicitly marked as untrusted). I'll create a bug to remove those from
the upstream certdata.txt and that will put the versions in sync again.


bob

[Martin Thomson]

Is there an automated check we can run that will help us remember to
do this properly in future? I really don't like having to remember
this sort of thing.

> --
> dev-tech-crypto mailing list
> dev-tec...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-tech-crypto

[Robert Relyea]

On 6/10/20 10:48 PM, Martin Thomson wrote:
> Is there an automated check we can run that will help us remember to
> do this properly in future? I really don't like having to remember
> this sort of thing.

There isn't, which is why it happened, I think we should have one
though, where would be the best place to put it? nss/automation?

bob

[Martin Thomson]

On Fri, Jun 12, 2020 at 1:16 AM Robert Relyea <rre...@redhat.com> wrote:
>
> On 6/10/20 10:48 PM, Martin Thomson wrote:
> > Is there an automated check we can run that will help us remember to
> > do this properly in future? I really don't like having to remember
> > this sort of thing.
>
>
> There isn't, which is why it happened, I think we should have one
> though, where would be the best place to put it? nss/automation?

Any of our unit tests runners could catch this, it's a fairly cheap
thing to check on.