Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ponzu – An open-source HTTP server framework and CMS in Go

github.com

Post reply on HN
Print view View original

41–43 of 43 posts

Re: Ponzu – An open-source HTTP server framework and CMS in Go

#41

Post by srcmap »

nilslice wrote: post #24
patrickmn wrote: post #3

> Automatic & Free SSL/TLS A couple of years ago, I wouldn't have believed we would be seeing essentially zeroconf TLS/PKI in software anytime soon. Letsencrypt, the "encrypt everything" movement, and people like Steve, Ponzu's author, have improved internet security tremendously at a time when it is critically needed.

Thank you, but all credit is due to the Let's Encrypt team. It is an amazing thing they have done.

Steve,

Quick question, must the server use "Let's Encrypt" be public on internet to use it?

Like: Can I use private ip (10.1.1.x) behind the NAT and still use "Let's Encrypt" + your CMS/server?

Thanks

Re: Ponzu – An open-source HTTP server framework and CMS in Go

#43

Post by nilslice »

srcmap wrote: post #41
nilslice wrote: post #24

Earlier quoted context omitted.

Thank you, but all credit is due to the Let's Encrypt team. It is an amazing thing they have done.

Steve, Quick question, must the server use "Let's Encrypt" be public on internet to use it? Like: Can I use private ip (10.1.1.x) behind the NAT and still use "Let's Encrypt" + your CMS/server? Thanks

Sort of. If you're OK with manually updating the certificates after initially fetching them from L.E., then you can use them. However L.E. must be able to communicate directly with the server via HTTP to prove authority and send you the certificate.

There are other tests that the ACME protocol can do to determine authority over a domain name, but Ponzu's implementation doesn't handle them.

Sorry if that doesn't fully answer your question.

Post reply on HN