6 ms·
Marginally better for sure but in this case the path would also have been "leaked" to the sentry instance owned by developers of the the NAS device phoning home
by amichal 8mo ago
Marginally better for sure but in this case the path would also have been "leaked" to the sentry instance owned by developers of the the NAS device phoning home. This can happen in zillions of ways and is a good reason to use relatively opaque urls in generally and not "friendly ids" and generally being careful abou putting secrets in URLs.
- andix 8mo agoJust try it. The first example gets attacked by bots nearly immediately after issuing a TLS cert. The second one usually doesn't get detected at all.
- Kwpolska 8mo agoWhat if you have a wildcard cert for *.example.com?
- andix 8mo agoMuch better. But you still leave traces from dns queries. Subfinder has a lot of sources to find subdomains, not only certs: https://github.com/projectdiscovery/subfinder https://github.com/projectdiscovery/subfinder
- jamesfinlayson 8mo agoI worked at a company where the security team disliked wildcard certificates because it exposed us to the risk of someone, somehow, hosting something malicious on a subdomain.