Bug 1785748

Summary:	Expose crypt_safe_free in libcryptsetup public API
Product:	Red Hat Enterprise Linux 8	Reporter:	Dennis Keefe <dkeefe>
Component:	cryptsetup	Assignee:	Ondrej Kozina <okozina>
Status:	CLOSED ERRATA	QA Contact:	guazhang <guazhang>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.3	CC:	agk, guazhang, jbrassow, mbroz, okozina, prajnoha
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cryptsetup-2.3.3-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-04 01:59:39 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:	1796826
Bug Blocks:	1825061

Description Dennis Keefe 2019-12-20 20:48:09 UTC

Please expose crypt_safe_free in libcryptsetup public API in RHEL 8.3

Here is the Stratis PR

https://github.com/stratis-storage/project/issues/85

Comment 2 guazhang@redhat.com 2020-01-10 02:38:02 UTC

Hello

Could you share some test steps for the bug?

thanks 
guazhang

Comment 3 Ondrej Kozina 2020-01-13 14:36:52 UTC

Fixed with upstream commit: https://gitlab.com/cryptsetup/cryptsetup/commit/b03cb3f3d84069cffc6f8a147cedef7b6af5a5e5

Comment 4 Ondrej Kozina 2020-01-14 11:00:02 UTC

This can't be tested from command line interface.

Simplest test from my perspective would be to write very minimal C program that would link with libcryptsetup and try to use one of following symbols:

crypt_safe_alloc
crypt_safe_free
crypt_safe_realloc
crypt_safe_memzero

Description for those symbols and usage will be in libcryptsetup.h in cryptsetup-devel package in release cryptsetup-2.3.0-1.el8 or later.

Comment 7 guazhang@redhat.com 2020-06-18 08:14:40 UTC

Hello

Did code review and verified patches applied correctly on cryptsetup-2.3.3-1.el8, and no regression found. so will moved to "VERIFIED"

Comment 10 errata-xmlrpc 2020-11-04 01:59:39 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 (Moderate: cryptsetup security, 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/RHSA-2020:4542