Bug 1252936 - nettle: sha3 implementation does not conform to the published version
Summary: nettle: sha3 implementation does not conform to the published version
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nettle
Version: 7.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Nikos Mavrogiannopoulos
QA Contact: Hubert Kario
Mirek Jahoda
Depends On:
Blocks: 1296594 1313485 1297572 1298279
TreeView+ depends on / blocked
Reported: 2015-08-12 14:30 UTC by Nikos Mavrogiannopoulos
Modified: 2016-11-03 19:30 UTC (History)
2 users (show)

Fixed In Version: nettle-2.7.1-5.el7
Doc Type: Enhancement
Doc Text:
The SHA-3 implementation in _nettle_ now conforms to FIPS 202 _nettle_ is a cryptographic library that is designed to fit easily in almost any context. With this update, the Secure Hash Algorithm 3 (SHA-3) implementation has been updated to conform the final Federal Information Processing Standard (FIPS) 202 draft.
Clone Of:
: 1298465 (view as bug list)
Last Closed: 2016-11-03 19:30:44 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1252935 0 unspecified CLOSED nettle: sha3 implementation does not conform to the published version 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2016:2582 0 normal SHIPPED_LIVE Moderate: nettle security and bug fix update 2016-11-03 12:08:24 UTC

Description Nikos Mavrogiannopoulos 2015-08-12 14:30:00 UTC
Description of problem:
The final version of SHA3 [0] does not match the original accepted version of keccak. The changes are trivial but nevertheless result to incompatible results [1].

[0]. http://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.202.pdf
[1]. https://en.wikipedia.org/wiki/SHA-3#Examples_of_SHA-3_and_Keccak_variants

Comment 9 errata-xmlrpc 2016-11-03 19:30:44 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.


Note You need to log in before you can comment on or make changes to this bug.