Adrien Ferrand 595b1b212e [Windows] Avoid letsencrypt.log permissions error during scheduled certbot renew task (#7537) ... While coding for #7536, I ran into another issue. It appears that Certbot logs generated during the scheduled task execution have wrong permissions that make them almost unusable: they do not have an owner, and their ACL contains nonsense values (non existant accounts name). The class `logging.handler.RotatingFileHandler` is responsible for these logs, and become mad when it is in a Python process run under a scheduled task owned by `SYSTEM`. This is precisely our case here. This PR avoids (but not fix) the issue, by changing the owner of the scheduled task from `SYSTEM` to the `Administrators` group, that appears to work fine. * Use Administrators group instead of SYSTEM to run the certbot renew task		2019-11-13 10:04:45 -08:00
..
.gitignore	[Windows] Create an installer for Certbot (#7324)	2019-09-03 16:30:13 -07:00
certbot.ico	[Windows] Create an installer for Certbot (#7324)	2019-09-03 16:30:13 -07:00
construct.py	Make uncomplicated modules private (#7528)	2019-11-08 16:19:21 -08:00
renew-down.ps1	[Windows] Create a certbot renew scheduled task using the installer (#7371)	2019-09-23 12:29:18 -07:00
renew-up.ps1	[Windows] Avoid letsencrypt.log permissions error during scheduled certbot renew task (#7537)	2019-11-13 10:04:45 -08:00
run.bat	[Windows] Create an installer for Certbot (#7324)	2019-09-03 16:30:13 -07:00
template.nsi	Create a release pipeline on Azure for Windows installer (#7441)	2019-10-30 10:19:10 -07:00