-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add Tmpl.Scan options for anti-phishing rules #788
Conversation
Automatic detection of anti-phishing rules per browser is achieved through scan options, so this deprecates the use of Firefox_Phishing_DirectAccess and Chrome_Phishing_DirectAccess as default templates.
JFYI: In the past, the asterisk "*" after "safebrowsing" was necessary. The update was done via temporary files or folders. Without the asterisk "*", the update then always failed. |
@APMichael Most likely blocklist.xml and cert9.db will stay the same, because some known trojans rename them. |
Yes, "blocklist.xml" and "cert9.db" work fine. These do not need an asterisk. |
I tested extensively the detection for all supported browsers, so this pull request is not a working in progress anymore. UPDATE: You might want to consider to add a new Scan option in order to exclude this behavior. |
Nobody seems interested in this PR, so it's time to close. If anyone wants, just let me know here and I'll recreate these changes in a new PR. |
With this commit, automatic detection of anti-phishing rules per browser is achieved through appropriate scan options, so it deprecates the use of
Firefox_Phishing_DirectAccess
andChrome_Phishing_DirectAccess
as default templates.By approving this commit, the decision to accept these templates is demanded to the user after the upgrade through the Software Compatibility tab (the
#4337,
reference will be replaced with 'Allow direct access to xxx phishing database'):I tested successfully the detection of all browsers supported by Sandboxie, including Firefox and Edge.
The first one was a bit hard to be recognized automatically in Classic's Software Compatibility, but it was sufficient to apply and uncheck twice
Firefox_Phishing_DirectAccess
in DefaultBox settings.New configurations will benefit from this change, but also all old configurations cleaned from the
Firefox_Phishing_DirectAccess
andChrome_Phishing_DirectAccess
references inside sandboxes.