Isnt security mostly achieved by heavy obscurity? A password secures because other people dont know what it is, it is obscured.
Comment on How are people discovering random subdomains on my server?
4am@lemmy.zip 3 days ago
At the end of the day this is obscurity, not security; however obscurity is a good secondary defense because it buys time.
I too would be interested to learn how this leaked
zeca@lemmy.ml 3 days ago
pishadoot@sh.itjust.works 3 days ago
They’re not the same.
Hiding an unlocked treasure chest in the forest is obscurity. Sure, you might be the only one who knows it’s there at first but eventually someone might come across it.
Having a vault at a bank branch is security - everyone knows there’s a vault there, but you’ll be damned if you’re going to get into it when you’re not authorized.
Good passwords, when implemented correctly, use hashing (one way encryption) to provide security. It’s not obscured, people know you need a password to access the thing (in our example)
bluehambrgr@lemmy.world 3 days ago
In cryptography, there’s a difference between “secrets” (like passwords and encryption keys), and hiding / obscuring something (like steganography or changing your web server to run on a different port)
chillpanzee@lemmy.ml 3 days ago
it’s not even obscurity; it’s logged publicly.
sommerset@thelemmy.club 3 days ago
It’s not. Wildcard DNS and wildcard cert. Domain is not logged publicly.
People that keep saying logged publicly simply don’t understand setup and technilogy
Keelhaul@sh.itjust.works 3 days ago
How is it being logged publicly? Like OP said there is no specific subdomain registered in the DNS records (instead using a wildcard). Same for the SSL cert. Only things I can think of is the browser leaking the subdomains (through google or Microsoft) or the DNS queries themselves being logged and leaked. (Possibly by the ISP inspecting the traffic or logging and leaking on their own DNS servers?). I would hardly call either of those public.