Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1168948

Summary:	Satellite doesn't install in FIPS mode
Product:	Red Hat Satellite 5	Reporter:	Pavel Studeník <pstudeni>
Component:	Installer	Assignee:	Matej Kollar <mkollar>
Status:	CLOSED NOTABUG	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	570	CC:	cperry
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-11-28 14:07:34 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:
Bug Depends On:
Bug Blocks:	1127217

Description Pavel Studeník 2014-11-28 13:55:02 UTC

Description of problem:
I try to install satellite on system with FIPS mode. During verifying certificate I get error "Could not parse certificate file."


Version-Release number of selected component (if applicable):
spacewalk-setup-2.3.0-9.el6sat.noarch

How reproducible:
always

Steps to Reproduce:
1. set FIPS mode on system
2. try to install satellite 5.7

Actual results:

>> install.pl --disconnected

** Loading Red Hat Satellite Certificate.
** Verifying certificate locally.
There was a problem activating the satellite: Could not parse certificate file.

>> tail ../rhn/rhn_installation.log
Red Hat Satellite Entitlement Certificate failed to validate.
MORE INFORMATION:
  Return value: 3
  Standard-out: Error: Your satellite certificate signature is not valid.  Please contact your support representative.

  Standard-error: DBG: md_enable: algorithm 3 not available
gpg: Digest algorithm not available probably due to FIPS mode.


ERROR: RHN Entitlement Certificate failed to validate.

Comment 1 Pavel Studeník 2014-11-28 14:07:34 UTC

Certification must be sign newer PGP

correct:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

incorrect old version:
-----BEGIN PGP SIGNATURE-----
Version: Crypt::OpenPGP 1.03