Description of problem: Let's Encrypt client writes its certificates to /etc/letsencrypt/(archive|live)(/.*)? (symlink from live into archive). This currently gets the standard etc_t type which httpd/nginx is not permitted to read. For now I'm going to advise users in the configuration docs for LE to add this context to this path but to have things working out of the box it'd be beneficial to label that regex as cert_t Version-Release number of selected component (if applicable): selinux-policy-3.13.1-155.fc23.noarch How reproducible: Every time Steps to Reproduce: 1. Install letsencrypt 2. Request a certificate for a domain (note this step requires a public facing webserver): letsencrypt --text --email recovery \ --domains www.example.com,example.com,foo.example.com \ --agree-tos --webroot --renew-by-default --webroot-path/var/www/html certonly 3. ls -lZ /etc/letsencrypt/{archive,live}/ Actual results: [root@server ~]# ls -lZ /etc/letsencrypt/{archive,live}/* /etc/letsencrypt/archive/www.example.com: total 16 -rw-r--r--. 1 root root unconfined_u:object_r:etc_t:s0 1801 Dec 8 16:46 cert1.pem -rw-r--r--. 1 root root unconfined_u:object_r:etc_t:s0 1675 Dec 8 16:46 chain1.pem -rw-r--r--. 1 root root unconfined_u:object_r:etc_t:s0 3476 Dec 8 16:46 fullchain1.pem -rw-r--r--. 1 root root unconfined_u:object_r:etc_t:s0 1704 Dec 8 16:46 privkey1.pem /etc/letsencrypt/live/www.example.com: total 0 lrwxrwxrwx. 1 root root unconfined_u:object_r:etc_t:s0 41 Dec 8 16:46 cert.pem -> ../../archive/www.example.com/cert1.pem lrwxrwxrwx. 1 root root unconfined_u:object_r:etc_t:s0 42 Dec 8 16:46 chain.pem -> ../../archive/www.example.com/chain1.pem lrwxrwxrwx. 1 root root unconfined_u:object_r:etc_t:s0 46 Dec 8 16:46 fullchain.pem -> ../../archive/www.example.com/fullchain1.pem lrwxrwxrwx. 1 root root unconfined_u:object_r:etc_t:s0 44 Dec 8 16:46 privkey.pem -> ../../archive/www.example.com/privkey1.pem Expected results: [root@server ~]# ls -lZ /etc/letsencrypt/{archive,live}/* /etc/letsencrypt/archive/www.example.com: total 16 -rw-r--r--. 1 root root unconfined_u:object_r:cert_t:s0 1801 Dec 8 16:46 cert1.pem -rw-r--r--. 1 root root unconfined_u:object_r:cert_t:s0 1675 Dec 8 16:46 chain1.pem -rw-r--r--. 1 root root unconfined_u:object_r:cert_t:s0 3476 Dec 8 16:46 fullchain1.pem -rw-r--r--. 1 root root unconfined_u:object_r:cert_t:s0 1704 Dec 8 16:46 privkey1.pem /etc/letsencrypt/live/www.example.com: total 0 lrwxrwxrwx. 1 root root unconfined_u:object_r:cert_t:s0 41 Dec 8 16:46 cert.pem -> ../../archive/www.example.com/cert1.pem lrwxrwxrwx. 1 root root unconfined_u:object_r:cert_t:s0 42 Dec 8 16:46 chain.pem -> ../../archive/www.example.com/chain1.pem lrwxrwxrwx. 1 root root unconfined_u:object_r:cert_t:s0 46 Dec 8 16:46 fullchain.pem -> ../../archive/www.example.com/fullchain1.pem lrwxrwxrwx. 1 root root unconfined_u:object_r:cert_t:s0 44 Dec 8 16:46 privkey.pem -> ../../archive/www.example.com/privkey1.pem Additional info: This of course affects rawhide as well Of course I could just add the semanage and restorecon in a %post in letsencrypt but it feels like it would be better to have it upstream and not as a local customization.
Actually checking sesearch -A -s httpd_t -t etc_t on F23 I think it *can* read etc_t fine as a base type so this bug isn't quite right in it's specific initial thought process... Rather the certificates should be cert_t to prevent *other* things from reading them incorrectly. So the title is right and the end goal is the same ;)
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Policy to apply this is in this PR: https://github.com/fedora-selinux/selinux-policy/pull/194
certbot-0.12.0-3.fc24 python-acme-0.12.0-3.fc24 python-certbot-apache-0.12.0-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-0b35be64b3
certbot-0.12.0-3.fc25 python-acme-0.12.0-3.fc25 python-certbot-apache-0.12.0-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-e06b5ed81c
certbot-0.12.0-3.el7 python-acme-0.12.0-2.el7 python-certbot-apache-0.12.0-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-7036057408
certbot-0.12.0-3.fc25, python-acme-0.12.0-3.fc25, python-certbot-apache-0.12.0-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-e06b5ed81c
certbot-0.12.0-3.el7, python-acme-0.12.0-2.el7, python-certbot-apache-0.12.0-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-7036057408
certbot-0.12.0-4.fc25 python-acme-0.12.0-3.fc25 python-certbot-apache-0.12.0-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-e06b5ed81c
certbot-0.12.0-4.el7 python-acme-0.12.0-2.el7 python-certbot-apache-0.12.0-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-7036057408
certbot-0.12.0-3.fc24, python-acme-0.12.0-3.fc24, python-certbot-apache-0.12.0-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-0b35be64b3
certbot-0.12.0-4.fc24 python-acme-0.12.0-3.fc24 python-certbot-apache-0.12.0-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-0b35be64b3
certbot-0.12.0-4.fc24, python-acme-0.12.0-3.fc24, python-certbot-apache-0.12.0-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-0b35be64b3
certbot-0.12.0-4.fc25, python-acme-0.12.0-3.fc25, python-certbot-apache-0.12.0-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-e06b5ed81c
certbot-0.12.0-4.el7, python-acme-0.12.0-2.el7, python-certbot-apache-0.12.0-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-7036057408
certbot-0.12.0-4.fc24, python-acme-0.12.0-3.fc24, python-certbot-apache-0.12.0-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
certbot-0.12.0-4.fc25, python-acme-0.12.0-3.fc25, python-certbot-apache-0.12.0-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
certbot-0.12.0-4.el7, python-acme-0.12.0-2.el7, python-certbot-apache-0.12.0-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.