-
-
Notifications
You must be signed in to change notification settings - Fork 345
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
No Resource URI Leak doesn't work #255
Comments
It seems like this issue was finally fixed in Firefox 57+ and, probably, these fixes can be backported to Waterfox too. |
good to know, should this issue be marked as closed then? Or should I wait until the issue is actually fixed? |
Yes, please. |
Accidently closed it, I was a little confused for a second sorry |
You may have a look this way |
If the issue is what he says it is, then this should work. However I usually don't trust some random person posting a patched version just out of principle that it isn't always safe. The developer's repo isn't on github so I would have to create a new account and isn't very responsive it seems, anyway here is the link |
In short, addons that use relative paths for scripts break in FF55+. To fix them you have to convert to absolute paths |
Perhaps it's the reason why anothers addons (such as Refresh Blocker, etc) doesn't work anymore ? Nevermind it's just an idea because I will have to replace it in the futur. Another choice will be to wait the next release (called Waterfox_v56). In fact because it was announced there (n°235) and that's a very good news. |
I'll back port this patch for the final v56 release. |
Thanks so much! |
Is this patch already in v56 - or will it be in a later revision ? [I do not see it working at the moment on the first 56 release] |
I will suppose at the moment no it's missing. Because I had check it and the result is clear : no it doesn't work as expected. |
Tested with Waterfox 56.1.0_2 on FreeBSD-CURRENT. Before and after installation: Would you like to close this issue 255? If trust of an extension is an issue, it should be raised with the developer. NB earthlng is a member of the ghacksuserjs organisation. When the patch is backported, the commit can be marked as a fix for an earlier issue, About the leak (resource) · Issue #235 . |
Yay I can use this addon again! Yeah I will close it. Thanks For convenience, here are the links again xpi can be downloaded directly here: https://raw.githubusercontent.com/earthlng/testpages/master/no_resource_uri_leak-1.1.1-an%2Bfx%2Bsm%2Btb.xpi |
Well I will assume the plan has change ? It won't happen, right ? PS : I was thinking today I will take another little time to check it (this time with Waterfox_v56.1.0). But at the end, there is no point. |
I didn't look into who made the patch until the recent post on this issue. This issue was just for the No Resource URI Leak extension, which a patched version has been made that works (and that I trust). I agree that @MrAlex94 should have ported the patch by now. |
Sorry, at the time I incorrectly assumed the patch would land in 56.
“At least, the next time @MrAlex94 <https://github.com/MrAlex94> have the
decency to apologize (almost 7 months ? No news. Damn right sometimes I'm
too kind and very very very patient).”
Honestly, that’s really rude. You’re more than free to submit a patch
request if you’re unhappy. This is an open source project after all, that
I’m doing my best to maintain.
If you check the bug filing, there were patches out around v55, which is
what caused the initial confusion.
https://bugzilla.mozilla.org/show_bug.cgi?id=863246
…On Fri, 6 Apr 2018 at 18:58, Matthew Seal ***@***.***> wrote:
I didn't look into who made the patch until the recent post on this issue.
This issue was just for the No Resource URI Leak extension, which a patched
version has been made that works (and that I trust).
I agree that @MrAlex94 <https://github.com/MrAlex94> should have ported
the patch by now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#255 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEgoWHMsieYk0_wx0_2O03Xjg1S3K8b6ks5tl_L1gaJpZM4QKERy>
.
|
Oh ok, hope I didn't come off as rude as well. As long as it gets ported at some point I'm happy. |
No, you're okay :-). Just that being respectful costs nothing, seems people seem to forget there's another human being reading these messages sometimes. |
To be clear, no I don't forget about the human being. Well let's say it's sound rude but to explain, you should at first remember 3 little things :
Despite my respect (and no I haven't forgot the real meaning), for me it's seem understandable. Now (nevermind let's try to move on) I will conclude by thank you I accept your excuse. But don't except from me any patch. Because that's right, (like I said at the beginning) no I don't have the knowledge. |
Hello, I would just like to report that the extension "No Resource URI Leak" doesn't work in waterfox
link: https://addons.mozilla.org/en-US/firefox/addon/no-resource-uri-leak/?src=search
This is an issue if you want to stop fingerprinting as it allows accessing certain files through resource:// URIs https://browserleaks.com/firefox
The text was updated successfully, but these errors were encountered: