Jump to content

ceckelberry

Staff
  • Posts

    34
  • Joined

Everything posted by ceckelberry

  1. @Chas4 I totally get it. Apologies for the mis-communication there. Safari is more deeply tied to the OS than other browsers which creates additional overhead. This being a small team unfortunately makes maintaining different forks for different OSes not feasible at this time.
  2. Hello all, The reason you are seeing this discrepancy is the number of rules in the Safari DB are more limited than Chrome, Firefox and Edge. This is due to restrictions on rule limits placed upon us by the techinical architecture provided to us by Apple.
  3. @Chas4 Unfortunately we currently only support Mac OS 12 or higher . Legacy versions are still offered via the app store, but there are no updates provided to them.
  4. @Chas4 Sorry to hear that. Can you share your logs please(there is a button on the Support page in the extension now)?
  5. @fonebone this is a false positive. You can safely allow this. We will allow on our side as well
  6. Thanks for update! Looks like it was a Safari issue then, as our developer on this could not reproduce.
  7. Ok got it. Will have a developer take a look.
  8. I see, that looks to be the issue then. Perhaps it became corrupted. There should be at least 4 items. On that same screen, please uninstall all three items and re-install from the app store.
  9. Thank you. And just to be sure, all four checkboxes are checked?
  10. What Safari and Mac Version are you on?
  11. Thanks all. Added to the allowlist. Give it about 30 minutes.
  12. Thanks for confirming @Sondroyo. Can you reproduce the block, download the logs, and share here please? I'd like to investigate deeper.
  13. Thanks @Sondroyo! And just to be sure are you on the latest 2.6.0 version of Browser Guard? Have you manually checked for Database Updates (3 vertical dots ->Support -> Check for database updates)?
  14. My suspicion is that there an infected extension trying to inject something on your google searches, so you click it thinking it's legit.
  15. Like @AdvancedSetup said this is a valid block. I'm curious that it shows up on Google searches and I'm not able to reproduce. Do you use any other extensions? Perhaps one of them was hijacked and is injecting malicious JS into your Google searches.
  16. @BobSoulThis was due to a database that dynamically applies new patterns in the wild to proactively block emerging threats and was an FP. This should be resolved in the next database update (give it about 30 minutes).
  17. What link does Browser Guard say it is blocking? I'm not seeing a block on the latest database.
  18. This issue is only affecting Chrome (not Edge), we are still investigating why. I'm curious to hear if updating to the latest Chrome 112.0.5615.121 solves the issue as @IanH pointed out. This was an urgent update from the Chrome team. If that doesn't work, doing a factory reset of Browser Guard has been reported to resolve the issue. To do so: Open Browser Guard On the top right, click the 3 vertical dots Click "Support" Click "Factory Reset" If anyone is able to share logs and upload to Box while experiencing the issue, that would be greatly appreciated.
  19. @herolabs thank you so much for sharing. Unfortunately the logs don’t include any mention of hero.co. Is it possible to ask the user to reproduce the block on hero.co and then download the logs newly?
  20. Yes I don't have a matching rule for that either. @thisisu. Logs and reproduction steps would help if possible. I'm also not able to reproduce.
  21. This has been added to the allowlist, please allow about an hour for the update to take effect.
  22. Thanks for your feedback, we did some digging. While it is true that ads can be delivered on AMP, the ads are delivered through another intermidiary. Thus this block has been removed, expect an update in about an hour. The scam blocker issue we are aware of.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.