When internal hostnames are leaked to the clown

Post by [deleted] » Thu, Feb 05, 2026, 10:59 AM UTC

notsylver wrote: post #13

I think people are misunderstanding. This isn't CT logs, its a wildcard certificate so it wouldn't leak the "nas" part. It's sentry catching client-side traces and calling home with them, and then picking out the hostname from the request that sent them (ie, "nas.nothing-special.whatever.example.com") and trying to poll it for whatever reason, which is going to a separate server that is catching the wildcard domain a…

Post by joshstrange » Thu, Feb 05, 2026, 11:21 AM UTC

atmosx wrote: post #53

I bought a SynologyNAS and I have regretted already 3-4 times. Apart from the software made available from the community, there is very little one can do with this thing. Using LE to apply SSL to services? Complicated. Non standard paths, custom distro, everything hidden (you can’t figure out where to place the ssl cert of how to restart the service, etc). Of course you will figure it out if you spent 50 hours… but w…

Post by zaptheimpaler » Thu, Feb 05, 2026, 11:26 AM UTC

lsofzz wrote: post #97

zaptheimpaler wrote: post #85

Earlier quoted context omitted.

Clueless lol. This is not about any of that. I run Plex on my local network at plex.domain.com. Plex sends logs to the internet with its local domain in the string. Leak. There is no easy way to solve this without deeply inspecting each packet a service sends outside your network, and even that doesn't work when services use SSL certificates and certificate pinning preventing MITMs.

wtf are you allowing plex to initiate outbound connections to begin with? and why is plex not in it's own VLAN with a egress FW rules to second with? lastly, why aren't you running snort/suricata to inspect the packets originating at plex? let me solve this problem for you - it probably doesn't bother you at all. otherwise, you'd scratched your itch a long time ago. > Clueless lol. It's ok to be clueless. And, it's o…

Post by prmoustache » Thu, Feb 05, 2026, 11:38 AM UTC

TheDong wrote: post #108

zaptheimpaler wrote: post #79

Earlier quoted context omitted.

I don't know much about email, but how would some random service send an email from my domain if I've never given it any auth tokens?

You don't need any auth to send an email from your domain, or in fact from any domain. Just set whatever `From` you want. I've received many emails from `root@localhost` over the years. Admittedly, most residential ISPs block all SMTP traffic, and other email servers are likely to drop it or mark it as spam, but there's no strict requirement for auth.

Post by namibj » Thu, Feb 05, 2026, 11:50 AM UTC

prmoustache wrote: post #118

TheDong wrote: post #108

Earlier quoted context omitted.

You don't need any auth to send an email from your domain, or in fact from any domain. Just set whatever `From` you want. I've received many emails from `root@localhost` over the years. Admittedly, most residential ISPs block all SMTP traffic, and other email servers are likely to drop it or mark it as spam, but there's no strict requirement for auth.

> Admittedly, most residential ISPs block all SMTP traffic, and other email servers are likely to drop it or mark it as spam, but there's no strict requirement for auth. Source? I've never seen that. Nobody could use their email provider of choice if that was the case.