unidentified publisher on windows on a VM + VPN

eeyoredragon

I can't use the Firefox extension with 1password. "firefox by unidentifed publisher , process ID ${correct.firefox.proc.id}"

• Windows 10 is running in a VM (Parallels 12)
• This is not a corporate managed machine, so everything installed is mine/unmodified
• I'm connected to a corporate VPN via Cisco AnyConnect which I have setup to allow unsecured LAN access
• If it matters, I am using the following 1Password configuration
  ** Main Teams account
  ** The VM uses a guest account that only contains work related credentials/data. (This all works other than the extension.)

Any idea on debugging this?

---

1Password Version: 6.1.308
Extension Version: 4.6.3 b1
OS Version: Windows 10
Sync Type: Teams

MikeT

Hi @eeyoredragon,

Thanks for writing in.

When you said allow unsecured LAN access, do you mean the 127.0.0.1 address is excluded from the VPN client?

Beside the VPN, what anti-malware solution are you using on your computer?

1Password can't read the process to see if its code signature is correct, which means something's blocking 1Password from reading it. Usually, this is caused by the anti-malware solution and VPN would just prevent 1Password from ever seeing the connection from the 1Password extension because the traffic is routed via the VPN rather than the localhost address, so it never gets to 1Password.

eeyoredragon

Due to some IT issues, I had to connect to the VPN with a second laptop which booted my VM connection.

I'm supposed to keep the second laptop connected for a few hours. I'll test it again tomorrow.

Thanks :)

EDIT: The loopback address should be included yes, but I can't see the routes until I get connected again.

AGAlumB

Ah, I see. Be sure to let us know what you find!

eeyoredragon

Ok, so I got connected to the VPN again today, and lo and behold it's working fine. So apparently a reboot fixed it. I should be used to this on Windows by now...

Works great. Thanks, guys.

AGAlumB

Ok, so I got connected to the VPN again today, and lo and behold it's working fine. So apparently a reboot fixed it.

Good to hear! hopefully you don't run into any further issues. I'd be lying if I said I haven't had my own share of VPN-related woes...

I should be used to this on Windows by now...

Oh dear. I don't know whether to laugh or cry. :lol: :cry:

Works great. Thanks, guys.

Likewise, thanks for the update! We're here if you need us! :)