-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Low
-
sst_security_special_projects
-
ssg_security
-
20
-
None
-
False
-
-
None
-
None
-
None
-
None
-
If docs needed, set a value
-
-
All
-
None
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:
