OS X 10.10, 1Password 5, Chromium [known bug; disabled "Verify browser code signature" not honored]

arnaud_

Hi,

I try to use 1password with chromium without any succes.
I try disabling code signature verification but i always get the same message about it ...

Any idee what can i try ?

PS: I try in 2 computers ... same result

fago

Got the same issue here. Have you found any solution for this problem?

arnaud_

nop ...

ravenac95

I too am having the same issue. Is there a way we can file some kind of ticket with the agilebits devs?

sjk

Hey guys,

I've been able to reproduce this issue and was investigating its cause with one of our developers. We're still unclear what's happening, but this is possibly the easiest workaround:

After disabling the Verify browser code signature option under 1Password Preferences > Advanced, please restart your Mac and check if you're able to use 1Password with Chromium after that.

We'd appreciate hearing whether or not that works for you to get a better idea of what to suggest next if it doesn't.

Reporting issues here on the forum, or through email using one of the Contact Us links on the AgileBits Support page, is the best way to do it. I've filed a detailed internal bug report that includes what's been reported here, @ravenac95, plus additional results of my testing.

Thanks for your help and patience with resolving this.

ref: OPM-2470

Unknown

This content has been removed.

sjk

Hi @LosInvalidos,

What you've described sounds like a bug that's been reported when using version 38 of Chrome, which would also apply to Chromium 38. From @Megan's comment about it:

We have been tracking an issue where Chrome and 1Password don't seem to play nice in the first Chrome tab. Opening a second tab usually behaves as expected. You don't mention how many tabs are open when you see this behaviour - might this issue explain your troubles as well? We do suspect that this one is related to a change in Chrome, but if you're seeing something different, please let us know and we'll investigate further. :)

Later in the same discussion, Michael Vilain mentions:

I downgraded to Chrome 37 and autofill works just fine. Google messed with autofill on 38.0.2125.104 and it doesn't work with 1Password.

One of our developers has also noticed the same thing with Evernote's web clipper extension, so it's not only an issue with 1Password and appears to be a bug in Chrome/Chromium.

We don't have a solution yet but I hope that information is helpful.

ref: CSI-22

Unknown

This content has been removed.

sjk

Hi @LosInvalidos,

I wasn't assuming that this is a Chrome/Chromium bug, only suggesting the possibility that it might be. The developer who noticed it with Evernote's web clipper may have already submitted a bug report to Google about getting it fixed on their end. And we already have it filed in our tracker, intended to be fixed regardless of who's bug it turns out to be.

ravenac95

@sjk Even after a reboot of the system. Turning off "Verify browser code signature" option doesn't seem to have an effect.

sjk

Sorry that didn't work for you, @ravenac95. Thanks for letting me know.

We're still checking on another possible workaround for this until there's a full fix. I'll post more information once we have it.

ravenac95

@sjk Thanks so much!

arnaud_

same issue here ... reboot doesnt help

fago

Tried a reboot and installing chromium and 1password new - without success.

Rad

Hi guys,

Scott and I spent some time trying to figure this issue out. Fortunately, we were able to reproduce it. This is the first step towards fixing it.

We filed an internal bug in our issue tracker and are currently trying to find a temporary workaround. We'll post more information as soon as we know more.

Thanks!

Rad

ref: OPM-2470

Unknown

This content has been removed.

sjk

Nothing yet, @LosInvalidos. Thanks for checking. Like Rad said, we'll post more info once we have it. :)

Unknown

This content has been removed.

sjk

Hi @LosInvalidos,

There doesn't appear to be any difference with Chromium 38.0.2125.111. Just to confirm, have you already tried what I suggested earlier?

After disabling the Verify browser code signature option under 1Password Preferences > Advanced, please restart your Mac and check if you're able to use 1Password with Chromium after that.

Unknown

This content has been removed.

sjk

Sorry that didn't work for you, @LosInvalidos. I hope you're able to use 1Password with one of the supported browsers (Safari, Chrome, Firefox, Opera) until this problem is fixed.

ravenac95

@sjk or @Rad Is there any update on this? Also, I'm going to make a request for a slightly different workflow for the "Verify browser code signature" option. I think it would be safer if you could somehow let only SOME applications make requests to 1password. This way people don't have to disable "Verify browser code signature". Instead some kind of list of exceptions is optionally kept internal to the app. Though, perhaps that's also the same level of danger as disabling "Verify browser code signature".

Thanks again guys! Love your work!

Rad

Hi @ravenac95‌,

Thanks for the followup and for the kind words. You're awesome! :+1:

We found a fix and squashed the bug since 5.1.BETA-1. If you are using the web store version and wish to test our latest beta, you can Enable beta builds in Preferences > Updates and check for updates.

The fix is should be available in the upcoming version of 1Password for Mac.

Best,

Rad

stuartmcintyre

Great that you have a solution to this. Any idea when an updated version will make it into the App Store?

Cheers

Rad

Hi @stuartmcintyre‌,

We are planning to submit the upcoming version of 1Password 5 for Mac to the Mac App Store really soon. We cannot give you a specific timeframe because there are several external factors that we do not control.

Thanks!