Vlad sbeaz I believe this needs to be resolved by Bitwarden.
Two main things need to change on Bitwarden's side:
See this commit which adds support for Chromium in the same way.
There is one complication. Orion supports both Chrome and Firefox extensions. The json
file that is missing is different depending on browser. Bitwarden defaults to the Chrome version and makes an exception for FF.
I can imagine two options:
- Orion decides to only support the Chrome or FF version of the Bitwarden extension. Bitwarden would then need to make either no logic changes (if Orion exclusively support Chrome version) or a very minor logic change (if Orion exclusively supports FF version, just adding
|| 'Orion'
in a single conditional)
- Orion continues to support either version. In this case, Bitwarden would need to be able to determine which version of the extension was installed in Orion. Does Orion expose this information? I kinda hope it doesn't as it sounds like a potential security issue. Perhaps Orion maintains a very simple JSON file in
NativeMessagingHosts
called orionExtensions.json
which looks something like this:
{
"bitwarden": {
"version": "Firefox"
}
}
This way, Bitwarden needs no additional entitlements to determine which version of the extension is installed - it will already have read access to this file. Reading a JSON file is pretty straightforward; hopefully Bitwarden wouldn't mind some minor special handling like this.
If any other extensions in the future need to use the NativeMessagingHosts stuff, it would hopefully be trivial to add relevant information to this file from Orion's side.
Edit: I don't understand how biometrics could possibly have ever worked in Orion because only the Bitwarden desktop app makes the JSON files, and it doesn't have permission to access the directory where they need to go to work...