It was online for 3 seconds before getting a 404 request for /.git/config

Re:It was online for 3 seconds before getting a 404 request ... by singron on Thursday May 16, 2024 @10:53PM (#40385910)

If you care, you can use a wildcard cert. E.g. instead of getting a cert for foo.example.com, get one for *.foo.example.com, and then use an obscure subdomain. AFAIK, nobody is bruteforcing subdomains on wildcard certs.

[ Parent | on HN ]

Re:It was online for 3 seconds before getting a 404 request ... by bradtheappguy on Thursday May 16, 2024 @10:58PM (#40385940)

They are

[ Parent | on HN ]

Re:It was online for 3 seconds before getting a 404 request ... by thwarted on Thursday May 16, 2024 @11:23PM (#40386066)

Are they brute forcing them, or are they relying on the fact that most users of wildcard certs also have wildcard DNS entries, so it's just that everything is actually available. Wildcard DNS pointing to a web server with a wildcard cert will pass through to the web server, and at that point the web server responds with a 404 if the host header isn't one configured for virtual hosts.

[ Parent | on HN ]

Re:It was online for 3 seconds before getting a 404 request ... by ffsm8 on Friday May 17, 2024 @10:05AM (#40390066)

Didn't the wildcard cert still need the alt-names specifying the host for the browser to accept the certificate as fully valid? I remember being annoyed by warnings until I added them a decade ago while playing around with a private CA at a previous job

[ Parent | on HN ]

Re:It was online for 3 seconds before getting a 404 request ... by dilyevsky on Friday May 17, 2024 @07:12PM (#40395029)

Yes, /cn is deprecated. But letsencrypt adds your wildcard into subjAltNames as well and it works great.

[ Parent | on HN ]