Remix.run Logo
WebPKI and You(blog.brycekerley.net)
62 points by aragilar 3 days ago | 4 comments
ivanr 2 hours ago | parent | next [-]

If you like this sort of thing, perhaps you'll enjoy my SSL/TLS and PKI history where I track a variety of ecosystem events starting with the creation of SSL in 1994: https://www.feistyduck.com/ssl-tls-and-pki-history/

bob1029 2 hours ago | parent | prev | next [-]

The short lived certificates started making a lot more sense to me when I discovered I could get Let's Encrypt to issue IP address certs. Clearly, in this context of use we need our certificates to die quickly.

You can now make any web server operate with a publicly valid TLS certificate without paying any money, registering a domain, configuring DNS or disclosing any personally identifiable information. It can be entirely automatic and zero configuration. The only additional service required is something like a STUN server so the public IP can be discovered and updated over time.

yosamino 7 minutes ago | parent [-]

I am reading your comment and find the proposition interesting, but I can't quite understand the part about the STUN server - doesn't that "just" help me find my own public IP address ? Do you mean that I could then give out this address to others (instead of them having to do a DNS lookup) so they can connect to the webserver ?

Uptrenda 6 hours ago | parent | prev [-]

I feel this is a perfect complement to the current 1. link: https://satproto.org/ which implements its own CA system with different trade-offs.