certbot/letsencrypt-auto-source/pieces
Brad Warren d1330efe41
Print warning when certbot-auto has insecure permissions. (#6995)
This PR attempts to better inform people about the problem identified at https://community.letsencrypt.org/t/certbot-auto-deployment-best-practices/91979/.

I was hesitant to add the flag --no-permissions-check, however, if there's some obscure distro out there (or custom user setup) that has a strange users and groups, I didn't want us to either:

Have to put out a bug fix release
Refuse to fix the problem and let them deal with warnings on every run

* add check_permissions.py

* Update letsencrypt-auto.template.

* build letsencrypt-auto

* Add test_permissions_warnings to auto_test

* Allow uid/gid < 1000.

* Add --no-permissions-check to Certbot.

* Add --no-permissions-check to certbot-auto.

* Add test farm test that letsencrypt-auto is quiet.

As a bonus, this new test will catch problems like the one that the caused
0.33.1 point release.

* Update CHANGELOG about permissions check.

* Update permissions comment.

* Fix symlink handling.

* Use a better default in auto_test.py.
2019-04-30 10:45:03 -07:00
..
bootstrappers Fix typo in comment ("upstreqm") (#6926) 2019-04-07 22:20:03 +02:00
certbot-requirements.txt Release 0.33.1 2019-04-04 15:24:43 -07:00
check_permissions.py Print warning when certbot-auto has insecure permissions. (#6995) 2019-04-30 10:45:03 -07:00
create_venv.py Construct the sanitized, pinned and hashed requirements file for certbot-auto (#6839) 2019-03-25 18:52:59 +01:00
dependency-requirements.txt Update urllib3 to 1.24.2 (#6977) 2019-04-22 15:23:26 -07:00
fetch.py Address erikrose's comments on #5329 (#5400) 2018-01-09 16:48:16 -08:00
letsencrypt-requirements.txt Pin dependency versions when using tools/venv.sh (#4629) 2017-05-11 10:06:05 -07:00
pipstrap.py Construct the sanitized, pinned and hashed requirements file for certbot-auto (#6839) 2019-03-25 18:52:59 +01:00