Bug 2227089

Summary:	[RFE] clevis slot reports sha256 value even though it has been formatted with sha512
Product:	Red Hat Enterprise Linux 9	Reporter:	Chetan <cjain>
Component:	clevis	Assignee:	Sergio Arroutbi <sarroutb>
Status:	CLOSED MIGRATED	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	dapospis, rmadhuso, sarroutb
Target Milestone:	rc	Keywords:	FutureFeature, MigratedToJIRA, Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-01 13:01:20 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:

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