Osprey: Browser Protection

Changes in 1.2.7

• Added custom logos to each protection provider
• Added HideProtectionOptions policy to hide the panel
• Revised approach for displaying Official Partners
• Added policy protections for important default settings
• Added a new blocked cache to reduce network requests
• Block page and icon now show total blocks for all providers
• Renamed Restricted classification to Adult Content
• Cleaned up code

Looks great! Thanks, @Foulest .

 

Access to your test page was successfully blocked by Osprey:
"Reported by: AdGuard Security DNS (and 8 others)"



Is it possible to find out who the other 8 protection providers are?

Edit: The 8 shown in the icon is a bit misleading if access to your test page was blocked by AdGuard Security DNS (1) and 8 others: 1+8 = 9

 

That's a good catch - I'll fix that right away!

 

You'll also now see what other providers blocked a page. Again, thanks for letting me know!

 

Good news! Thank you very much, @Foulest . I love Osprey.

 

I've been getting a lot of CAPTCHA's when doing google searches lately, to prove I'm human. I'm not suggesting Osprey is the cause, but I'm just trying to find out why.

Anyone seeing this the last couple of weeks?

 

I haven't experienced this.

 

I now suspect it's Google's Ai. I've found I can search something similar on another tab (Firefox) and I don't see the CAPTCHA.

 

https://malwaretips.com/threads/google-search-captcha.136307/#post-1129778

 

I noticed that version 1.2.7 reports how many other Protection Providers block the malicious web page.

This reporting is done exclusively based on the selected Protection Providers.

In the example below the malicious web page appears to be blocked by only 1 Protection Provider (active - Gdata/Bitdefender/Open DNS):




When in fact as many as 6 protection providers would be blocking the malicious web page.
Example below all active Protection Providers:




Test performed here:

https://db.aa419.org/fakebanksview.php?key=173205

 

This is intentional.

 

Yes,I have noticed.
But only by opening the browser development tools you can know which other Protection Providers intervene in blocking and instead which ones do not block the web page: