claudiodekker/ungoogled-chromium-macos

Automated, code-signed builds of https://github.com/ungoogled-software/ungoogled-chromium-macos

ungoogled-chromium-macos's Issues

Even with this version of Chromium added to 1Password's trusted browsers, the extension won't auto unlock. Why?

Answer: Because 1Password is very dishonest about their actual browser support, to put it mildly.

They claim that "it should be up to you to decide which vendors and applications you trust to connect to 1Password and access your data", and repeatedly mention you can add additional trusted browsers in 1Password for Mac as long as they’re code signed by Apple.

Furthermore, they state that "Browsers which are based on Chromium should be able to use the Chrome extension", but as we're able to observe, this clearly isn't the case.

Taking a closer look at their own log files, we can see that the reason for this is due to the fact that 1Password is creating NativeMessagingHosts files for a hardcoded list of browsers:

INFO  2023-12-18T17:52:01.587 ThreadId(12) [1P:ssh/op-ssh-config/src/lib.rs:309] agent not configured
INFO  2023-12-18T17:52:01.589 ThreadId(12) [1P:native-messaging/op-native-core-integration/src/lib.rs:568] Enabling BrowserHelper with bundle id: 2BUA8C4S2C.com.1password.browser-helper
INFO  2023-12-18T17:52:01.595 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-native-core-integration/src/lib.rs:329] Starting IPC listener on 2BUA8C4S2C.com.1password.browser-helper
INFO  2023-12-18T17:52:01.595 tokio-runtime-worker(ThreadId(8)) [1P:op-ipc/src/ipc/xpc.rs:77] XPC starting connection
INFO  2023-12-18T17:52:01.596 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /Users/$USER/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.1password.1password.json
INFO  2023-12-18T17:52:01.596 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /Users/$USER/Library/Application Support/Google/Chrome Beta/NativeMessagingHosts/com.1password.1password.json
INFO  2023-12-18T17:52:01.596 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /Users/$USER/Library/Application Support/Google/Chrome Canary/NativeMessagingHosts/com.1password.1password.json
INFO  2023-12-18T17:52:01.597 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /Users/$USER/Library/Application Support/Google/Chrome Dev/NativeMessagingHosts/com.1password.1password.json
INFO  2023-12-18T17:52:01.597 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /Users/$USER/Library/Application Support/Microsoft Edge/NativeMessagingHosts/com.1password.1password.json
INFO  2023-12-18T17:52:01.597 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /Users/$USER/Library/Application Support/Microsoft Edge Beta/NativeMessagingHosts/com.1password.1password.json
INFO  2023-12-18T17:52:01.597 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /Users/$USER/Library/Application Support/Microsoft Edge Canary/NativeMessagingHosts/com.1password.1password.json
INFO  2023-12-18T17:52:01.598 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /Users/$USER/Library/Application Support/Microsoft Edge Dev/NativeMessagingHosts/com.1password.1password.json
INFO  2023-12-18T17:52:01.598 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /Users/$USER/Library/Application Support/Vivaldi/NativeMessagingHosts/com.1password.1password.json
INFO  2023-12-18T17:52:01.598 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /Users/$USER/Library/Application Support/Arc/User Data/NativeMessagingHosts/com.1password.1password.json
INFO  2023-12-18T17:52:01.598 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /Users/$USER/Library/Application Support/Mozilla/NativeMessagingHosts/com.1password.1password.json
INFO  2023-12-18T17:52:01.598 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:83] Successfully installed all native messaging manifests.

One could initially argue this is based on detection of what browsers are installed, but it even installs manifests files (and creates folders) for browsers you've never ever installed. Go ahead and check.

Fortunately however, this also means that in order to "fix" it for Chromium, all you'll have to do is create a 1Password NativeMessagingHost manifest file for it. The easiest way to do so is to simply copy Chrome's:

mkdir -p ~/Library/Application\ Support/Chromium/NativeMessagingHosts/
cp ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.1password.1password.json ~/Library/Application\ Support/Chromium/NativeMessagingHosts/com.1password.1password.json