Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sticky: extensions #655

Closed
Thorin-Oakenpants opened this issue Feb 26, 2019 · 132 comments
Closed

sticky: extensions #655

Thorin-Oakenpants opened this issue Feb 26, 2019 · 132 comments

Comments

@Thorin-Oakenpants
Copy link
Contributor

previous threads #492 #294 #211 #12


Use this issue for extension announcements: new, gone-to-sh*t, recommendations for adding or dropping in the wiki list 4.1: Extensions. Stick to privacy and security related items

🔸 possible additions

🔸 nah

@Just-me-ghacks
Copy link

Just-me-ghacks commented Feb 27, 2019

Any thoughts on Trace by AbsoluteDouble?

P.S.: IMHO it's a perfect fit for the "nah" category.

@ghost
Copy link

ghost commented Mar 9, 2019

Trace Firefox extension, IMHO, offers several of the features found on different extensions but doesn't really handle any of them correctly or at least as best as possible, as well as some others. Not yest anyway.

My feeling is that the developer's work scheme was to install practically all features right from the start, more or less elaborated (rather less) and progressively bring each of these components to maturity. My preference is rather to add new features only once those in place have been optimized, not before.

@crssi
Copy link

crssi commented Mar 10, 2019

window.opener be gone can be removed from the list, its redundand with pref 2429 and this pref gives better protection

Add suggestions:
HTTPZ | GitHub -> HTTPS by default does not work when using Temporary Containers
Privacy-Oriented Origin Policy | GitHub

Here on are not a suggestion, bust just for your info:
Context Plus | GitHub <- A nice TC companion
Certainly Something (Certificate Viewer) | GitHub
Cookie Quick Manager | GitHub
Kimetrak | GitHub

@ghost
Copy link

ghost commented Mar 11, 2019

Kimetrak: I can see this info in uBO's dropdown and logger (and in UM)

Indeed. I have in mind another interesting Firefox extension which will as well provide the list of all sites accessed once on a page but will moreover display the security status of these connections:

208853

This is interesting because not provided by uBO.

SixIndicator on AMO and GitHub

@crssi
Copy link

crssi commented Mar 12, 2019

About Kimetrac... I know you can see all that crap in uBO and uM and logger... but it caught my eye because:
uBO and uM here is blocking a lot of crap, but if something go 3rd party, then I can see "filtered" in Kimetrac and it helps me see much faster and easier, if there is something new that uBO and uM didn't block and worth to investigate to tighten uBO personal list.

That is it, nothing further to discuss anyway, since I have put it in my post under the "section": Here on are not a suggestion, bust just for your info... so I don't care. 😄

Cheers and ❤️ you all 😸

@ghost
Copy link

ghost commented Apr 8, 2019

I've discovered a Firefox (& Chrome) extension which seems to me so worthy that I'd appreciate your opinion about it: API-Killer-IndexedDB at its GitHub repository, available at Add-ons for Firefox.

What has always bothered me are sites laying data in my Firefox's profile storage/default folder, so called indexedDB. With this API-Killer-IndexedDB extension I can now avoid blocking cookie permission for sites such as youtube.com without having my indexedDB folder filled with unnecessary data (of course if cookie permission is session-only this data is removed on FF exit, yet I dislike sites laying on my computer what is not at all necessary).

Works great here. The developer has other extensions of which API-Killer-WebSocket and API-Killer-WebAssembly, all three in the scope of ghackuserjs concerns.

Any cons to argument?

@crssi
Copy link

crssi commented Apr 8, 2019

@StanGets
First and the only commit was done 5 hrs ago.
That is a fast discovery... or you know the author?

@ghost
Copy link

ghost commented Apr 8, 2019

@crssi I don't know the developer, I discovered the extension while reviewing AOM's updated extensions and immediately spotted API-Killer-IndexedDB because of the word killer associated to IndexedDB....

One thing is sure: it works. But as the developer notes it on his GitHub repository,

Kills HTML5' IndexedDB API, might break websites, if they do not have a localStorage/cookie fallback.

This is what I remain aware of but up to now, with cookies blocked and therefor indexedDB as well, I've encountered no problematic site.

I'm really enthusiastic about this extension but there may be cons, I'm no professional.

@ghost
Copy link

ghost commented Apr 8, 2019

Thanks for correcting me, @Thorin-Oakenpants :

You will only clear IDB after a session if 1) PB mode or 2) you clear "offline website data" on close (or manually with time range everything) or 3) Temp Containers

Indeed I have set Firefox to clear "offline website data" on close. Wow, I had it all wrong, thanks agaiin.

PPS: I haven't looked, so feel free to inspect that these extensions don't use any CSP header injection

I'm afraid that's above my skills. I mentioned the extension because it solves my problems on websites where i'd like to have a cookie -- i.e. YouTube when a userscript aiming to block Autoplay does it by modifying the site's cookie -- but where allowing the cookie would have that site lay itself in my IDB ... but considering the best often includes drawbacks is why I ask here advice.

@ghost

This comment has been minimized.

@ghost
Copy link

ghost commented Apr 8, 2019

I kinda fail to see the point, esp if you use FPI.

Yeah, you're absolutely right @Thorin-Oakenpants , and I do use FPI!
I'll be frank, I'm overdoing it, not for sentimental reasons but basically for psychological ones, in other terms even if other settings do the job I insist on extras even if they appear to not at all be implied in enhanced privacy for the sole reason of a non-rational principle : I don' t like sites writing to my device unless I've authorized them to. But you are right, it is not necessary. Maybe am I getting obsessed? LOL

@ghost

This comment has been minimized.

@ghost

This comment has been minimized.

@crssi
Copy link

crssi commented Apr 8, 2019

@StanGets

I'm afraid that's above my skills.

Its actually simple to do. See the last line in the post #664 (comment)

  1. Install extension CRX
  2. Open https://addons.mozilla.org/firefox/addon/api-killer-indexeddb/
  3. Click on yellow CRX icon on the right side of URL bar and then View source
  4. Enter !content-security-policy into the search field (upper left corner). NOTE: ! means search all files.
  5. If you get a hit, then most probably the extension is modifying the CSP (need to decipher code to be sure).

Cheers :)

@ghost
Copy link

ghost commented Apr 8, 2019

@crssi thanks! Done and imputing !content-security-policy led to 0 hits.

But what I don't understand is the CRX extension being a requirement for checking CSP. Can't I just download an extension's xpi file, unzip it and search from there on? Second point is, how is searching for content-security-policy performed? Does CRX search for a specific term or specific code? Because if the query is only content-security-policy then I could as well search for it from the unzipped xpi ...

Anyway, thanks. This is not school, forget my wondering...

@crssi
Copy link

crssi commented Apr 8, 2019

But what I don't understand is the CRX extension being a requirement for checking CSP.

No. Its not, but makes the whole process much much simpler. For sure you can just download and unzip, which CRX essentially is doing already for you. 😉
API for CSP is called over content-security-policy, so if not found then CSP does not get modified. If found, then you need to review the code in those lines.

Cheers

@Kraxys
Copy link

Kraxys commented Apr 20, 2019

previous threads #492 #294 #211 #12

Use this issue for extension announcements: new, gone-to-sh*t, recommendations for adding or dropping in the wiki list 4.1: Extensions. Stick to privacy and security related items

small_orange_diamond possible additions

* [Site Bleacher](https://addons.mozilla.org/en-US/firefox/addon/site-bleacher/) | [GitHub](https://github.com/wooque/site-bleacher)

small_orange_diamond nah

I find Site Bleacher interesting because it seems to handle IndexedDB in a more clever way than other comparable addons. For what I have seen, the IndexedDB a site has put in my browser, while remaining after closing my tab, is cleared as soon as I'm visiting this site again. This seems to me to be the most efficient way to handle IDB, given the API limitation.

@ghost

This comment has been minimized.

@crssi
Copy link

crssi commented Apr 26, 2019

^^ This extension doesn't touch CSP. Did you even check?

@atomGit
Copy link

atomGit commented Apr 27, 2019

@StanGets with regard to CRX asked...

Second point is, how is searching for content-security-policy performed?

in the CRX search input use:
!content-security-policy
the exclamation char prefix tells CRX to look at the content of the source files (default is file name) - i also use this to search for 'http' ( !http ) to look at URLs

@atomGit
Copy link

atomGit commented Apr 27, 2019

re: Site Bleacher - been using it for a while and, according to dev, it does not raise entropy (he's not injecting anything into IDB storage that website can read like i thought he may have been)

i just asked him if it handles Workers cache, but i'm pretty sure it don't

@ghost
Copy link

ghost commented May 3, 2019

AFAICT all your api-killer stuff has been removed from AMO

The developer has removed all his API-Killers and all his other extensions except one, or these have been removed by Mozilla, no idea.

I had indeed mentioned the API-Killer-IndexedDB for the reasons evoked here above. The extension having been removed from AMO, and because I ignore for what reasons, I've removed it as well from my Firefox profile.

Because I continue to dislike sites pouring data in my IDB, I've found another way to block the IDB Web Api : WebAPI Blocker

I checked all occurrences of IDBxxx proveded by this WebAPI blocker and disabled all 14 of them, which are:

IDBCursor
IDBCursorWithValue
IDBDatabase
IDBFactory
IDBFileHandle
IDBFileRequest
IDBIndex
IDBKeyRange
IDBMutableFile
IDBObjectStore
IDBOpenDBRequest
IDBRequest
IDBTransaction
IDBVersionChangeEvent

Works like a charm. Certainly not all 14 need to be disabled but until I check the ones strictly required i disable all. No issues at this time.

@atomGit
Copy link

atomGit commented May 3, 2019

so... i asked the Site Bleacher dev if he would have a go at cleaning the 'service workers' stuff and he did :)

in addition to cookies, local storage and IndexedDB, the extension also addresses service workers, cache storages, filesystems and webSQLs - i don't know exactly what's covered by the latter 3, so i asked him here if anyone cares to follow that and his answer was "Don't really know"

@jingofett
Copy link

Is there a downside to using Clean Links over the other link cleaners listed on the wiki?

https://addons.mozilla.org/en-US/firefox/addon/clean-links-webext/

Personally, I find this extension catches and cleans a lot more links than the alternatives (ClearURLs, Neat URL, Skip Redirect), but I remember back before webextensions, people having an issue with it.

I use it with the following settings:

image

@atomGit
Copy link

atomGit commented May 24, 2019

Is there a downside to using Clean Links ...

somebody more knowledgeable might chime in, but IMO CleanURLs is the best of the bunch because it covers more and breaks less (not sure i've ever had ClearURLs break anything) - it's been an install & forget ext. for me - no need to fiddle with white/black lists (doen't even have one)

some may not like it because it uses an external file (hosted on gitlab) but that's actually a plus in one way in that the dev doesn't have to update the ext. every time they need to change something

@jingofett
Copy link

Is there a downside to using Clean Links ...

somebody more knowledgeable might chime in, but IMO CleanURLs is the best of the bunch because it covers more and breaks less (not sure i've ever had ClearURLs break anything) - it's been an install & forget ext. for me - no need to fiddle with white/black lists (doen't even have one)

some may not like it because it uses an external file (hosted on gitlab) but that's actually a plus in one way in that the dev doesn't have to update the ext. every time they need to change something

When using the examples on this page to test:
https://github.com/tumpio/requestcontrol/wiki/Testing-links

Clean Links successfully cleans most of them, except for the "no redirection, only parameters" group (except for example no.11) and no.14 in misc. ClearURLs cleans: no.2, no.6, no.7, no.8, no.11

Again, I'm not an expert on this but I'm just asking so I can get more information

edit: Just realized I referenced other issues on accident, I thought I had to select the issue when using the hashtag symbol. Sorry about that...

@atomGit
Copy link

atomGit commented May 24, 2019

i never actually tested CleanURLs, so i'm glad you did - given your findings, i'll have to reconsider Clean Links which is what i used before

@atomGit
Copy link

atomGit commented May 24, 2019

i made the mistake of writing CleanURLs instead of ClearURLs in this thread

anyway, i visited the test page you linked to and most of the samples are redirects ... ClearURLs is designed to remove tracking params, so i'm not sure if it's supposed to deal with redirects??? seems like it should be though

Skip Redirect caught all the redirect samples, but ClearURLs did not catch all of the "no redirection, only parameters" samples -- i'm not sure what to think, but maybe ClearURLs isn't the best solution - ima gonna chat with da dev n c whts up

@Atavic
Copy link

Atavic commented May 25, 2019

Repo here.

@DanKGooGLy
Copy link

@atomGit
Copy link

atomGit commented Apr 26, 2021

@DanKGooGLy - correct me if wrong, but Universal Bypass seems to be a very different animal than Skip Redirect in that UB doesn't skip redirects

@meedstrom
Copy link

meedstrom commented May 9, 2021

I don't know if any of you are in the EU, but here's a matter of QoL (quality-of-life). With an amnesic browser like this one (especially with Temporary Containers), either I don't care about cookies or Ninja Cookie feel nearly indispensable. You can train yourself to not mind all the cookie questions, but I think many would just give up on TC or arkenfox itself. Even after such training, I experience these as a huge QoL win.

As an alternative, I just found that the uBlock Origin filter lists for annoyances (AdGuard, Fanboy, or EasyList Cookie), which seem to take care of many cases, but not YouTube for one. I'll continue to try them. Perhaps it could be useful to put in this as a tip on the wiki.

I'm actually curious what you think about Ninja Cookie, i.e. automatically saying no to all the nonessentials. I don't think honest webmasters are a rare creature, so this would lead to less logging, right?

@geeknik
Copy link

geeknik commented May 9, 2021

I would avoid Ninja Cookie but that is just me. Good luck out there. \m/

@tirphana
Copy link

tirphana commented Jun 5, 2021

Could anyone provide an opinion/recommendation concerning https://addons.mozilla.org/en-US/firefox/addon/trackmenot/, considering it’s no longer being maintainted?

@g-2-s
Copy link

g-2-s commented Jun 16, 2021

For uMatrix the wiki says "Use it as long as it works for you... except that's risky, because how do you know it's working properly?". As far as I can see (which is not much considering I'm no expert), it seems to work quite efficiently still, but am I missing some crucial detail here? I'd be glad to ditch it for uB0 only but uM is simpler to use in my case.

@atomGit
Copy link

atomGit commented Jun 16, 2021

Port Authority by ACK-J

github: https://github.com/ACK-J/Port_Authority

Blocks websites from using javascript to port scan your computer/network and dynamically blocks all LexisNexis endpoints from running their invasive data collection scripts.

not sure this is something worth using - feedback appreciated

@curiosityseeker
Copy link

curiosityseeker commented Jun 24, 2021

Port Authority by ACK-J

github: https://github.com/ACK-J/Port_Authority

Blocks websites from using javascript to port scan your computer/network and dynamically blocks all LexisNexis endpoints from running their invasive data collection scripts.

not sure this is something worth using - feedback appreciated

Doesn't this add-on offer what gwarser's lan-block.txt list already provides? It blocks the scans on https://defuse.ca/in-browser-port-scanning.htm

@gwarser : What do you think?

@potassiumchloride

This comment was marked as abuse.

@kah0922
Copy link

kah0922 commented Jun 28, 2021

Port Authority by ACK-J
github: https://github.com/ACK-J/Port_Authority

Blocks websites from using javascript to port scan your computer/network and dynamically blocks all LexisNexis endpoints from running their invasive data collection scripts.

not sure this is something worth using - feedback appreciated

Doesn't this add-on offer what gwarser's lan-block.txt list already provides? It blocks the scans on https://defuse.ca/in-browser-port-scanning.htm

@gwarser : What do you think?

uBlock Origin's CNAME blocking also takes care of the LexisNexis endpoint blocking as well.

Edit: The addon seems to pick up Lexis Nexis endpoints not picked up by uBlock Origin, but more testing is needed to confirm that.

Edit2: uBlock Origin blocks both the original script from running or if that is not blocked, the uncloaked domain.

On another note, has anyone checked out https://github.com/garywill/autoreferer?

Also with AdGuard URL Tracking filter being added to uBlock Origin, Neat URL is redundant.

@Gitoffthelawn
Copy link

On another note, has anyone checked out https://github.com/garywill/autoreferer?

It looks good, but I prefer tools that allow you to specify the referer depending on the source URL and/or target URL, not the tab/window.

@Thorin-Oakenpants
Copy link
Contributor Author

Thorin-Oakenpants commented Jul 15, 2021

I'm going to quote potassiumchloride's from minimized comment three posts up

However, I don't really acknowledge the very biased description of @Thorin-Oakenpants about uM in the Wiki. It's nothing but pure FUD and should be replaced with a neutral, objective comment (i.e. just saying that it's currently unmaintained and nothing else!). I disliked this change of subjective personal wording from the very beginning, when uM was transferred into the Extensions-maybe section, but I'm a bit late with my complaint now. :-)

... and then I'm going to FUCKING RUB IT IN HIS FACE

Not cheering the fact this happened to uM, just pointing out that my apparent "very biased" "subjective" "personal" "FUD" was anything but

uM

edit: and for the record, this was what it was, apparently "just saying that it's currently unmaintained and nothing else"

fyi

@rusty-snake
Copy link
Contributor

FYI: https://github.com/gorhill/uMatrix/releases/tag/1.4.2

@B00ze64
Copy link

B00ze64 commented Jul 20, 2021

hpHosts has not disappeared from my uMatrix, even though I updated to 1.4.2 just now, unchecked the list, and restarted the browser. No harm done, this was just a quick edit to the default config I see on the commit...

@g-2-s
Copy link

g-2-s commented Jul 20, 2021

I updated to 1.4.4 but the "Reveal canonical names" option is now gone and adding the rule manually does nothing, can anyone confirm if they have the same issue?

@EchoDev
Copy link

EchoDev commented Jul 20, 2021

I updated to 1.4.4 but the "Reveal canonical names" option is now gone and adding the rule manually does nothing, can anyone confirm if they have the same issue?

Get this build if you want cname uncloaking https://github.com/gorhill/uMatrix/releases/tag/1.4.3b0
cname uncloaking never made it to stable (it also has a DNS leak issue when using SOCKS proxy)

@Solomon1732
Copy link

Solomon1732 commented Sep 16, 2021

uBO-Scope is abandonware. Latest commit was in July 2018. Might want to at least take note of it in the Extensions page.
https://github.com/gorhill/uBO-Scope/commits/master

@Thorin-Oakenpants
Copy link
Contributor Author

uBO-Scope is abandonware. Latest commit was in July 2018. Might want to at least take note of it in the Extensions page.
https://github.com/gorhill/uBO-Scope/commits/master

IDK if it's abandoned. Maybe it doesn't need anything done to it - @gorhill - then again, it could probably do with cname detection to properly ascertain partyness? the rest seems perfectly fine. Hopefully gorhill will reply

@practik
Copy link

practik commented Jan 24, 2022

I guess this is still the right place for extension talk, even though it's closed?

A while back there was some discussion of Universal Bypass, an extension for demystifying shortened links. claustromaniac checked it out and found it was no help in the privacy dept.

I generally avoid those links but every so often I encounter one (e.g. in an e-mail from the water company) that I have to click. So I looked to see what else is available on AMO these days and found four: Fast Forward (a fork of Universal Bypass), Link Unshorten, Quo Vadis?, and Unshort.link.

I am no 🐈 but I did my best to test them out, and it looks to me like all but Quo Vadis? work by sending your URL to the developer's server or a third-party service for analysis, which I don't love.

Quo Vadis? stumped me: It sends requests to the shortened URL and the final URL and any URLs in between, but none of those requests show up in the browser console; I could only see them by monitoring my computer's network traffic. So I wrote to the developer (https://basa.nl/quovadis/), who answered:

Quo Vadis? works by using the browser's built-in ability to perform HTTP requests. It runs entirely within the browser. When it is triggered by the user, it launches its own private (sandboxed) HTTP-request for the initial URL. This does not involve any user oriented "browsing", all data is absorbed internally, nothing is rendered. It then asks the browser to inform the extension of any redirections that occur for that request. This information includes the next URL, and the next, etc. That's it!

"Sandboxed" definitely sounds good, but I don't have the skills to evaluate what that really means, so I'm posting here in case others are interested in looking into it further.

@lhindir
Copy link

lhindir commented Jan 18, 2023

I’d appreciate more justification for Skip Redirect, since it’s the only extension to share the Recommended tier with uBlock Origin. Most of the Optional tier have caveats, and I think Skip Redirect does as well. While it works well when it works, it applies to a small enough class of links that I don’t think it’s worth the recommendation.

Inherently, it can only detect trivial redirect links directly including the target URL. base64-encoding the target is enough to get past it. Many sites work this way; email newsletter service tracking links come to mind. Similarly, any custom server-side mapping of ID’s to target links, e.g. any URL shortener service, goes undetected. This can give users a false sense of security since Skip Redirect only skips the most benign redirect links.

Additionally, it has a number of false positives (e.g. archive.org) that require users to attempt to exhaustively enumerate exceptions. This is futile, especially when services change their URL schemes.

Given the prevalence of both false negatives and false positives, I’m not a big fan and don’t use it myself. Obviously, the wiki is just recommendations, so it’s up to the author and doesn’t force anyone to follow it, but since I think most of the rest of the repo and wiki are very well-thought-out, I’m genuinely curious about the rationale here.

@xe-3
Copy link

xe-3 commented Mar 9, 2024

I’d appreciate more justification for Skip Redirect, since it’s the only extension to share the Recommended tier with uBlock Origin. Most of the Optional tier have caveats, and I think Skip Redirect does as well. While it works well when it works, it applies to a small enough class of links that I don’t think it’s worth the recommendation.

I also think providing further explanation/justification for Skip Redirect would provide value.

@ntnguyen1234
Copy link

base64-encoding the target is enough to get past it.

I think Skip Redirect can go to base64-encoded link. I just tested with this link http://example.com/?url=aHR0cHM6Ly93aWtpcGVkaWEub3JnLw== and it redirects successfully for me (no example.com connection made in network console).

@lhindir
Copy link

lhindir commented Apr 13, 2024

Yeah, I was wrong about that. The rest of my comment still applies.

@stephenhawk8054
Copy link

Btw, uBO has added a new network filter urlskip to skip click trackers. It does not skip automatically like "Skip Redirect" though, but based on the filters in the list:

https://github.com/uBlockOrigin/uAssets/blob/ea7bea1f5a86cbf32291c4b166b8c0d198b92273/filters/privacy.txt#L579-L773

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests