Who benefits from this? Even though Let’s Encrypt stresses that most site operators will do fine sticking with ordinary domain certificates, there are still scenarios where a numeric identifier is the only practical choice:

Infrastructure services such as DNS-over-HTTPS (DoH) – where clients may pin a literal IP address for performance or censorship-evasion reasons.
IoT and home-lab devices – think network-attached storage boxes, for example, living behind static WAN addresses.
Ephemeral cloud workloads – short-lived back-end servers that spin up with public IPs faster than DNS records can propagate.
  • AliasVortex@lemmy.world
    link
    fedilink
    English
    arrow-up
    32
    ·
    4 days ago

    That’s kind of awesome! I have a bunch of home lab stuff, but have been putting off buying a domain (I was a broke college student when I started my lab and half the point was avoiding recurring costs- plus I already run the DNS, as far as the WAN is concerned, I have whatever domain I want). My loose plan was to stand up a certificate authority and push the root public key out with active directory, but being able to certify things against Let’s Encrypt might make things significantly easier.

  • surph_ninja@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    3 days ago

    This could go a long way towards fighting online censorship. One less issue when an authoritarian overreach gets your domain seized. Pretty awesome.

    • 3abas@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      3 days ago

      Domains need to be registered annually and DNS servers are needed to route traffic to them. But using an IP directly, you don’t need to worry about domain registration issues that can brick your systems, and you don’t have to worry about DNS providers knowing about your traffic (or maintaining your own private dns).

      If it’s not a user trying in a memorable domain, an IP serves much better.

    • SteveTech@programming.dev
      link
      fedilink
      English
      arrow-up
      7
      ·
      4 days ago

      With dynamic DNS? Yeah it always has, as long as you can host a http server.

      With a dynamic IP? It should do, the certs are only valid for 6 days for that reason.

    • jj4211@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 days ago

      They will require the requester to prove they control the standard http(s) ports, which isn’t possible with any nat.

      It won’t work for such users, but also wouldn’t enable any sort of false claims over a shared IP.

    • Melmi@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      edit-2
      4 days ago

      I don’t see how? Normal HTTP/TLS validation would still apply so you’d need port forwarding. You can’t host anything on the CGNAT IP so you can’t pass validation and they won’t issue you a cert.

      • squaresinger@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        4 days ago

        You can totally host something on carrier-grade NAT using techniques like NAT hole punching.