Re:.INTERNAL is now reserved for private-use applications
by politelemon on Saturday August 10, 2024 @03:07AM
(#41207849)
It's the opposite - there is a risk, but not a larger risk. Environment traversal is easier through a certificate transparency log, there is almost zero work to do. Through a wildcard compromise, the environment is not immediately visible. It's much safer to do wildcard for certs for internal use.
[ Parent
| on HN ]
Re:.INTERNAL is now reserved for private-use applications
by ixfo on Saturday August 10, 2024 @05:12AM
(#41208276)
Environment visibility is easy to get. If you pwn a box which has foo.internal, you can now impersonate foo.internal. If you pwn a box which has *.internal, you can now impersonate super-secret.internal and everything else, and now you're a DNS change away from MITM across an entire estate.
Security by obscurity while making the actual security of endpoints weaker is not an argument in favour of wildcards...