Anti-virus makes 1 password 4 not work. When will it, without the unexceptable 127.hack?

Mainia

Do you see a "for sure" fix coming soon for using 1Password 4 when used with Sophos and Intego anti-virus? I don't and won't use the 127.0.0.1 "hack". Is it feasible to fix or is it a limitation on how you coded 1 Password 4?

DavidB

For what it's worth, I am using Intego VirusBarrier X6 (OS X 10.8.5) and 1P 4 (AgileBits website version) with no apparent conflict.

Mainia

Thanks, Then I could use that. But I really want Sophos

Mainia

Mike T,

What do the developers say, do they think they will get a "good" fix so that Sophos will work without the 127. hack? How far along are they on fixing this issue?
.

MikeT

Hi @Mainla,

Beside contacting Sophos to whitelist 1Password by default, there is nothing we can do to fix this. It's on Sophos and other companies to allow folks to whitelist specific apps and their processes. Our customers did contact Sophos and a few told us that Sophos told them to whitelist the 127.0.0.x address.

The browsers sandbox the extensions (isolating them from different extensions and from the file system), so there's no way for our extensions to access your data file directly, thus the extension is forced to communicate with the main 1Password app through a localhost connection.

Until Sophos can release an update to allow you to whitelist specific apps/processes or web browsers allow extensions to access file system completely (not likely to happen due to widespread issues with malware), there is no fix coming on our side.