Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionAmar Huchchanavar
2018-12-14 14:40:08 UTC
Description of problem:
'katello-certs-check' succeeds if the server cert has CN=shortname.
We recommend Satellite configuration with FQDN and if customer tries to configure custom certs with short-name it creates lot of issues.
Version-Release number of selected component (if applicable):
Satellite 6 All versions.
How reproducible:
Always
Steps to Reproduce:
1.Gnerate/get certs with satellite's shortname.
2.Perfrom katello-certs-check.
Actual results:
It succeeds.
Expected results:
It should display a warining message.
or
It should fail.
Additional info:
>/usr/sbin/katello-certs-check
~~~~
function check-ca-bundle () {
printf "Checking CA bundle against the certificate file: "
CHECK=$(openssl verify -CAfile $CA_BUNDLE_FILE -purpose sslserver -verbose $CERT_FILE 2>&1) <<<
if [ $? == "0" ]; then
success
else
error 4 "The $CA_BUNDLE_FILE does not verify the $CERT_FILE"
echo $CHECK
fi
}
~~~
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
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 (Moderate: Satellite 6.9 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2021:1313
Description of problem: 'katello-certs-check' succeeds if the server cert has CN=shortname. We recommend Satellite configuration with FQDN and if customer tries to configure custom certs with short-name it creates lot of issues. Version-Release number of selected component (if applicable): Satellite 6 All versions. How reproducible: Always Steps to Reproduce: 1.Gnerate/get certs with satellite's shortname. 2.Perfrom katello-certs-check. Actual results: It succeeds. Expected results: It should display a warining message. or It should fail. Additional info: >/usr/sbin/katello-certs-check ~~~~ function check-ca-bundle () { printf "Checking CA bundle against the certificate file: " CHECK=$(openssl verify -CAfile $CA_BUNDLE_FILE -purpose sslserver -verbose $CERT_FILE 2>&1) <<< if [ $? == "0" ]; then success else error 4 "The $CA_BUNDLE_FILE does not verify the $CERT_FILE" echo $CHECK fi } ~~~