Bug 1168948 - Satellite doesn't install in FIPS mode
Summary: Satellite doesn't install in FIPS mode
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Installer
Version: 570
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matej Kollar
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: sat570-triage
TreeView+ depends on / blocked
 
Reported: 2014-11-28 13:55 UTC by Pavel Studeník
Modified: 2015-07-26 22:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-28 14:07:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.