Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

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

Hello

Could you share some test steps for the bug?

thanks 
guazhang

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

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.

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"

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