NixOS ACME / LetsEncrypt | 103 Members | |
| Another day, another cert renewal | 42 Servers |
| Sender | Message | Time |
|---|---|---|
| 29 Jan 2025 | ||
| This has been a decision from the get-go: We are not testing lego, we are testing the Nix module. I have 0 interest in testing behaviour of lego outside of standard operation. | 20:16:47 | |
| 2 Feb 2025 | ||
| https://github.com/NixOS/nixpkgs/issues/374792#issuecomment-2629203727 | 02:07:22 | |
| 6 Feb 2025 | ||
| 06:10:06 | ||
| 15 Feb 2025 | ||
| 10:19:26 | ||
| 10:43:22 | ||
| 16 Feb 2025 | ||
| I'm looking at what can be done to create the ACME account separately of fetching a cert again because of the impending Revert "nixos/nginx: not "before" ACME certs using DNS validation". m1cr0man Have you already brought up adding a lego sub-command that only creates the account with them? That looks like something I can try to contribute there, so I'm curious if there's relevant discussion I didn't find. | 22:13:39 | |
| I haven't reached out to lego about that specifically. It would be a nice thing to have for sure | 22:43:14 | |
| We could then add it to the setup service | 22:43:23 | |
| Ok, I'll look into it more | 22:43:59 | |
| Exactly, the goal behind it is to simplify the unit dependencies | 22:44:34 | |
| 17 Feb 2025 | ||
| I don't think we currently support ACME Renwal Info (ARI), because don't execute lego when the certificate is not yet outdated | 16:55:13 | |
| https://github.com/go-acme/lego/pull/1912 | 16:55:14 | |
| I thought we execute lego like every 24 hours | 16:56:10 | |
| LE are currently sending out mail to their subscribers with recommendations | 16:56:11 | |
| did that get conditionalized? | 16:56:15 | |
| hm, let me check | 16:56:26 | |
| https://github.com/NixOS/nixpkgs/pull/80856 | 16:56:48 | |
of course the module has changed a lot since then so it's possible we don't reliably execute lego when that timer fires, which would be bad | 16:57:04 | |
| 16:58:04 | |
| looks like we always call lego | 16:58:13 | |
| perhaps we just need to pass an ARI flag then. (not sure why that wouldn't be default) | 16:58:42 | |
| still a draft | 16:59:00 | |
| https://datatracker.ietf.org/doc/draft-ietf-acme-ari/ | 16:59:08 | |
| I think it's been deployed at Let's Encrypt for a while though | 17:07:42 | |
| (years?) | 17:07:48 | |
| yeah, 2023-2024 | 17:10:23 | |
| they updated the spec a few times | 17:10:30 | |
| 17:10:44 | |
| does nothing when the acme endpoint does not offer RenewInfo | 17:11:12 | |
| https://letsencrypt.org/2024/04/25/guide-to-integrating-ari-into-existing-acme-clients/#step-5-selecting-a-specific-renewal-time | 17:12:17 | |