So it isn't that Brave issued an update and the mere act of updating broke things, its that certain details about the certificate and the bundle ID changed. Signing certificates change infrequently compared to updates to the browser and any certificate can last for a number of years. This list must be updated as browsers change but only in terms of the signing certificate. 1Password contains a hardcoded list of known browsers.

Like 1Password's own components the browser must have a valid code signature, the copy in memory must be the same as on disk and the code signature must be one known to 1Password. The code signature check I referred to is a check that 1Password performs on both itself and its various components as well as the originating process connected to the extension i.e the browser. The extension being able to run in a browser does not mean that 1Password will accept the connection attempt. Hi do my best to address the various points.īeing based on Chromium merely means that the Chrome extension should work in terms of being installable and running without error. I'm not sure how the signature check works exactly, but if another major browsers push an update, will this break things as if AgileBits has an official legacy support policy could you point me to it? Many thanks! actually there's just one more thing', but at the end of the day these decisions should be made from the customers perspective.ġPassword6 is effectively broken for me now. I guess the question I have is - what is the official AgileBits stance on support for anything other than the most recent version of their desktop app? 1Password6 is just one version away from the latest version - does that mean AgileBits doesn't care about it anymore? I know how hard it can be when you tell the engineering department they are done working on a particular version, and then later come back to them and tell them 'well. If that's the case than the issue should be trivial (ish) to address! I mean, I'm sure it involves a bunch of testing and what not, but at least it's not an unknown issue.

Brave browser mac