acme-dns-tiny, branch masterFork of https://github.com/Trim/acme-dns-tiny but simpler and lets you define your way of update dns serverhttps://git.devys.org/acme-dns-tiny/atom?h=master2025-07-06T07:08:04Zupdate test suite to latest letsencrypt certificate policy updates2025-07-06T07:08:04Zvgvgm+dev@devys.org2025-07-06T07:08:04Zurn:sha1:f201868b9089da733ae268a5a72f8359be10e51dAdd conversion for retry-after header2025-06-26T08:53:05Zvgvgm+dev@devys.org2025-06-26T08:53:05Zurn:sha1:ac6cbfb81f5683e5af2fdb8810c5bb536643f47d
Headers coming from request answer are strings, and sleep expect
a number. Convert header to integer, fallback default is already an
integer, will do a no-op in this case.
add requirements for listing dependencies for this project2025-06-23T21:09:18Zvgvgm+dev@devys.org2025-06-23T21:09:18Zurn:sha1:ad50a8ee4d5ab6676e045230fea435409b23a1d6Fix stupid mistake introduced in previous commit2025-06-23T20:18:00Zvgvgm+dev@devys.org2025-06-23T20:18:00Zurn:sha1:ff9ba98c8802669d096c1cb48c8b60f102c93c61
While removing contact lines, I also removed the call which registers
the account, leading the client to not work anymore.
Remove contact field management2025-06-23T19:32:24Zvgvgm+dev@devys.org2025-06-23T19:32:24Zurn:sha1:c2e9d2acf3159ebd6ff6ed28513945eb62d05265
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.
robustify nonce management by retry mechanism2023-01-16T16:16:24Zvgvgm+dev@devys.org2023-01-16T16:16:24Zurn:sha1:c4d914d69b2fe53e56b1fd81549b14a1cf667befadd compatibility for older dnspython releases2021-02-21T12:00:17Zvgvgm+dev@devys.org2021-02-21T12:00:17Zurn:sha1:9aa60992fbc87cb3c5cc21421ef7e59038d90540add support for alternative chains2021-01-17T20:25:43Zvgvgm+dev@devys.org2021-01-17T20:25:43Zurn:sha1:4338401912e3a415bf0a056c521cef612e29888cadd contact information example2020-04-04T16:50:02Zvgvgm+dev@devys.org2020-04-04T16:50:02Zurn:sha1:706cffaac7aba2a4e623b4d1971d7c93d666d599Rework test (coverage and refactorization)2020-03-12T16:43:52Zvgvgm+dev@devys.org2020-03-12T16:43:52Zurn:sha1:cf2f1f2d3429650444685e07ee4e11bcd596bba8
- better coverage (add contact tests)
- split one big test with a loop on a dict to single test functions,
giving better view on test advance and report
- factorization of _csr and _san_csr to a single function