Bug 2159736

Summary:	avoid “Warning: Value 512 is outside of the allowed entropy range, adjusting it.”
Product:	Red Hat Enterprise Linux 8	Reporter:	Martin Zelený <mzeleny>
Component:	clevis	Assignee:	Sergio Arroutbi <sarroutb>
Status:	CLOSED ERRATA	QA Contact:	Martin Zelený <mzeleny>
Severity:	medium	Docs Contact:	Jan Fiala <jafiala>
Priority:	unspecified
Version:	8.8	CC:	dapospis, jafiala, qe-baseos-security, sarroutb, scorreia
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	clevis-15-13.el8	Doc Type:	Bug Fix
Doc Text:	.Clevis no longer requests too much entropy from `pwmake` Previously, the `pwmake` password generation utility displayed unwanted warnings when Clevis used `pwmake` to create passwords for storing data in `LUKS` metadata, which caused Clevis to use lower entropy. With this update, Clevis is limited to 256 entropy bits provided to `pwmake`, which eliminates an unwanted warning and uses the correct amount of entropy.	Story Points:	---
Clone Of:	2159735	Environment:
Last Closed:	2023-05-16 08:39:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2159735
Bug Blocks:

Description Martin Zelený 2023-01-10 14:42:45 UTC

+++ This bug was initially created as a clone of Bug #2159735 +++

Backport commit [1] from upstream PR:

luks: define max entropy bits for pwmake

So that we don't get a warning about using a value outside the allowed
entropy range, when generating a new passphrase.

Update existing documentation that mentions entropy to list the
limitation of 256 bits.

[1] https://github.com/latchset/clevis/pull/338/commits/49401c27e018d4fbf61e40e9f63b1bfc5d5ca46f

Comment 15 errata-xmlrpc 2023-05-16 08:39:14 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 (clevis bug fix and enhancement update), 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/RHBA-2023:2868