!MthpOIxqJhTgrMNxDS:nixos.org

NixOS ACME / LetsEncrypt

107 Members
Another day, another cert renewal45 Servers

Load older messages


SenderMessageTime
26 Dec 2021
@aanderse:nixos.devaandersenamesilo23:03:50
@moritz.hedtke:matrix.orgmoritz.hedtke
In reply to @hexa:lossy.network
like … why wouldn't 10 seconds work for a dynamic dns update 😕
I could imagine because of the issues documented in https://letsencrypt.org/2020/02/19/multi-perspective-validation.html
23:58:53
@moritz.hedtke:matrix.orgmoritz.hedtkeIf I understood correctly what you mean23:59:04
27 Dec 2021
@moritz.hedtke:matrix.orgmoritz.hedtkewhen I think about it the reasoning doesn't make sense in that case00:00:05
@moritz.hedtke:matrix.orgmoritz.hedtkeTTL?00:00:19
@hexa:lossy.networkhexa moritz.hedtke: the record doesn't exist before the validation try 00:02:41
@hexa:lossy.networkhexaso negcache at worst00:02:57
@hexa:lossy.networkhexabut letsencrypt probably won't do caching here00:03:04
@moritz.hedtke:matrix.orgmoritz.hedtkeAnd you think the record is there before e.g letsencrypt starts querying? I'm not too familiar with acme using dns00:05:55
@hexa:lossy.networkhexasomething like that00:53:31
@hexa:lossy.networkhexaI haven't dug deeper00:53:34
@hexa:lossy.networkhexaMerged!16:38:09
@m1cr0man:m1cr0man.comm1cr0manThanks!16:59:15
@m1cr0man:m1cr0man.comm1cr0manhaha so many emails from the 8 closed tickets16:59:24
29 Dec 2021
@winterqt:nixos.devWinter (she/her) In https://github.com/NixOS/nixpkgs/blob/ac169ec6371f0d835542db654a65e0f2feb07838/nixos/modules/security/acme.nix#L417, it says that this makes it readable to the group specified by the cert service, but the perms for /var/lib/acme are 0750. Wouldn't the cert be inaccessible even by the group specified by the cert service, then? 03:03:55
@winterqt:nixos.devWinter (she/her)ah, I see https://github.com/NixOS/nixpkgs/blob/ac169ec6371f0d835542db654a65e0f2feb07838/nixos/modules/security/acme.nix#L294 now03:07:40
@winterqt:nixos.devWinter (she/her) So because of the fix permission service having its working directory set to /var/lib/acme, I guess acme:acme would be the owner of /var/lib/acme. 03:09:35
@winterqt:nixos.devWinter (she/her) But then wouldn't the permissions of 0750 would still disallow access to the cert specified groups? 03:10:19
@winterqt:nixos.devWinter (she/her) * But then wouldn't the permissions of 0750 still disallow access to the cert specified groups? 03:10:27
@winterqt:nixos.devWinter (she/her)
      # These StateDirectory entries negate the need for tmpfiles
      StateDirectory = [ "acme" "acme/.lego" "acme/.lego/accounts" ];
      StateDirectoryMode = 755;
      WorkingDirectory = "/var/lib/acme";

...ah.

03:16:37
@m1cr0man:m1cr0man.comm1cr0man yeah, we really went all-in on statedirectory/systemd activation logic for the folder creation. It ended up solving all previous permissions issues we were encountering, whilst also providing systemctl clean --what=state acme-mydomain.service for easy full renewals 13:22:39
@m1cr0man:m1cr0man.comm1cr0manThere's a bunch of really difficult to figure out logic wrt when directories need to be created, recreated or permissions changed which all depend on systemd service activation. Hence, it was best to leave it to systemd where possible13:30:20
30 Dec 2021
@winterqt:nixos.devWinter (she/her)Redacted or Malformed Event04:44:03
@winterqt:nixos.devWinter (she/her) Also: the useACMEHost option in Nginx vhosts doesn't set the group for the certificate, so it (unexpectedly) fails to start. I can't find any documentation that requires anything other than setting useACMEHost, though, so I don't think I'm doing anything wrong. 04:54:21
@m1cr0man:m1cr0man.comm1cr0man You do need to set the group explicitly when using useACMEHost. We can't assume that the cert is being used for other purposes in that scenario, thus it would be unsafe to set the group automatically 15:01:20
@m1cr0man:m1cr0man.comm1cr0man * You do need to set the group explicitly when using useACMEHost. We can't assume that the cert is being used for only ngnix/apache in that scenario, thus it would be unsafe to set the group automatically 15:01:37
@winterqt:nixos.devWinter (she/her)

Got it. I feel like that can definitely be documented better, I’ll PR if I can think of adequate wording.

Question: why can’t we assume, though? In what scenario would someone be using one certificate across multiple HTTP servers? idk, just seems unlikely, it’s definitely best not to assume but i can’t think of an actual practical use case unless I’m just missing something obvious…

20:05:16
@winterqt:nixos.devWinter (she/her)maybe something something different ports something something?20:07:50
@m1cr0man:m1cr0man.comm1cr0manone wildcard for mail and web is a use case I used to maintain for a deployment21:14:33
@m1cr0man:m1cr0man.comm1cr0manI added nginx + dovecot + postfix users to acme group21:14:56

Show newer messages


Back to Room ListRoom Version: 6