-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
[ BUG? ] Links Launching Browser Are NOT Filtered Consistently #2067
Comments
The browser does not wait for extensions to be fully loaded and ready before opening tabs, it's a by-design browser issue. Reported before. |
This is a system-wide issue. You can block the default browser in the OS settings with a firewall, or even prevent default browser execution with an Intrusion Prevention System. While the user actively launches a non-default OS browser, any automated/drive-by browser connection is blocked by the firewall, |
@gorhill yes my friend, I know as much but sometimes it will bypass it even when it is running. You put your focus entirely on Scenario 1 and completely glossed over the second one where the browser is now up and running - so by your statement - the extension is active, so what's the reason then it will continue to allow them to open after the extension is loaded? Because right now, the allowance at initial startup can be triggered willfully by simply the malicious program initiating a new instance of the browser too with a different "command line" parameters. Since that instance has to "load" the extensions again as well, it is effectively nullifying the blocks. What I am mostly asking is, why after the initial bypass it keeps letting it through? And as a resolution to this, or to at least try and mitigate (which looking through the source of Chromium there are ways to hook in earlier, much like NoScript does with Mozilla by for lack of a better word "hooking the kernel" so it runs at system level which means that the browser WILL honor any security restrictions BEFORE launching, no matter the extension recognition time) to try and provide a slightly earlier execution time? Alternatively, can we just introduce a render block which effectively acts like say JQuery's document.ready mechanism, to prevent any links from ACTUALLY making the socket connection, until the browser has fully loaded and the system is in place, so voila once the render block is done because the system is ready, it will let the socket go through at which time if it matches a rule, bam, killed. Now, I know these might not be solutions readily available, but what if we at least lobby for them, or look into using existing framework's that Google uses to secure the browser itself, to leverage to what we need. Sort of like off label use of a medication. @Atavic what you are saying makes little sense, because the firewall would block the BROWSER itself, not a link within it, unless you mean web filtering like Malwarebytes or Avast which cause more problems than they resolve and not interested in hacking all over the place, we are testing for a reliable single existing solution, because asking the end user to protect so many end points is a near impossibility as not everyone is technically inclined. So your system of blocking the default browser results in poor usability and we don't need the "cure" to be worst than the disease. |
Maybe wasn't my previous post clear enough? I have my default browser blocked by my IDS. It can't even launch. Any link launched by applications in my OS call this blocked browser. I use another browser and I have a taylored Open with... on my system. This solves all your problems that are security issues on a system level, not the browser or the addons. |
I did not address issue 2 because there is no reproducible case, no URL. What I need is all the steps for me to reproduce without having to guess anything. |
BTW the answer was given: Browser Issue. Addons work inside the browser, so the issue should be filed to: Bugzilla@Mozilla or you can block the default browser at the system level. |
Second scenario is probably caused by cached items, remnants of scenario 1. Scenario 3 is the only one that seems plausible and worth a try. |
@anewuser I can't believe someone agreed with your statement given it means nothing here. You say be concise, what about the way I presented the details of the problem organized answering everything the developer specifically puts to be answered no concise? This is technology and discussing ways to do something can't be done in a single line, if that's how you consider development, you are in the wrong field. I was concise without sacrificing detail or explanation. @Atavic I understand your system, it was clear and I find it very clever and something I would do for myself but not something that is scalable, deployable (easily) or stable long-term, too many things can break the hackiness of it. I am on Chrome with this right now, not Mozilla, so keep referring to that is just ignorant. The part that is the fault of the browser has been starred and not much else can be done. @CrisBRM Yes that one is included for completeness because it DOES happen even when the browser was manually and fully loaded. While cache is a possible problem, it shouldn't actually matter. The blocking is done at the socket level, so cache request or not, shouldn't matter. Especially that the links in question don't really cache since they are "hoppers". It was mostly the scenario 1 & 3 that are issues, but I don't believe in being half assed even when accused of not being concise; whatever the hell that is supposed to mean from a random hit and run comment. @gorhill We go way back, and I was there when you started uMatrix (when it was still called HTTP Switchboard), so at least have the civility to be respectful and don't be condescending when you know you are being glib and dismissive. I don't know the motivation and I personally don't care, but what I am bringing up is valid and pretending like it is not, is not the right way to go. I included all the links above (in the filter section) and the reason I didn't give out full links is because it would be putting malicious links in the wild and I have more consideration than that. Since you can easily test what I am saying with ANY short link that you can generate yourself, hanging up on no links to test is disingenuous as is saying it's not reproducible simply because you didn't even try. I provided you EVERYTHING you asked in your template and was even insulted and accused of not being concise because of all the things you asked for and I provided and yet you are still claiming you don't have what you need? There is no guessing and seriously you should just say I don't care about it working right, don't want to fix it or look into it despite putting my name and reputation on it, and I don't care that you took time to come to me and try to help me and it would been far more genuine and appreciated than trying this act. There are things you don't know that would make this even more wrong and shameful but ignorance is not an excuse and I have no interest in telling the world what you should already know. Fix it, don't fix it, care, don't care, I am done. Good luck with that but the day you realize I was right and you could have done something about it, remember this. |
I don't know why you say that -- nowhere in here did I write something condescending. I just try to keep my answers short and to the point. If it's about my "no URL" answer, then again that is me pointing out that fact: I currently would have to go on a hunt to find somewhere on the web URLs which involve at least one of your listed wildcarded hostnames to use as test case for this issue -- and such time-consuming URL-hunt is not something that should be expected from me; it is the responsibility of the person opening an issue, hence why I emphasize this in CONTRIBUTING. There might be something to do for point 1, there is an idea I have been juggling with since a while -- but I am really not sure about the result, I will have to experiment when I get the time. |
What can you do about it? Forcing Offline Mode until the addon is loaded and working? |
Actually duplicate of #1327 -- I had forgotten there was an issue already opened about this. |
Related issues: - #2067 - uBlockOrigin/uBlock-issues#128 Related mozbug issue: - https://bugzilla.mozilla.org/show_bug.cgi?id=1503721
Issues
> Scenario # 1
> Scenario # 2
> Scenario # 3
URLs
Any link shortening service, although I have experienced it with these:
Screenshots
Really not a visual issue that a screenshot would add any value and plus I didn't grab any of the times it happened, so since this is understandable without it, shouldn't be an issue.
Reproduce
First put the filters above in. Then you can have a program trigger them for you or create a desktop shortcut to some shortened URL, preferably one of the above, close your browser completely and make sure its not in memory anymore, then double click the link and have it open up, watch and see what I mean.
Settings
Not entirely important here but here you go:
Lists
As already state in issue #2066 , not applicable here, so I won't clutter here with it but except for a couple extras that I clicked, the rest is pretty default, minus ONE outside list that is actually meant to prevent blocking of the blocking and it is combined with a TM script to ensure that they can't invalidate my blocks.
Filters
N/A beyond what is already listed above.
The text was updated successfully, but these errors were encountered: