3 ms·

LE lets you get a cert by putting stuff in DNS, but it's generally hard for a program running on your Web server to modify DNS in an automated fashion and this

• kuschku 11y ago
  Well, that can be automated easily, too. If I could just put a public key in DNS, sign stuff with the corresponding private key, and send the signed request via POST to LE, then they can easily check that I control the DNS, and I can automate it (and never have to change the webserver’s content or DNS).
  • wolf550e 11y ago
    You can prove you control the domain by DNS: https://letsencrypt.org/howitworks/technology/ https://letsencrypt.org/howitworks/technology/
    • kuschku 11y ago
      Yes, but that is only a challenge-response DNS verification. What I’m looking for is "I write a value into DNS once, and use that to prove at any future point at which it exists that I still control the DNS". In this example, by putting an RSA public key in there. (the very same I use for the CSR)
      • hlandau 11y ago
        I've suggested this on the ACME list, actually; allowing people to put their ACME account public keys in DNS, rather than the random-per-transaction challenge specified right now, which is quasi-unusable. The problem, apparently, is that CA forum rules require that a random challenge be used. Of course this doesn't make much sense in the context of ACME, where you have a private key identifying the user account. But this obstructs the specification of a deterministic challenge for DNS, alas.