News for hackers. Stuff that matters.

A comment on .INTERNAL is now reserved for private-use applications. Parent comment

Re:.INTERNAL is now reserved for private-use applications by Spooky23 on Saturday August 10, 2024 @01:29AM (#41207535)
The big issue with encrypted HTTP on the local LAN is that you’re stuck running a certificate authority, ignoring TLS validation, or exposing parts of your network in the name of transparency.

Running certificate authority is one of those a minute to learn, lifetime to master scenarios.

You are often trading “people can sniff my network scenario” to a “compromise the CA someone setup 10 years ago that we don’t touch” scenario.

[ Parent | on HN ]
Re:.INTERNAL is now reserved for private-use applications by bruce511 on Saturday August 10, 2024 @09:49AM (#41209487)
I agree that setting up a self-signed CA is hard, and harder to keep going.

However DNS challenge allow for you to map an internal address to an IP number. The only real information that leaks is the subnet address of my LAN. And given the choice of that or unencrypted traffic I'll take that all day long.

[ Parent | on HN ]