3 ms·
If you are running a private intranet type thing, installing your own root certs seems fairly reasonable to me. You could also just have the dns be public. No
by bawolff 6y ago
If you are running a private intranet type thing, installing your own root certs seems fairly reasonable to me.
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.
- orisho 6y agoThe 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.
- bawolff 6y agoThat'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.
- mook 6y agoHow 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.
- bawolff 6y agoIn 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.