Bug 139110 - rhnreg_ks improperly deals with --sslCACert command line option
Summary: rhnreg_ks improperly deals with --sslCACert command line option
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: up2date
Version: 2.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Bret McMillan
QA Contact: Red Hat Satellite QA List
Depends On:
Blocks: 106771
TreeView+ depends on / blocked
Reported: 2004-11-12 23:06 UTC by Ian McLeod
Modified: 2007-11-30 22:06 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2007-10-19 19:21:28 UTC

Attachments (Terms of Use)

Description Ian McLeod 2004-11-12 23:06:02 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1)

Description of problem:
Summary: rhnreg_ks fails when I attempt to point it at a custom CA
cert for registration against a satellite.  It correctly sets this
cert in the rhn_register config file, but uses the default Red Hat
cert when attempting to contact the satellite.  If I run the same
command a second time, the registration works.

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

How reproducible:

Steps to Reproduce:
Delete the rhn_register config file.

Attempt to forcibly reregister against a satellite using rhnreg_ks.

Registration must use a token and the server must use a custom CA cert.


Actual Results:  Registration fails with a "Cannot validate apache SSL
cert" error.

Expected Results:  Server should register.

Additional info:

Comment 1 RHEL Product and Program Management 2007-10-19 19:21:28 UTC
This bug is filed against RHEL2.1, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products.  Since
this bug does not meet that criteria, it is now being closed.

For more information of the RHEL errata support policy, please visit:

If you feel this bug is indeed mission critical, please contact your
support representative.  You may be asked to provide detailed
information on how this bug is affecting you.

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