Bug 713410

Summary:	Move "Running in FIPS mode." to more verbose level to not break scripts
Product:	Red Hat Enterprise Linux 6	Reporter:	Milan Broz <mbroz>
Component:	cryptsetup-luks	Assignee:	Milan Broz <mbroz>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.1	CC:	agk, atodorov, mbroz, prajnoha, prockai, pvrabec, zkabelac
Target Milestone:	rc	Keywords:	Regression, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cryptsetup-luks-1.2.0-5.el6	Doc Type:	Bug Fix
Doc Text:	When the cryptsetup or libcryptsetup utility was run in FIPS (Federal Information Processing Standards) mode, the "Running in FIPS mode." message was displayed during initialization of all commands. This sometimes caused minor issues with associated scripts. This bug has been fixed and the message is now displayed only in verbose mode.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-06 17:02:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	661821, 713456

Description Milan Broz 2011-06-15 10:36:43 UTC

Description of problem:
If system is in FIPS mode "Running in FIPS mode." message is always displayed
when runnit cryptsetup (or libcryptsetup).

This message could break scripts (it appears even in status commands.)

Version-Release number of selected component (if applicable):
cryptsetup-luks-1.2.0-3.el6

Change is trivial.

Comment 5 Milan Broz 2011-06-15 13:01:21 UTC

Fixed in cryptsetup-luks-1.2.0-5.el6.

Comment 7 Tomas Capek 2011-06-17 12:37:06 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When the cryptsetup or libcryptsetup utility was run in FIPS (Federal Information Processing Standards) mode, the "Running in FIPS mode." message was displayed during initialization of all commands. This sometimes caused minor issues with associated scripts. This bug has been fixed and the message is now displayed only in verbose mode.

Comment 9 Alexander Todorov 2011-08-11 10:55:27 UTC

# rpm -q cryptsetup-luks
cryptsetup-luks-1.2.0-5.el6.x86_64

# cryptsetup status luks-df0be28a-b130-465a-8e16-a49b204aa0fd
/dev/mapper/luks-df0be28a-b130-465a-8e16-a49b204aa0fd is active and is in use.
  type:  LUKS1
  cipher:  aes-xts-plain64
  keysize: 512 bits
  device:  /dev/vda2
  offset:  4096 sectors
  size:    15747072 sectors
  mode:    read/write

# cryptsetup -v status luks-df0be28a-b130-465a-8e16-a49b204aa0fd
/dev/mapper/luks-df0be28a-b130-465a-8e16-a49b204aa0fd is active and is in use.
Running in FIPS mode.
  type:  LUKS1
  cipher:  aes-xts-plain64
  keysize: 512 bits
  device:  /dev/vda2
  offset:  4096 sectors
  size:    15747072 sectors
  mode:    read/write
Command successful.

Running in FIPS mode is printed only in verbose mode.

Comment 10 errata-xmlrpc 2011-12-06 17:02:30 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1688.html