Hacker News Reader

Comment by optymizer | Hacker News Reader

  * To serve content that can be accessed on networks using captive portals
  * To serve content on localhost while developing
  * To serve content on devices where setting up letsencrypt or other SSL is either too much of a hassle or not important
  * To stand up a quick HTTP server on hacked servers

Maybe others can come up with more examples

View on HN

> * To serve content on devices where setting up letsencrypt or other SSL is either too much of a hassle or not important

This is my use case, serving homeserver stuff from a ".internal" domain, only accessible through WireGuard. I ain't gonna mess with a custom CA just for this.

If one of my devices gets compromised enough to be able to sniff network packets that pass through the WireGuard interface, I have bigger problems to worry about.

To allow access by devices (embedded, vintage) where SSL cannot run.

Serve content that is reversed proxied by something that terminates SSL - cloudflare, cloud gateways, Nginx etc, ingress controllers ...

Reply on news.ycombinator.com