Description of the issue: Mobile client goes to site, keeps ‘https’ status and shows no warning of danger. desktop client goes to site, drops back to ‘http’ and displays a “Deceptive site ahead” dangerous warning.
Did the issue present with default Shields settings? Yes, desktop & mobile both have default settings.
Does the site function as expected when Shields are turned off? Neither client changes website behaviour when shields are turned off.
Is there a specific Shields configuration that causes the site to break? If so, tell us that configuration.: No, shields don’t seem to have any effect on behaviour.
Does the site work as expected when using Chrome? I don’t use Chrome, but it does function like the mobile client does when opened in Edge.
Brave version (check About Brave):
Desktop = 1.39.111 Chromium 102.0.5005.61 (Official Build) (64-bit) on a Windows 10 notebook
Mobile = 1.39.115, Chromium 102.0.5005.78 on a Galaxy A52 running Android 12
So is the desktop client being overzealous in protecting me, or is it justified in the danger warning? Does the mobile client not incorporate the same level of security, and is therefore potentially leaving me open to malicious attack?
Thanks fanboynz, I had assumed this since the safe browsing now accurately states it is through google safe browsing in the desktop client. The mobile client has ‘Safe browsing’ set to ‘Standard protection is on’, surely it should also give the same warning?
We won’t disable safebrowsing in shield settings (or any Brave settings), would be just bad security if we did. The site being blocked should contact safe browsing support.
I don’t want to disable it; I’m wanting the mobile client to warn me, the same as the desktop client does. Without the warning, if I use my phone, I’m oblivious to the known risk of a site.
Example: I had been looking on my phone at an item on the site I first posted about for a while. I finally went to purchase using my notebook and bam; a security notice. If it wasn’t for the fact that I had my notebook open, I would have purchased on my phone; being unaware that I’d just entered my details into a suspicious site.