Red Hat Bugzilla – Bug 857482
new rule needed for certmonger to access dogtag 10 ports
Last modified: 2012-12-20 11:07:41 EST
Description of problem: certmonger talks to dogtag on the dogtag ports. In dogtag 10, though, we will be using standard tomcat ports - which means some new rules are needed to allow this access. We plan to release dogtag 10 on f18+. However, many people are testing dogtag 10 on f17 using developer builds, and there is no harm in adding the rule there too. corenet_tcp_connect_http_cache_port(certmonger_t) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Fixed in selinux-policy-3.11.1-23.fc18.noarch
selinux-policy-3.11.1-25.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/selinux-policy-3.11.1-25.fc18
Package selinux-policy-3.11.1-25.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.11.1-25.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14807/selinux-policy-3.11.1-25.fc18 then log in and leave karma (feedback).
selinux-policy-3.11.1-25.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.