Re:Chrome is deploying HTTP/3 and IETF QUIC
by judge2020 on Wednesday October 07, 2020 @02:49PM
(#24711333)
You can still define a custom HTTPS endpoint[0], you just need to trust (within Windows) the self-signed certificate your pihole/etc device has, in order to use it on Chrome; your endpoint setting isn't messed with when you select 'enhanced protection' or anything[1].
The only downside to this is that rogue IoT devices or hacked IoT devices can easily get around DNS filtering, but that was already possible before DoH by using or running some benign free public http api for dns lookups.
The only downside to this is that rogue IoT devices or hacked IoT devices can easily get around DNS filtering, but that was already possible before DoH by using or running some benign free public http api for dns lookups.
0: https://i.judge.sh/hollow/Lyra/chrome_hxURk11GDb.png
1: https://i.judge.sh/bony/Fleet/s4HD5OqNvf.gif