<xmp><!-- <body> --></xmp>

Chromium 113 on Linux: a bug

Jon Nileprecinct Feline


fyi: DoH coming soon :: DoH :: what is DoH :: mozilla cloudflare & google vs the world :: DoH: facts you should know :: techtalks: DoH :: the DoH mess :: ycombinator: DoH :: DoH: theres a catch :: chrome 83: DoH

PlanitiaPost PlanitiaPost PlanitiaPost PlanitiaPost

DoH on Linux design doc :: archwiki: DoH :: linux: DoH :: opensuse: DoH :: ubuntu: DoH :: nsswitch.conf :: chromium: DoH :: firefox: DoH :: opera: DoH :: vivaldi: DoH :: DoH: benefits & risks :: DoH: clarity needed :: DoH: good bad moot :: DoH: questionable :: DoH: wrong partial solution :: DoH: covert command & control :: DoH: global domination


whatsmydns.net :: dnscrypt: public servers :: github: DoH servers :: controld.com: standard configs :: controld.com: opera :: controld.com: take back your internet

"Chrome’s behavior is generally equivalent to an nsswitch.conf hosts: configuration of files dns (checking the HOSTS file and then making DNS queries), so that configuration (a common configuration) will always be accepted as compatible, and any configuration not containing those two entries in that order will always be incompatible ... resolve (see nss-resolve). Used to invoke a more advanced replacement library (systemd-resolved) for host resolution. As this library supports features like DNSSEC validation (that Chrome does not support), it could be very surprising and non-ideal for typical users for Chrome to bypass the library, so such entries will be considered incompatible with Chrome resolution ... Anything else will be considered incompatible, but could be allow-listed as compatible in the future if additional common compatible cases are identified."

Blog Intro
Articles / News


hosted by
hosted by

powered by
kBlog v1.02.007
freedns by

find the Mystique
Screaming CuckooBroad Associates part of the CircleOmega organisation
<noscript> <!-- ooo