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.
DescriptionNalin Dahyabhai
2012-06-25 20:10:53 UTC
Description of problem:
Starting with development versions of certmonger leading up to 0.58, certmonger is going to gain the ability to talk directly to Dogtag servers. The policy currently denies its attempts to do so.
Version-Release number of selected component (if applicable):
selinux-policy-3.7.19-155.el6_3.noarch
How reproducible:
Always
Steps to Reproduce:
1. Install ipa-server and its dependencies.
2. Use ipa-server-install to set up the server.
3. Run "getcert start-tracking -d /etc/httpd/alias -n Signing-Cert -c dogtag-ipa-renew-agent -p /etc/httpd/alias/pwdfile.txt" to tell certmonger about the certificate.
4. Run "getcert list -c dogtag-ipa-renew-agent" to check on the certificate's lifetime.
5. Run "getcert resubmit -d /etc/httpd/alias -n Signing-Cert" to tell certmonger to attempt to renew the certificate.
6. Run "getcert list -c dogtag-ipa-renew-agent" again to check if you managed to get yourself a new certificate.
Actual results:
The enrollment client fails to contact the server, and the client goes back to monitoring the certificate that it already had. It generates these AVC messages while I temporarily flip to permissive mode and try it again:
type=SYSCALL msg=audit(1340643217.213:64474): arch=c000003e syscall=42 success=no exit=-115 a0=3 a1=7fff6e012d20 a2=10 a3=7fff6e012930 items=0 ppid=6983 pid=7261 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=153 comm="dogtag-ipa-rene" exe="/usr/libexec/certmonger/dogtag-ipa-renew-agent-submit" subj=unconfined_u:system_r:certmonger_t:s0 key=(null)
type=AVC msg=audit(1340643217.213:64474): avc: denied { name_connect } for pid=7261 comm="dogtag-ipa-rene" dest=9180 scontext=unconfined_u:system_r:certmonger_t:s0 tcontext=system_u:object_r:pki_ca_port_t:s0 tclass=tcp_socket
Expected results:
Success, with the second run of "getcert list" showing that the newly-issued certificate will last that much longer than the old one would have.
Additional information:
Similar changes will be needed in other releases where we include the certmonger package (Fedora, perhaps EL 5), as support for acting as a client for Dogtag will be included whenever we update the package for those releases.
Comment 3RHEL Program Management
2012-07-10 06:31:36 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 4RHEL Program Management
2012-07-11 01:57:10 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
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.
http://rhn.redhat.com/errata/RHBA-2013-0314.html
Description of problem: Starting with development versions of certmonger leading up to 0.58, certmonger is going to gain the ability to talk directly to Dogtag servers. The policy currently denies its attempts to do so. Version-Release number of selected component (if applicable): selinux-policy-3.7.19-155.el6_3.noarch How reproducible: Always Steps to Reproduce: 1. Install ipa-server and its dependencies. 2. Use ipa-server-install to set up the server. 3. Run "getcert start-tracking -d /etc/httpd/alias -n Signing-Cert -c dogtag-ipa-renew-agent -p /etc/httpd/alias/pwdfile.txt" to tell certmonger about the certificate. 4. Run "getcert list -c dogtag-ipa-renew-agent" to check on the certificate's lifetime. 5. Run "getcert resubmit -d /etc/httpd/alias -n Signing-Cert" to tell certmonger to attempt to renew the certificate. 6. Run "getcert list -c dogtag-ipa-renew-agent" again to check if you managed to get yourself a new certificate. Actual results: The enrollment client fails to contact the server, and the client goes back to monitoring the certificate that it already had. It generates these AVC messages while I temporarily flip to permissive mode and try it again: type=SYSCALL msg=audit(1340643217.213:64474): arch=c000003e syscall=42 success=no exit=-115 a0=3 a1=7fff6e012d20 a2=10 a3=7fff6e012930 items=0 ppid=6983 pid=7261 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=153 comm="dogtag-ipa-rene" exe="/usr/libexec/certmonger/dogtag-ipa-renew-agent-submit" subj=unconfined_u:system_r:certmonger_t:s0 key=(null) type=AVC msg=audit(1340643217.213:64474): avc: denied { name_connect } for pid=7261 comm="dogtag-ipa-rene" dest=9180 scontext=unconfined_u:system_r:certmonger_t:s0 tcontext=system_u:object_r:pki_ca_port_t:s0 tclass=tcp_socket Expected results: Success, with the second run of "getcert list" showing that the newly-issued certificate will last that much longer than the old one would have. Additional information: Similar changes will be needed in other releases where we include the certmonger package (Fedora, perhaps EL 5), as support for acting as a client for Dogtag will be included whenever we update the package for those releases.