1password and blisk

@muddauber: We definitely don't support Blisk. This is actually the first I've heard of it, so thanks for bringing it up! Firefox and Chrome are fully supported though. And since Blisk seems to support Chrome extensions, you can technically use 1Password there by disabling the code signature check (under 1Password Help > Advanced). It isn't something we recommend since this is an important security feature for verifying a browser's authenticity, it's a workaround you can use if you choose to. I hope this helps!

Hi @muddauber,

We do understand that but we can't feasibly support and test every browser there is on the market to confirm they're safe to use with our extensions. We give you the option to disable the security check but we can only support the most popular ones that covers most of the market share. We'll see what we can do for Blisk.

Hi @jb510,

Thanks for writing in.

+1 on Blisk support. It's just Chromium underneath so support would be easy to add to 1P.

It's not about the ease of adding support for them, it's a matter of trust behind whitelisting an unknown browser by default. It means that if Blisk or anyone else get breached, sell it to someone else, etc, they have the power to do whatever they want in the code; such as pushing an bad update and 1Password would continue to whitelist it, which could mean your extension could push data to their servers without your knowledge.

Hi @jb510,

That's something we're aiming for in the future. I don't know if you're using 1Password 6 yet but if you are, check out Settings > Options > Browsers.

Basically, we now keep a list of currently authorized browsers and rejected attempts as well. You can click on each one to remove to de-authorize it and so on. It may be possible for us to add a Whitelist option and even with a time limit, like we'd like you to reauthorize once every 6 months or so. As you said, new browsers come and go and one of the problems is that we have to ship updates to update our certificates list, which mean bad browsers may linger around longer. So, with this process, it can work much better and phase out old browsers much quicker.

Hi @jb510,

Sorry, I'm referring to 1Password 6 for Windows (this is the Windows forum), not macOS. We're trying it out first in the new 1Password 6 for Windows app and if it works out, we might add it to the macOS version too. However, in the macOS version, you can disable the code signature check via the 1Password Menu > Preferences > Advanced tab.

Here's what 1Password 6 for Windows shows:

Ah, thanks for explaining that. Have you seen the option to disable the code signature and see if 1Password works now in Blisk on your Mac?