Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 6 subscribers
  • Views 9875 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos AV 9.x blocks the new 1Password 4.x browser extension

SCM73

Sophos AV 9.x does not allow the 1Password browser extension to auto-fill login/password fields in browser

Using Sophos AV 9.x with 1Password 3 was not an issue, everything worked fine, but the folks from 1Password recently revamped their software to a 4.x version. And then the browser plugin that allowed auto-fill of login/password fields stopped working. It still opens and you can select the login/password information, it just does not fill the fields anymore.

The folks from 1Password released the following page concerning problems with their software, and Sophos AV is mentioned as being one possible culprit for the "does not auto-fill" problem: http://learn.agilebits.com/1Password4/Mac/en/KB/filling-issues.html

Indeed, entering 127.0.0.1 as a whitelisted web address in Sophos AV solves the problem, at least for me, in the Chrome browser.

Can Sophos make both softwares compatible again, so that we do not need to input this "exception"? I don't like giving localhost a whitelist status.

:1013799


This thread was automatically locked due to age.
  • 0

    Seems to be solved!

    I use Mavericks and Sophos 9.0.3. 

    Before on Lion I made the exclusion as mentioned. Just dit a reinstall for Sophos on Mavericks. No exclusions anymore and 1Password fills the data as usual

    Regards,

    Iwan

    :1013941
  • 0

    Good to know! Might not be Mavericks though... I would rather bet that a Sophos update fixed the problem. Since I will delay the Mavericks upgrade for a while, to ensure maximum compatibility with the apps I use, I will try to exclude the rule and then check for any Sophos upgrades, and reboot the system, to check if indeed it's Sophos that fixed the issue.

    :1013955
  • 0

    A little update here....

    The problem wasn't fixed in Mavericks. Here is what i found out:

    I had Sophos for MAC SA edition installed (Non free version) there i made settings to exclude 127.0.0.1 for 1Password I allso had multiple credentials filled in for updating. After a minor problem i decided to uninstall Sophos SA version and then reinstall the free version Sophos for Mac HE.

    Now updating went wrong (never stopped) because Sophos was using my previous credentials allthough i couldn't see those in the autoupdate configuration. Allso 1Password seems to be working fine again without the exlusion filled in (e.g. not showing in the exclusions). 

    Untill i did a complete clean install for my Mac and reinstalled sophos again i had to put back in the exclusion again in order to get 1PW functioning again.

    Bottomline THE PROBLEM ISN'T SOLVED! MY PREVIOUS CONCLUSION WAS WRONG.

    Hope i didn't put others to search why it isn't functioning on their machines.

    Regards Iwan

    :1013961
  • 0

    Ok, thanks for the update. I did mention the issue on Sophos' own forum, let's see if they pick up.

    :1013967