-
-
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
Safe Browsing availability and levels #452
Comments
Phishing list is probably the most interesting one. No clue if Safe Browsing V2 still works but to enable V4 (aka
|
Open the page about:preferences#security, you should see that :
And according to the page about:config :
In the case, I'm just wonder : it isn't the same thing ? |
@WagnerGMD, do you see warnings (i.e., |
Oh, yes, I see that they're enabled with a clean profile. Have I raised an issue without testing? I'm an itsy-witsy bit stoned, just enough to not test the other prefs. Sorry |
At this moment, I can't try with Waterfox. Because it was disable (a long time ago). The main reason was : I assume my antivirus will work too. (but it doesn't seem to bue true for now...that's strange and I will need to check this later...) I don't use Chrome but I had try with Firefox_v60. Bad news, it was able to block only a fews (I will need to check again but at first feeling, I would say between 4 and 8). No trouble @grahamperrin and no worry, I just want to avoid confusion. Because I really don't know if we are talking about the same thing ? Right now, I can't say because I had just discover your post. And apparently there is also an addon Safe Browsing_v4. Do you have a link ? Because at the moment, I can't tell which one it's between them on AMO |
I'm a starter of the reddit thread, and I mean that safe browsing itself works but Waterfox doesn't use lists which Google provides ( For example, http://malware.testing.google.test/testing/malware/ is blocked with Firefox but not with Waterfox. |
Thanks,
I find it blocked. Tested with both:
Also blocked in the new profile 56.0.4_4 on FreeBSD-CURRENT. |
Tag https://addons.mozilla.org/firefox/tag/google%20safe%20browsing draws attention to Privacy Settings, version 0.2.6 of which is compatible with the current release of Waterfox. However, tags on AMO are/were so rarely used that I should not treat the result as comprehensive. Safe Browsing Version 4, 1.0.0The attempted |
V2.2 would probably be supported until ESR52 reaches EOL. @grahamperrin, on FreeBSD waterfox-56.0.4.20_1 or later should use V4. Safe Browsing will stop working until limits on downstream key are bumped. As a workaround just remove the patch or use a different key. Firefox has |
Thank you @grahamperrin for the clarification, now I understand (and it doesn't come from AMO). |
Waterfox application functionalityRe: my 'everyday' Waterfox profile, at https://mozilla.logbot.info/firefox/20180526#c14811467 (without mentioning Waterfox) I pinpointed a 2018-01-16 update … that probably arose from prior use of the profile, on FreeBSD-CURRENT, with Firefox. On a nearby Mac running Sierra I found a Waterfox profile named 'hello' that was created on 2018-01-16. This profile has the preferences for Safe Browsing, and:
– if I'm not mistaken, no update. My concern here is that end users may have a false sense of security. Meta, tracking: #538 |
At about:preferences#security I found both:
– whilst at about:config?filter=browser.safebrowsing.enabled I found:
|
According to the page about:config, for me (right now) it doesn't seem to exist.
Then I'm wonder :
From my point of view (and a lot of people), it's almost useless because we have a good antivirus (web filter, antimalware, etc (and for the record, nothing has change I'm still under W10 and I didn't yet done the update because it's again Waterfox_v56.1.0 (for the moment))). That's why @grahamperrin I decide to disable these settings (a long time ago). PS : You can check it (the page about:preferences#security) on this picture. |
Hi,
https://mozilla.logbot.info/firefox/20180526#c14811471 includes a link to an an extension that will convert numbers such as those. OT
(If you'd like to discuss the pros and cons of e.g. uBlock Origin and Privacy Badger compared to the Safe Browsing API, please aim for https://www.reddit.com/r/waterfox/ – I'll pick it up from there. Thanks 👍) |
HI, thank you for the clue @grahamperrin and sorry I just can't. The reason is very simple, I don't use them (neither uBlock Origin, neither Privacy Badger). PS : But today my afternoon was very good (for once). So I will give you 2 drawback examples (for each addons) :
Do you remember (or know) the addon Policeman or Policy Control ? By clarity I refer to my wish to identify clear (pictures, fonts, etc) and control anything about the request. |
Please, no more off-topic.
This issue deserves focus. |
To be clear, my first intention was to explain my point of view (or the situation). That's why at this moment, I can't help on the reddit website. Like I said (for real) the bugs are very annoying... and if you want to blame someone take reddit (after all I have report these bugs several months ago and nothing was done to rectify these bugs (until these last days and no it isn't good enough yet)). And don't forget one thing : Which one has mentioned these addons at first ? It wasn't me then my advice will be to avoid to blame me (because no it won't be my fault) and (no offense) but sometimes this kind of reaction is a bad one (exaggeration for nothing). PS : For the record, nearly 12 years ? I had help a very huge number of people over the internet (on various matter). |
https://www.waterfoxproject.org/, I never realised that Waterfox lacks this feature.
I learnt through https://www.reddit.com/r/waterfox/comments/7zouiz/safe_browsing_google_provider/dupreza/.
Can a preference be added to Waterfox, to allow use of the API?
If not: the web site etc. should make things such as this clear, please.
Reference
Mozilla bug 1387651 - Staged rollout of Safe Browsing V4 to the release population using Shield (RESOLVED FIXED 2017-11-08)
I became aware of the roll-out when an outdated Firefox ESR alerted me to an incompatibility:
The text was updated successfully, but these errors were encountered: