Yeah, but it seems like a better default than trusting whatever happens to be in the dhcp options
. Maybe the default should be a RR of providers that meet availability standards (like CT logs do), I dunno.
-
This Tweet is unavailable.
-
-
This Tweet is unavailable.
-
Replying to @munin
That seems like a pretty cynical interpretation dude. It's just the default, I think when users go to McDonald's free WiFi, they're usually not explicitly stating they wanted to trust the McDonald's DHCP option tags.
2 replies 0 retweets 7 likes -
This Tweet is unavailable.
-
Replying to @munin
Ahh, the tweet you were quoting said "DNS privacy is a huge issue", it sounds like you disagree with that, and think it's not an issue at all - You want browsers to just do what the network admins indicate?
2 replies 0 retweets 1 like -
This Tweet is unavailable.
-
Replying to @munin
I've heard the argument, network admins argue it's a source of visibility into what their users are doing, and this is "going dark". If they have admin on the endpoints they can disable it - but I think it shouldn't be the default, because of the Starbucks Wifi scenario.
2 replies 0 retweets 1 like -
This Tweet is unavailable.
-
What is the issue with TLS intercept other than for businesses that use byod?
2 replies 0 retweets 0 likes
I don't have any objection to it, it requires admin on the endpoint. At that point it's effectively their endpoint to do with as they please. I don't agree with @munin though, if you have admin just disable DoH if you think TLS intercept is bad 
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.