Chromium + MacOS: key exchange not successful

[QuantumQuill]

KeePassXC Browser extension can connect to the KeePassXC App, but can not do a successful key exchange.
KeePassXC settings allow browser extension support for Chromium.

KeePassXC-Browser - 1.7.9.1 ( oboonakemofpalcgghocfoadofidjkkk )
Operating system: MacIntel
Browser: Chromium 88.0.4324.150 (x86_64)
KeePassXC - Version 2.6.6
Revision: 386b79a
Qt 5.15.2
macOS 10.15
Kernel: darwin 19.6.0

• Auto-Type
• Browser-Integration
• SSH-Agent
• KeeShare
• YubiKey
• TouchID
• libgcrypt 1.9.3

~/Library/Application\ Support/Chromium/NativeMessagingHosts/org.keepassxc.keepassxc_browser.json contains:
{ "allowed_origins": [ "chrome-extension://pdffhmdngciaglkoonimfcmckehcpafo/", "chrome-extension://oboonakemofpalcgghocfoadofidjkkk/" ], "description": "KeePassXC integration with native messaging support", "name": "org.keepassxc.keepassxc_browser", "path": "/Applications/KeePassXC.app/Contents/MacOS/keepassxc-proxy", "type": "stdio" }

path to keepassxc-proxy is correct, ID of chrome-extension is also correct

[varjolintu]

What happens if you try to start /Applications/KeePassXC.app/Contents/MacOS/keepassxc-proxy manually from the Terminal?

[QuantumQuill]

I can execute it, but it kind of hangs. also CTRL + C is not interrupting it.

[varjolintu]

Strange. Everything should be in order then. Does it matter if you enable Chrome support also?

[QuantumQuill]

I tried all variations of Browser Support activation. Turning them all on/partially on/all off. It always shows the same error.

[varjolintu]

What does the browser JavaScript Console say?

[QuantumQuill]

keepass.js:1059 Connecting to native messaging host org.keepassxc.keepassxc_browser
keepass.js:1029 Failed to connect: Access to the specified native messaging host is forbidden.
keepass.js:1262 Error: No content script available for this tab.
keepass.js:1142 Error 5: The connection to KeePassXC is not possible. Check if the browser integration is activated in the KeePassXC settings.
keepass.js:1142 Error 5: The connection to KeePassXC is not possible. Check if the browser integration is activated in the KeePassXC settings.
keepass.js:1059 Connecting to native messaging host org.keepassxc.keepassxc_browser
keepass.js:1029 Failed to connect: Access to the specified native messaging host is forbidden.
keepass.js:1262 Error: No content script available for this tab.
keepass.js:1142 Error 9: Key exchange was not successful.
keepass.js:1262 Error: No content script available for this tab.

[varjolintu]

Interesting. Please check that the Chromium path and the JSON scripts are with correct user permissions. Seems something or someone has possibly changed them?

Also, this error might be seen if the extension ID doesn't match with the JSON script, but according to your first issue message, this is not the case.

[QuantumQuill]

check that the Chromium path and the JSON scripts are with correct user permissions.

No idea how to do that.

[varjolintu]

check that the Chromium path and the JSON scripts are with correct user permissions.

No idea how to do that.

Use Finder, right-click the folder and/or file and select Get Info. There should be a section called Sharing & Permissions at the bottom.

[QuantumQuill]

~/Library/Application\ Support/Google/Chrome/ and ~/Library/Application\ Support/Chromium/ contains only NativeMessagingHosts with org.keepassxc.keepassxc_browser.json. I have read + write permissions everywhere.

nothing else keepass related there

[varjolintu]

Then please double check the extension ID you have installed in Chromium using chrome://extensions. Did you use the official Chrome Web Store for it?

[QuantumQuill]

it is: chrome://extensions/?id=nmmcabpmnkjefgdkfbjpaadfffhpplmf
I extract the extension from the store with "Chrome extension source viewer" and install it manually afterwards.

[varjolintu]

@euakll In that case you must manually modify the JSON script file and add/edit that extension ID to it.