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

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

Description of problem:

Certmonger's getcert command provides a flag -C that runs a command after a certificate is downloaded.

This command is run after the certificate is written to disk, but before the root certificate is written to disk.

It makes more sense to write after both have been written.

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

latest (and before)
certmonger-0.75.13-0.20140818T1524Zgit0ed42b6.el6.x86_64

How reproducible:

Always

Steps to Reproduce:

1. ipa-getcert -k service.key -f service.cert -F root.cert -C "chmod 644 `pwd`/service.cert `pwd`/root.cert"
2. ls -l root.cert

Actual results:
-rw-------. 1 root root 3185 Jul 21 20:23 root.cer

Expected results:

-rw-r--r--. 1 root root 3185 Jul 21 20:23 root.cer

Additional info:

Fixed upstream in 0.76.3, so we can fix it here by rebasing.

Verified.

certmonger version:
===================
[root@dhcp207-115 certtest]# rpm -q certmonger ipa-server
certmonger-0.78.4-1.el7.x86_64
ipa-server-4.2.0-13.el7.x86_64
[root@dhcp207-115 certtest]# 

console output:
===============
[root@dhcp207-115 ~]# ipa-getcert request -k /tmp/certtest/service.key -f /tmp/certtest/service.cert -F /tmp/certtest/root.cert -C "chmod 644 /tmp/certtest/service.cert /tmp/certtest/root.cert"
New signing request "20151012081159" added.
[root@dhcp207-115 ~]# cd /tmp/certtest/
[root@dhcp207-115 certtest]# ls
root.cert  service.cert  service.key
[root@dhcp207-115 certtest]# ls -la root.cert 
-rw-r--r--. 1 root root 1310 Oct 12 13:42 root.cert
[root@dhcp207-115 certtest]#

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.

https://rhn.redhat.com/errata/RHBA-2015-2365.html