This key, and the practice of coercing its generation/transmission, it’s reasonable to expect that such will become a (the) “new, improved evercookie” mechanism. By sending a DRM -encrypted video file (perhaps surreptitiously, sized 1×1 px), a site can coerce one’s browser to generate and transmit an EME verification key (immutable, permanent, based on serial number(s) of your system hardware components). This is indeed an important privacy (if not security) consideration - one which Orfox documentation may not explain fully. Safer ~= “Audio and video (HTML5 media) is tap to play” This seems like a weird, misdirected, configuration choice.
Safer ~= “JavaScript is disabled on non-HTTP websites”īecause bad actors presumably never serve malicious scripts via https? Tor… on mobile… YMMV but content is often intolerably slow to load.
0 kommentar(er)
