Source code
Revision control
Copy as Markdown
Other Tools
.. _mozilla_projects_nss_nss_3_48_release_notes:
NSS 3.48 release notes
======================
`Introduction <#introduction>`__
--------------------------------
.. container::
The NSS team has released Network Security Services (NSS) 3.48 on **5 December 2019**, which is a
minor release.
The NSS team would like to recognize first-time contributors:
- Craig Disselkoen
- Giulio Benetti
- Lauri Kasanen
- Tom Prince
`Distribution Information <#distribution_information>`__
--------------------------------------------------------
.. container::
The HG tag is NSS_3_48_RTM. NSS 3.48 requires NSPR 4.24 or newer.
NSS 3.48 source distributions are available on ftp.mozilla.org for secure HTTPS download:
- Source tarballs:
Other releases are available :ref:`mozilla_projects_nss_nss_releases`.
.. _notable_changes_in_nss_3.48:
`Notable Changes in NSS 3.48 <#notable_changes_in_nss_3.48>`__
--------------------------------------------------------------
.. container::
details.
default, where possible. See `Bug
- The master password PBE now uses 10,000 iterations by default when using the default sql
(key4.db) storage. Because using an iteration count higher than 1 with the legacy dbm
(key3.db) storage creates files that are incompatible with previous versions of NSS,
applications that wish to enable it for key3.db are required to set environment variable
NSS_ALLOW_LEGACY_DBM_ITERATION_COUNT=1. Applications may set environment variable
NSS_MIN_MP_PBE_ITERATION_COUNT to request a higher iteration count than the library's default,
or NSS_MAX_MP_PBE_ITERATION_COUNT to request a lower iteration count for test environments.
.. _certificate_authority_changes:
`Certificate Authority Changes <#certificate_authority_changes>`__
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. container::
- The following CA certificates were Added:
Certification Authority - G4 Cert
- SHA-256 Fingerprint: DB3517D1F6732A2D5AB97C533EC70779EE3270A62FB4AC4238372460E6F01E88
.. _upcoming_changes_in_nss_3.49:
`Upcoming Changes in NSS 3.49 <#upcoming_changes_in_nss_3.49>`__
----------------------------------------------------------------
.. container::
- The legacy DBM database, **libnssdbm**, will no longer be built by default. See `Bug
.. _bugs_fixed_in_nss_3.48:
`Bugs fixed in NSS 3.48 <#bugs_fixed_in_nss_3.48>`__
----------------------------------------------------
.. container::
NSS 3.48
self-encrypt functions
test for early Key Update
nssCKFWObject_GetAttributeSize
Certification Authority - G4 certificate to NSS
of versions lower than 1.3 after HelloRetryRequest
and unified MAC implementation for HMAC and CMAC behind PKCS#11
Pro performance workaround
known-answer-test scripts
use maxout not block size (CVE-2019-11745)
similar "beginning-of-validity-period" parameter to
mozilla::pkix::TrustDomain::CheckRevocation
leak in NSC_GenerateKey if key length > MAX_KEY_LEN (256)
ctr_xor
disabled in TLS 1.2
friendly if it implements CKP_PUBLIC_CERTIFICATES_TOKEN
Acceleration
PR_ASSERT_ARG in certdb.c
PK11_MakeCertFromHandle
is valid before usage from PKCS#11
gtests in NSS CI
length in constant time
default iteration count, by default for modern key4 storage, optionally for legacy key3.db
storage
than -std=gnu99
doesn't support NEON
master secret by default
incomplete coverage
-Wmaybe-uninitialized warning in tls13esni.c
Delegated Credential key strength checks
tests that missed NSS 3.47
btoa.c
variable warnings from certdata.perl
default in NSS
This Bugzilla query returns all the bugs fixed in NSS 3.48:
`Compatibility <#compatibility>`__
----------------------------------
.. container::
NSS 3.48 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.48 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.
`Feedback <#feedback>`__
------------------------
.. container::
Bugs discovered should be reported by filing a bug report with