HTTP header spoofing + cross-engine coherence (v1.2.0) #5
Loading…
Reference in a new issue
No description provided.
Delete branch "anti-detection-and-v1.1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Closes the largest remaining fingerprinting gap: the engine only rewrote what page JavaScript saw, while the browser still sent its real
User-Agent,Accept-LanguageandSec-CH-UAheaders — a JS-vs-network mismatch that is itself a strong signal.HTTP header layer (declarativeNetRequest)
User-Agent/Accept-Language; rewrites thesec-ch-uatrio for Chromium covers and strips it for Firefox/Safari; strips high-entropy client hints andDNT/Sec-GPC; per-engineAccepton document requests.declarativeNetRequest,webNavigation.Cross-engine JS coherence
applyIdentityPresence), now applied when the real cover arrives instead of at install with the default profile (this was also a latent bug): deletesgetBattery/connection/deviceMemory/userAgentData/window.chromeand other Chromium-only surfaces under Firefox/Safari covers; provides them coherently under Chromium;oscpu/buildIDonly for Firefox.Intllocale coherence (resolvedOptions().locale) +v8BreakIteratorremoval.screen.availLeft/availTop,window.screenLeft/screenTop.enumerateDevicesreturns a fixed plausible device set instead of empty.EXT_disjoint_timer_queryhidden.Known gaps (deliberately deferred, tracked separately)
Test plan
npm run compile(tsc) cleannpm run build/npm run zipproduce a valid MV3 zip (v1.2.0, new permissions present)getBattery/window.chrome/userAgentData