• 0 Posts
  • 178 Comments
Joined 3 years ago
cake
Cake day: June 25th, 2023

help-circle






  • “Isn’t” what? If you’re referring to the hosting experience, I’m talking based on experience setting up some PHP software from the last year or two. Unless you just slap docker on it, it seems to be a pain getting php running, it might want a very specific version (extra pain to get that specific version running), and I remember dependency management giving me trouble, possibly also being weird with the older version of PHP.




  • I wonder about one thing, if somebody can perform MITM on arbitrary domains, is there something like certificate pinning to stop impersonating the authorities used for things like this? I remember OCSP being something like that (if I’m not butchering the initialism), where the browser requests confirmation the certificate is currently valid, and the server can pre-fetch this confirmation to send to the client.







  • Jet says the following

    If you want https it’s gotta be a external DNS record anyway, might as well point to internal ips

    My point is, the A record, the one pointing to an IP address, doesn’t need to be public/external, it’s not needed for the wildcard cert, so it can be kept internal.

    I’m mentioning the other challenge trying to make it clear why the record matters for that, and not for a wildcard cert, sorry if that just made things more confusing.


  • Perhaps a better analogy is a painter who has no idea what their canvas is made out of; they know it’s a canvas, they know it’s for painting, they’re faintly aware they’re using some material stretched over a frame, but they just assumed a canvas is a canvas and they just never considered there might be other options than the one they’ve been getting.


  • The point is, the challenge doesn’t require a public DNS A record pointing to your IP, it’s not involved in issuing a wildcard certificate. It requires you to control DNS records for the domain to issue a temporary TXT or something record to prove it, one which you can remove afterwards. This was my point in the original comment.

    It’s A and AAAA records that are used when you open a website in a browser to map the domain to an IP address, the ones I’m saying don’t need to be public.

    The challenge dosent require your site to be public only the DNS to be public.

    And just to be clear, that was describing a different kind of challenge, the simpler one which most people probably use, and which does actually involve A records.


  • I’m a bit confused by what you’re saying, because to my knowledge the DNS entry you’re mentioning won’t help with getting a certificate at all. Challenges will typically require either having the DNS entry point to a publicly reachable website (doesn’t get you wildcard) or proving the ability to modify records for the domain by adding something like a TXT record on the fly, which shouldn’t require A/AAAA records.

    So you should be able to do the second type of challenge without a global A record to get a wildcard certificate, and use local DNS for the A record?