Or at least one that allows you to white-list stuff. Please open an issue on chromium and ask them to provide a more polite flag which also protects you from fingerprinting, but does not break valid use cases. But it does so by breaking everything that relies on reading from canvas no matter whether they may hurt your privacy or not. It is the -disable-reading-from-canva flag that breaks SwitchyOmega. You can also block reading data from canvas for all web pages but not for extensions. FYI, you can prevent canvas fingerprinting by painting random pixels on each canvas which completely changes the checksum without changing the image, and I've seen extensions doing this. It just happened that the way that you attempt to protect privacy broke SwitchyOmega as an unexpected side-effect. SO does not require you to sacrifice your privacy nor does it invade your privacy. Or you could turn the option off and use a Chrome Extension for the same blocking No, you don't. Slimjet should allow white-listing extensions on this feature. SwitchyOmega will continue to rely on canvas image data to work. However, I don't see any mature and reliable solutions on Chrome Web Store, so. Chrome Extensions can't touch other extensions' background page by default, and explicit permission can be granted for this when necessary, thus solving the problem. Or, the blocking can be implemented as a Chrome Extension. Or the browser should ask you to grant permission when you install extensions, just as the way you could grant the extensions cross-origin requests. Guess what? Websites will have to do a non-WebRTC version based on browser plugins (NPAPI) or flash, either of which is more dangerous.Īs a user of Slimjet, you should open their issue tracker and tell them that they should allow putting extensions in the white-list. I mean, if you are into that kind of reasoning, WebRTC shouldn't be used at all because there's also a WebRTC leak. But I don't think it is reasonable to bundle hundreds of extension icons just because one technique of blocking canvas fingerprinting could break it. It is unfortunate that SO doesn't work if your only intention is to hide from canvas fingerprinting. I'm going to close this issue because I believe SwitchyOmega is a legit use case of canvas image data. This could include Google Docs for example. Apart from SwitchyOmega, any website that wants to process image drawn canvas is also broken. Well, the bad part is, such blocking often results in many false positives. Actually I want to turn this on as well, but Chromium seems to hide this behind a flag. ![]() It is also kind of Slimjet to put it there as an option that could be easily tweaked. Yes, I understand the potential harmfulness of canvas fingerprinting and I wholeheartedly support you leaving it on. Such techniques hadn't cause any problem until this issue popped up on my Github notifications. Therefore it is not possible without relying on canvas drawing. However, SwitchyOmega lets you choose any color you like in the spectrum for profiles, and at most two of them end up in browser icons. Proxy SwitchySharp has bundled a bunch of extension icons in different colors so it does not have to use canvas at all. This limitation also applies to extensions that let you customize the icon color such as SwitchyOmega. bandwidth meter), animated icons and pictures. Examples of this include graph and bars in icons (e.g. I'm just saying that most extensions with dynamic icons could break. I'm not saying that most extension will break.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |