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.
Comment on Let’s Encrypt Begins Supporting IP Address Certificates
squaresinger@lemmy.world 3 days ago
Couldn’t this prove very troublesome in combination with carrier grade nat?
jj4211@lemmy.world 3 days ago
melmi@lemmy.blahaj.zone 3 days ago
I don’t see how? Normal HTTP verification would still apply so you’d need port forwarding. You can’t host anything on the CGNAT IP so you can’t pass verification and they won’t issue you a cert.
squaresinger@lemmy.world 3 days ago
You can totally host something on carrier-grade NAT using techniques like NAT hole punching.
deadcade@lemmy.deadca.de 3 days ago
You don’t get control of the incoming port that way. For LetsEncrypt to issue a certificate primarily intended for HTTPS, they will check that the HTTP server on that IP is owned by the requesting party. That has to live on port 80, which you can’t forward on CGNAT.