The CHACHA20-POLY1305 algorithm is specified in rfc7539, and is being adopted by TLS 1.3 and IPSec (rfc7634). It is becoming the de-facto backup algorithm of AES-GCM (implemented in all major browsers), and is being included into all major crypto libraries.
We should include chacha20-poly1305 in RHEL7 when possible.
Does this inclusion require a change to nss-softokn?
If yes, this cannot be done for RHEL 7.3, where nss-softokn is currently expected to remain frozen.
We have full flexibility for RHEL 7.4, which is expected to rebase all of NSS, including nss-softokn.
Upstream NSS has support ChaCha for TLS since upstream release NSS 3.25, and I see that code with that name has been added to the NSS freebl and softokn directories.
We intend to rebase RHEL 7.4 to version NSS 3.28, because it will be required for Firefox 52.
Based on current releases schedules, NSS 3.28 should be ready by mid November.
Bob, can we assume that the upstream NSS implementation of ChaCha is sufficiently complete to satisfy Nikos' expectations?
Is there anything necessary to verify/test the upstream implementation, that should be done prior to the release of NSS 3.28 mid November?
Assigning to Daiki, as this will likely be covered by the expected rebase.
The upstream implementation should be sufficient.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.