sudo-sys

sudo-sys@sudoroom.org

4 participants
922 discussions

Let's Encrypt Subscriber Agreement Update

by noreply＠letsencrypt.org

Dear Let's Encrypt Subscriber: We've updated our Subscriber Agreement, effective September 21, 2022. This is the agreement that governs the relationship between you and ISRG with regards to your acquisition and use of SSL/TLS digital certificates issued by ISRG (via Let's Encrypt). You don't need to take any action to continue to use the Let's Encrypt service but we encourage you to review the new agreement. The main updates are: we now link to instructions on choosing a revocation reason if you revoke a certificate. This is a requirement for Subscriber Agreements from all Certificate Authorities as of this year. Also, we've removed unneeded capitalization, removed a section that is redundant with our Certificate Policy (CP), and tweaked the wording of the requirement to "assure" control of your private key so it matches the Baseline Requirements (BRs). You can find the updated agreement (v1.3), along with a document that shows the differences between the previous and current agreement and the full text of the previous agreement here: https://letsencrypt.org/repository/ If you have any questions about the new agreement, please ask on our community forums: https://community.letsencrypt.org/ Let's Encrypt is a free service because we want to make the Web more secure and privacy-respecting for everyone. We're able to operate as a nonprofit thanks to corporate sponsorships and donations. Please consider joining our sponsorship program: https://www.abetterinternet.org/sponsor/ Or donate now during our summer fundraising campaign to support this service (and get neat Let's Encrypt apparel!). https://letsencrypt.org/donate/ Thank you, The Let's Encrypt Team

4 years

Let's Encrypt Subscriber Agreement Update

by noreply＠letsencrypt.org

4 years

Cron <www-data@sudoroom> [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.monthly /usr/share/mailman3-web/manage.py runjobs monthly

by root＠sudoroom.org

ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_extensions/management/commands/runjobs.py", line 40, in runjobs job().execute() File "/usr/lib/python3/dist-packages/hyperkitty/jobs/update_and_clean_index.py", line 37, in execute run_with_lock(update_index, remove=True) File "/usr/lib/python3/dist-packages/hyperkitty/lib/utils.py", line 181, in run_with_lock log.exception("Failed to update the fulltext index: %s", e) File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 447, in __exit__ self.unlock() File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 398, in unlock raise NotLockedError('Already unlocked') flufl.lock._lockfile.NotLockedError: Already unlocked

4 years