Bug 1126588

Summary:	Anaconda uses sha1 instead of sha2 hashes
Product:	[Fedora] Fedora	Reporter:	dcomrie <drcomrie>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	20	CC:	anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-04 20:45:07 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 dcomrie 2014-08-04 20:42:58 UTC

Description of problem:

Anaconda is using sha1 hashes instead of the more secure sha2.

Version-Release number of selected component (if applicable):

The version that is shipped with the Fedora 20 iso.

How reproducible:

Very.

Steps to Reproduce:
1.Run anaconda
2.Install with LVM/LUKS
3.do a luksDump on the encrypted partition

Actual results:

Version:        1
Cipher name:    aes
Cipher mode:    xts-plain64
Hash spec:      sha1
Payload offset: 4096
MK bits:        512

Expected results:

Version:        1
Cipher name:    aes
Cipher mode:    xts-plain64
Hash spec:      sha256 <-- or sha512
Payload offset: 4096
MK bits:        512


Additional info:

Comment 1 David Shea 2014-08-04 20:45:07 UTC


*** This bug has been marked as a duplicate of bug 1096530 ***