News for hackers. Stuff that matters.
Re:Google rolls out DNS-over-HTTPS support in Chrome 83 by kashug on Wednesday May 20, 2020 @05:38AM (#23244956)
Isn't the most common way to block "illegal websites" just to block it on the DNS owned by the ISP? (which is the one you will automatically use unless you configure something else). And just making their domain point to some website saying the site is blocked. Afaik this will still work. And the normal workaround of just changing to a different DNS should work aswell.

Is sniffing of traffic common in other countries?

Re:Google rolls out DNS-over-HTTPS support in Chrome 83 by throwaway8941 on Wednesday May 20, 2020 @06:09AM (#23245133)
I don't know about other countries, but this never worked in Kazakhstan. They block whole IP ranges and your traffic silently gets dropped. I'm sure that having a single monopolistic ISP helps with implementing this.
Re:Google rolls out DNS-over-HTTPS support in Chrome 83 by sasasassy on Wednesday May 20, 2020 @06:16AM (#23245178)
I think that this change would mean that, by default, the DNS server used will be specified by Google/Chrome team. If the DNS server were still my router then there's no point to this really.
Re:Google rolls out DNS-over-HTTPS support in Chrome 83 by dingaling on Wednesday May 20, 2020 @06:32AM (#23245269)
> the DNS server used will be specified by Google/Chrome team

I don't think that any oppressive regime is going to have any qualms about routing 8.8.8.8 to its own server, or just blocking it. So you use the national DNS or get nothing.