This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2227089 - [RFE] clevis slot reports sha256 value even though it has been formatted with sha512
Summary: [RFE] clevis slot reports sha256 value even though it has been formatted with...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: clevis
Version: unspecified
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Sergio Arroutbi
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-27 19:06 UTC by Chetan
Modified: 2023-08-01 13:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-01 13:01:20 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-944 0 None None None 2023-08-01 13:01:19 UTC
Red Hat Issue Tracker RHELPLAN-163715 0 None None None 2023-07-27 19:07:23 UTC
Red Hat Issue Tracker SECENGSP-5328 0 None None None 2023-07-27 19:07:28 UTC

Description Chetan 2023-07-27 19:06:43 UTC 
Description of problem: clevis slot reports sha256 value even though it has been formatted with sha512


Version-Release number of selected component (if applicable):
clevis-18-110.el9.x86_64  

How reproducible:
100% Reproducible

Steps to Reproduce:
1. Format the device with Sha512 as a hash value
2. Try to bind the device with tpm/tang for auto decryption
3. After binding, Check the Hash value in the #luksDump command 

Actual results:
It reports the incorrect (or default) hash value


Expected results:
Show the hash value which was used while formatting the device

Additional info:
Comment 3 Sergio Arroutbi 2023-08-01 11:51:36 UTC 
This bug is going to be migrated.

Contact point for migration questions or issues: rsroka
Guidance for Bugzilla users to test their Jira account or create one if needed:

https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016394
https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016694
https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016774
Note You need to log in before you can comment on or make changes to this bug.