Bug 709055 - libcryptsetup crypt_get_volume_key() should be disabled in FIPS mode
Summary: libcryptsetup crypt_get_volume_key() should be disabled in FIPS mode
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cryptsetup-luks
Version: 6.1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Milan Broz
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On: 701936
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-30 13:35 UTC by RHEL Program Management
Modified: 2013-03-01 04:10 UTC (History)
13 users (show)

Fixed In Version: cryptsetup-luks-1.2.0-3.el6_1.1
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-20 07:09:27 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0884 0 normal SHIPPED_LIVE cryptsetup-luks bug fix update 2011-06-20 07:09:22 UTC

Description RHEL Program Management 2011-05-30 13:35:51 UTC 
This bug has been copied from bug #701936 and has been proposed
to be backported to 6.1 z-stream (EUS).
Comment 3 Milan Broz 2011-06-02 12:19:47 UTC 
Fix in  cryptsetup-luks-1.2.0-3.el6_1.1.
Comment 4 Alexander Todorov 2011-06-03 09:11:32 UTC 
Per https://bugzilla.redhat.com/show_bug.cgi?id=701936#c15

# rpm -q cryptsetup-luks
cryptsetup-luks-1.2.0-3.el6_1.1.x86_64


# cryptsetup luksDump --dump-master-key /dev/vda2
Running in FIPS mode.

WARNING!
========
LUKS header dump with volume key is sensitive information
which allows access to encrypted partition without passphrase.
This dump should be always stored encrypted on safe place.

Are you sure? (Type uppercase yes): YES
Enter LUKS passphrase: 
Function not available in FIPS mode.
Comment 5 errata-xmlrpc 2011-06-20 07:09:27 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0884.html
Note You need to log in before you can comment on or make changes to this bug.