diff options
author | vg <vgm+dev@devys.org> | 2025-06-23 21:32:24 +0200 |
---|---|---|
committer | vg <vgm+dev@devys.org> | 2025-06-23 21:32:24 +0200 |
commit | c2e9d2acf3159ebd6ff6ed28513945eb62d05265 (patch) | |
tree | fef01f946399732761be5a7c8d9b4e6db7788066 /doc | |
parent | c4d914d69b2fe53e56b1fd81549b14a1cf667bef (diff) | |
download | acme-dns-tiny-c2e9d2acf3159ebd6ff6ed28513945eb62d05265.tar.gz acme-dns-tiny-c2e9d2acf3159ebd6ff6ed28513945eb62d05265.tar.bz2 acme-dns-tiny-c2e9d2acf3159ebd6ff6ed28513945eb62d05265.zip |
Remove contact field management
Since June 4 2025, letsencrypt don't return contact information anymore
from newAccount api point.
More information at
https://community.letsencrypt.org/t/support-ended-for-expiration-notification-emails/238173
acme_tiny_dns could be used with little modification outside
letsencrypt, but I'm aligned with the rationale given by letsencrypt on
why they removed contact information from their database.
So this commit removes contact management for the following reasons:
- without modifying the code (even if the modifications would be small),
the client does not work as the key 'contact' is not found anymore in
the json structure returned by the newAccount url.
- this client main target is letsencrypt and does not seek to be
complete.
- this simplifies the script by reducing the code and having less
features.
- I think, like explained by letsencrypt in addition to private data
issues, that reminders of an expiring certificate can be monitored by
other means. Monit for example can do it, and there exists also online
services for this if needed. See
https://letsencrypt.org/2025/01/22/ending-expiration-emails/ for more
information.
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions