DNS-over-HTTPS causes more problems than it solves, experts say https://www.zdnet.com/article/dns-over-https-causes-more-problems-than-it-solves-experts-say/ …pic.twitter.com/Td8WVxtwVZ
U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
I think applications authors would be happy for a central such resolver that do *secure* DNS. But there isn't one. So we circumvent the problems by doing it ourselves.
I guess I just don't see that a third-party DoH stack (as a supposed stopgap measure) inherently means that it has to be built into individual applications with no central point of control.
To be clear, my concern is primarily from a user PoV, with zero interest in logging. One big issue I see is exactly that each application vendor effectively take away a little bit of control from the owner, and on bigger scale control is basically lost.
We're talking about two browsers. Two. Both with documented Enterprise policy support. And if it actually becomes all or most applications, well, consider finally taking the hint that nobody wants your DNS snooping and meddling.
You are but I don't see why we would limit the discussion to two browsers. And as a user I don't feel at all the same about that scenario, each application sending DNS queries wherever it wants seems like worse snooping/meddling behind the user's back.
The problem in enterprise/school is that many devices are BYOD, hence no admin control to apply enterprise policy. Endpoint security is also not a given more generally, and even in cases where there’s enterprise OS config there may not be browser-specific configs.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.