Re:Feedback wanted: CORS for private networks (RFC1918)
by mook on Tuesday November 10, 2020 @11:59PM
(#25055628)
How the heck would I go about installing my own root cert into my TV? My fridge? (I'm picking devices here that could actually run browsers.)
How the heck would I have my DNS be public, if I don't have a domain? Getting one means a cost (some amount for the registration, plus whatever you consider costs to avoid your information in the registry getting leaked)
For large corporations, yes it totally makes sense to have your infrastructure be using proper domains and things. For your neighbor's network behind his router… not so much. Nothing that requires TLS does.
Re:Feedback wanted: CORS for private networks (RFC1918)
by bawolff on Wednesday November 11, 2020 @02:38AM
(#25056297)
In the context of this proposal, i'm not sure why your routers and stuff would need one, it seems like only corporate stuff would be affected.
That said, for a router, it would be vendors responsibility to set this all up. It seems possible but annoying to do this in a secure but privacy preserving way.
Re:Feedback wanted: CORS for private networks (RFC1918)
by orisho on Tuesday November 10, 2020 @08:33PM
(#25054574)
The certificate transparency log for an internal network would let you see which domains are in use and make it far easier for an attacker to exploit internal services. The attacker need not be an APT for this, it could be as mundane as a XSS attack.
Re:Feedback wanted: CORS for private networks (RFC1918)
by bawolff on Tuesday November 10, 2020 @09:18PM
(#25054850)
That's why i was suggesting using wildcard certs - they would not have the actual domain name in them.
That said, regardless of what one does, i wouldn't reccomend putting too much faith in security by obscurity.
You could also just have the dns be public. No reason why private networks can't be in public dns. If you are really paranoid use wildcard certs, and only have top domain be in the public dns.