search

smorks / keepassnatmsg

KeePass plugin to expose credentials securely to a browser using Native Messaging
GNU General Public License v3.0
271 stars 26 forks source link

"No Arguments Received" popup when opening browser or refreshing extension #53

Closed 9strands closed 4 years ago

9strands commented 4 years ago

KeePassNatMsg version: 2.0.9 OS: Fedora 32 x86_64 KeePass version: 2.45 portable

Issue: after the upgrade, when I open the browser, or if I attempt to refresh the keys, I get an error window pop up from the keepassnatmsg

image

KeePass opens and shows the information is accessible.

I have reinstalled the native messaging hosts as well, and it seems to have no effect.

9strands commented 4 years ago

From Chrome's background page for the extension: Connecting to native messaging host org.keepassxc.keepassxc_browser keepass.js:1065 Error 9: Key exchange was not successful. keepass.js:952 Failed to connect: Native host has exited. keepass.js:1185 Error: No content script available for this tab. keepass.js:1065 Error 5: Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings. keepass.js:1065 Error 5: Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings. keepass.js:982 Connecting to native messaging host org.keepassxc.keepassxc_browser keepass.js:1065 Error 9: Key exchange was not successful.

From Firefox: Sending message that cannot be cloned. Are you trying to send an XPCOM object? MessageChannel.jsm:1009:17 Error 5: Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings. keepass.js:1065:13 Promise resolved after context unloaded utils.js:25 Connecting to native messaging host org.keepassxc.keepassxc_browser keepass.js:982:13 Error 9: Key exchange was not successful. keepass.js:1065:13 Failed to connect: Unknown error keepass.js:952:13 Error 5: Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings. keepass.js:1065:13 Connecting to native messaging host org.keepassxc.keepassxc_browser keepass.js:982:13 Error 9: Key exchange was not successful. keepass.js:1065:13 Failed to connect: Unknown error keepass.js:952:13 Sending message that cannot be cloned. Are you trying to send an XPCOM object? MessageChannel.jsm:1009:17 Error 5: Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings. keepass.js:1065:13 Promise resolved after context unloaded utils.js:25 get moz-extension://cc4eac7a-5858-4fd7-bd05-2fd9159d969d/utils.js:25 Connecting to native messaging host org.keepassxc.keepassxc_browser keepass.js:982:13 Error 9: Key exchange was not successful. keepass.js:1065:13 Failed to connect: Unknown error keepass.js:952:13 Use of nsIFile in content process is deprecated. NetUtil.jsm:253:8 Error 5: Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings. keepass.js:1065:13 Connecting to native messaging host org.keepassxc.keepassxc_browser keepass.js:982:13 Error 9: Key exchange was not successful. keepass.js:1065:13 Failed to connect: Unknown error keepass.js:952:13

smorks commented 4 years ago

this appears to be an issue with the latest version of keepassnatmsg-proxy. manually downgrading to 0.0.6 (https://github.com/smorks/keepassnatmsg-proxy/releases/download/v0.0.6/keepassnatmsg-proxy.exe) fixed it for me, until i find the problem with the current version.

it appears to only affect mono as well, 0.0.7 works fine for me on windows.

smorks commented 4 years ago

i just released v0.0.8 of keepassnatmsg-proxy

https://github.com/smorks/keepassnatmsg-proxy/releases/tag/v0.0.8

hopefully that should fix this issue.

smorks commented 4 years ago

tested in ubuntu, works. closing issue.

GRbit commented 3 years ago

@smorks Please, tell me how to install keepassnatmsg-proxy manually on Linux? Seems like I have a problem with autoinstall P.S. sorry for the screenshot, I can't copy text from this window image

smorks commented 3 years ago

@GRbit see this issue (#11) for some commands you can try, and there's also instructions to download the proxy manually at the bottom. i will also add instructions to the readme for manually installing the proxy.

GRbit commented 3 years ago

Thanks, copying to ~/.keepassnatmsg helps.

P.S. I've tried to make the KeePassXC Firefox plugin work, now it connects to DB, but doesn't request my passwords when I'm loading any page, I don't know why. KeePassHttp-Connector plugin works better.

smorks commented 3 years ago

hmmm, that's strange. you're using the latest version of the KeePassXC-Browser? 1.7.9.1 appears to be the latest.

also, can you show me what's in the kpnm_firefox.json file in the ~/.keepassnatmsg directory?

GRbit commented 3 years ago

hmmm, that's strange. you're using the latest version of the KeePassXC-Browser? 1.7.9.1 appears to be the latest.

also, can you show me what's in the kpnm_firefox.json file in the ~/.keepassnatmsg directory?

Yep. It suggests saving the password after login, correctly saves it to the database, but on logout and page refresh it doesn't fill in my login or password. Tried to set up custom login/pwd fields - it doesn't help either.

smorks commented 3 years ago

it could be another extension causing the issue. have you tried disabling all other extensions except for KeePassXC-Browser?

if that still doesn't work, open a new issue with more details about your environment (OS, firefox version, etc) and i'll look into it.

GRbit commented 3 years ago

Tried in private mode with only KeePassXC-Browser extension version 1.7.9.1. I have no kpnm_firefox.json file in the ~/.keepassnatmsg directory.