RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1373158 (rhel7-chacha20-nss) - CHACHA20-POLY1305 in NSS
Summary: CHACHA20-POLY1305 in NSS
Keywords:
Status: CLOSED ERRATA
Alias: rhel7-chacha20-nss
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nss-softokn
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Daiki Ueno
QA Contact: Hubert Kario
Mirek Jahoda
URL:
Whiteboard:
Depends On: 1369055
Blocks: 1371038 1373157 1377248
TreeView+ depends on / blocked
 
Reported: 2016-09-05 11:33 UTC by Nikos Mavrogiannopoulos
Modified: 2017-08-01 16:47 UTC (History)
7 users (show)

Fixed In Version: nss-softokn-3.28.3-2.el7
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 16:47:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 1354152 0 -- RESOLVED Big Chacha20 records are not rejected by server 2020-01-29 17:13:11 UTC
Red Hat Product Errata RHEA-2017:1977 0 normal SHIPPED_LIVE nss bug fix and enhancement update 2017-08-01 17:57:47 UTC

Comment 1 Nikos Mavrogiannopoulos 2016-09-05 11:34:04 UTC 
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.
Comment 3 Kai Engert (:kaie) (inactive account) 2016-09-28 18:42:06 UTC 
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.
Comment 4 Kai Engert (:kaie) (inactive account) 2016-09-28 18:43:24 UTC 
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?
Comment 5 Kai Engert (:kaie) (inactive account) 2016-09-28 18:44:08 UTC 
Assigning to Daiki, as this will likely be covered by the expected rebase.
Comment 6 Bob Relyea 2016-09-28 22:54:31 UTC 
The upstream implementation should be sufficient.
Comment 20 errata-xmlrpc 2017-08-01 16:47:42 UTC 
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.

https://access.redhat.com/errata/RHEA-2017:1977
Note You need to log in before you can comment on or make changes to this bug.