When internal hostnames are leaked to the clown
rachelbythebay.com
When internal hostnames are leaked to the clown
1–10 of 265 posts
Re: When internal hostnames are leaked to the clown
#2Re: When internal hostnames are leaked to the clown
#3Re: When internal hostnames are leaked to the clown
#4Slightly surprised that this blog seems to have succumbed to inbound traffic.
Re: When internal hostnames are leaked to the clown
#5I agree the web UI should never be monitored using sentry. I can see why they would want it, but at the very least should be opt in.
Re: When internal hostnames are leaked to the clown
#6Pennywise found my hostname? We're cooked.
Re: When internal hostnames are leaked to the clown
#7Pennywise found my hostname? We're cooked.
Re: When internal hostnames are leaked to the clown
#8I don’t understand. How could a GCP server access the private NAS? I agree the web UI should never be monitored using sentry. I can see why they would want it, but at the very least should be opt in.
also
> you notice that you've started getting requests coming to your server on the "outside world" with that same hostname.
Re: When internal hostnames are leaked to the clown
#9I don’t understand. How could a GCP server access the private NAS? I agree the web UI should never be monitored using sentry. I can see why they would want it, but at the very least should be opt in.