-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[Security] [Android] Safe Browsing doesn't work in android-core (Follow up to #8381) #8705
Comments
Any updates to this issue? I think it would be good to have on Mobile, at least on Android, maybe iOS, since this feature is on Desktop. With the ability for users to turn it off of course. I for one would have it on just to be on the more secure side. |
Hi there @OnlinePlayer865 - we are making progress 😄 We're wrapping up this feature on iOS (see brave/brave-ios#1339) and are looking to merge soon (iOS product version 1.19?). We can then look at doing this on Android after taking care of some other priority work. I believe @jumde would be able to look at this in the next few months. Thanks for your patience! 😄 |
Perfect! Didn't think to check the iOS page. Thank you for the info! |
As mentioned in the security review, we decided against having our own implementation and went with Apple's built-in one. For Android, we could either reuse the desktop implementation (this is what Firefox does on Android) or go with the SafetyNet API. |
Any progress on this ? Brave still has no safebrowsing working on Android :/ |
We'll be starting work on this soon 😄 Doing some pre-work to see what is needed. We had taken a first step with #8664 (which looks correct) but that didn't work I verified our Android build servers are setting the |
Description
Safe Browsing isn't blocking anything in android core.
Steps to reproduce
Actual result
Not blocked.
Expected result
Should be showing the red interstitial pages just like on desktop.
Issue reproduces how often
Easy
Issue happens on
Device details
Brave version
1.5.x Android-core release
Website problems only
Additional information
Follow up to #8381
The text was updated successfully, but these errors were encountered: