smorks / keepassnatmsg

KeePass plugin to expose credentials securely to a browser using Native Messaging

*** KeePassNatMsg is in maintenance only mode ***

I don't personally use this plugin anymore, therefore it is currently in maintenance mode, which means I will fix critical bugs, and will still accept PR's. I'm also open to passing this project on to a new maintainer, see the relevant discussion topic.

KeePassNatMsg

is a plugin for KeePass 2.x and provides a secure means of exposing KeePass credentials to a browser via Native Messaging.

It is based on KeePassHttp.

This plugin is primarily intended for use with the keepassxc-browser browser extension.

Features

• returns all matching entries for a given URL
• updates entries
• secure exchange of entries
• notifies user if entries are delivered
• user can allow or deny access to single entries
• works only if the database is unlocked
• request for unlocking the database if it is locked while connecting
• searches in all opened databases (if user activates this feature)
• Whenever events occur, the user is prompted either by tray notification or requesting interaction (allow/deny/remember).

System requirements

• KeePass 2.17 or higher
• For Windows: .NET Framework 4.0 or higher
• For Linux: Mono 4.0 or higher
• For Mac: Mono 4.0 or higher (untested)

Installation

1. Download the latest KeePassNatMsg release
   • Arch Linux (AUR): https://aur.archlinux.org/packages/keepass-natmsg/
2. Unzip it into the KeePass\Plugins directory
   • default directory in Ubuntu14.04: /usr/lib/keepass2/
   • default directory in Arch: /usr/share/keepass
3. On linux systems you maybe need to install mono-complete: $ apt-get install mono-complete (in Debian it should be enough to install the packages libmono-system-runtime-serialization4.0-cil and libmono-posix2.0-cil)

• Tips to run KeePassNatMsg on lastest KeePass 2.31: install packages sudo apt-get install libmono-system-xml-linq4.0-cil libmono-system-data-datasetextensions4.0-cil libmono-system-runtime-serialization4.0-cil mono-mcs

4. Restart KeePass
5. Go to Tools -> KeePassNatMsg Options
6. Click on "Install/Update Native Messaging Host", wait for message telling you it was installed.
7. Install the KeePassXC-Browser extension for your browser, and Connect to the database from within the extension.

Chocolatey 📦

Or you can use Chocolatey to install it in a more automated manner:

choco install keepass-plugin-keepassnatmsg

To upgrade KeePass Plugin KeePassNatMsg to the latest release version for enjoying the newest features, run the following command from the command line or from PowerShell:

choco upgrade keepass-plugin-keepassnatmsg

KeePassNatMsg on Linux and Mac

KeePass needs Mono. You can find detailed installation instructions on the official page of KeePass.

Configuration and Options

KeePassNatMsg works out-of-the-box. You don't have to explicitly configure it.

• KeePassNatMsg stores shared public keys in "KeePassNatMsg Settings" in the root group of a password database.
• Password entries saved by KeePassNatMsg are stored in a new group named "KeePassNatMsg Passwords" within the password database.
• Remembered Allow/Deny settings are stored as JSON in custom string fields within the individual password entry in the database.

Settings in KeePassNatMsg options.

You can open the options dialog with menu: Tools > KeePassNatMsg Options

The options dialog will appear:

General tab

1. show a notification balloon whenever entries are delivered to the inquirer.
2. returns only the best matching entries for the given url, otherwise all entries for a domain are send.

• e.g. of two entries with the URLs http://example.org and http://example.org/, only the second one will returned if the requested URL is http://example.org/index.html

3. if the active database in KeePass is locked, KeePassNatMsg sends a request to unlock the database. Now KeePass opens and the user has to enter the master password to unlock the database. Otherwise KeePassNatMsg tells the inquirer that the database is closed.
4. expired entries are ignored if enabled.
5. KeePassNatMsg returns only these entries which match the scheme of the given URL.

• given URL: https://example.org --> scheme: https:// --> only entries whose URL starts with https://

6. sort found entries by username or title.
7. removes all stored permissions in the entries of the currently selected database.
8. Shows the status of the Native Messaging Host installations for the supported browsers, and the current Proxy version.
9. Installs or Updates the Native Messaging Host, and updates the Proxy if an update is available.

Advanced tab

10. KeePassNatMsg no longer asks for permissions to retrieve entries, it always allows access.
11. KeePassNatMsg no longer asks for permission to update an entry, it always allows updating them.
12. Choice of databases used for searches:

• Use only the active database (default).
• Use all open databases.
• Always use a specific database.

13. When activated, it will search all string fields beginning with "URL".
14. if activated KeePassNatMsg also search for string fields which are defined in the found entries and start with "KPH: " (note the space after colon). The string fields will be transferred to the client in alphabetical order. You can set string fields in the tab Advanced of an entry.
15. Override the version returned to KeePassXC-Browser
16. When a database is selected, KeePassNatMsg will always use the selected database to search for entries.
17. Use the same settings as KeePassXC. If checked, it will share all Allow/Deny lists and keys with KeePassXC.

• It is strongly recommended that you make a backup of your database before using the Migrate Settings and Check for Legacy Config buttons.
• Migrate Settings: will migrate settings between KeePassNatMsg and KeePassXC.
• Check for Legacy Config: will check to see if any legacy config exists in the current database, and migrate it to the new CustomData format.

Keys Tab

Will display all configured browser keys, and you can remove them as needed.

Tips and Tricks

Support multiple URLs for one username + password

This is already implemented directly in KeePass.

1. Open the context menu of an entry by clicking right on it and select Duplicate entry:

2. Check the option to use references for username and password:

3. You can change the title, URL and everything of the copied entry, but not the username and password. These fields contain a Reference Key which refers to the master entry you copied from.

TOTP Field Support

KeePassNatMsg can use the built-in TOTP support in KeePass (since KeePass v2.47, official docs).

KeePassNatMsg can also use the existence of either KeeOtp (otp) or KeeTrayTOTP (TOTP Seed) string fields to detect when TOTP entries should be returned in credential requests.

Troubleshooting

First: If an error occurs it will be shown as notification in system tray or as message box in KeePass.

Otherwise please check if it could be an error of the client you are using. For keepassxc-browser issues you can report an error here.

If you are having problems with KeePassNatMsg, please tell us at least the following information:

• operating system & version
• version of KeePass
• version of KeePassNatMsg
• error message (if available)
• used clients and their versions
• URLs on which the problem occur (if available)

URL matching: How does it work?

KeePassNatMsg can receive 2 different URLs, called URL and SubmitURL.

CompareToUrl = SubmitURL if set, URL otherwise

For every entry, the Levenshtein Distance of his Entry-URL (or Title, if Entry-URL is not set) to the CompareToURL is calculated.

Only the Entries with the minimal distance are returned.

###Example: Submit-Url: http://www.host.com/subdomain1/login

Entry-URL	Distance
http://www.host.com/	16
http://www.host.com/subdomain1	6
http://www.host.com/subdomain2	7

Result: second entry is returned

Protocol

• View detailed protocol information.

keepassnatmsg's Issues

Can't connect to KeePass through the browser extension

Repost from KP discussion.

Hello, Andy! Thanks for the plugin, but it doesn't work for me at all. I've added it to KeePass\Plugins directory, installed Native Messaging Host for Google Chrome and Firefox. But browser extension can't connect to KeePass. What's wrong?

My config: Windows 10 x64 version 1903 (build 18362.356), KeePass version 2.4.3 (Dev. 190924), Cent Browser x64 version 4.0.9.112 (based on Chromium 74.0.3729.169), Firefox Quantum x64 version 69.0.2. Chrome extension version 1.5.2, Firefox extension version 1.5.1.

Browser error message:

Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings.

and after several clicks on "Reload" button:

Key exchange was not successful.

Database unlock prompt not appearing

Hi,
I've been using KeePassHTTP-connector ever since Firefox transitioned to web extensions. I just switched over to giving KeePassNatMsg+KeePassXC-browser a try. For the most part it works great, one of the best things about the XC addon is that it detects dynamically-generated password fields like the old PassIFox addon used to.

However I've noticed that unlike KeePassHTTP, it doesn't seem to prompt KeePass to unlock the database. I'm not sure if this is the fault of the KeePassXC-browser extension or KeePassNatMsg, but since this is considered "beta" I thought I'd ask here first.

Instead of unlocking the database, it just times out:

I have this option enabled:

Let me know if there is any more info I can provide, or if you cannot repro the issue. Not sure if this is something unique to my setup (Firefox 57.0.4, KeePass 2.38, Windows 7 x64).

Thanks,
Luke

Problem saving passwords...

Whenever I use the keepassxc-browser extension with this plugin to save or update a password, the program actually saves, but right after that an error message pops up, and also doesn't allow the keepassxc-browser function to ask where to save, it is an expected issue related to this plugin?
I am using Keepass 2.43, Keepassnatmsg 2.0.8 and keepassxc-browser 1.5.4.

custom logon fields

Hello,
I've found a little bug on the dialog to define custom logon fields.

I use the proxmox system for hosting virtual machines. The logon screen shows 6 fields.

By selecting the button to define the fields they will be detected correctly.

After select the username field as user for the username only on field remains.

So I can't define the custom fields :(

focus problem if "Always On Top" is enabled

Hi,
I have used KeePass 2.42 since yesterday and changed from KeePassHttp to KeePassNatMsg. First: Great job!!! Especially filling Http Basic Auth with multiple entries in KeePass worked perfectly.

But, if you enable "Always On Top" and you open the "KeePassNatMsg Options" the options screen appears, gets focus, but the "Always On Top" function lays keeps over the Options screen, but the Input focus stays on the KeePassNatMsg Options screen. It's difficult to explain, the best is you try it by yourself :)

best regards.
Willi

URL Regex search issues

The URL Regex search will never work if the URL Regex is the only way to identify the host (see #45 (comment))

Need to research some alternative options to fix this.

OK I give up how to install this plugin on windows

Ok I feel silly to ask but how to get this this plugin installed in keepass. The releases are in binary format and I'm used to .pglx placed in plugins folder. I tried placing it in the plugin folder after extracting it and placing it in C:\Users\userredacted\AppData\Local\KeePass\PluginCache? Just gives a message that it is incompatible

Totp auto fill isn't working

I can't use the totp filler feature of the keepassxc-browser plugin.
I don't know if it's normal or not.
I tried to add a field "KPH: {TOTP}" but that does not change anything.
It works as a string field if the totp request is on the same page as the password. But for website like Amazon it doesn't work.
Thank you for your help

I'm Using Keepass 2.4 with Keepassnatmsg plugin

Extension fails to connect to database after first successful connection

Expected Behavior
The extension connects to an unlocked database, and continues to do so even after the browser restarts.

Current Behavior
The extension behaves as expected immediately following successful installation from the chrome extensions store, but then breaks once the browser is closed. Upon a restart of the browser, the extension will be stuck saying that it has not been configured, even though it has been successfully configured already.

Steps to Reproduce (for bugs)
keepassxc-browser successfully installed from chrome extensions
Extension makes pop-up window requesting access to the database
Unique identifier given and access granted to extension
Tried logging into a website, extension works.
Closed Chrome.
Restarted Chrome.
Opened extension menu.
Dialog with error message saying that it is not configured, thinks it needs to connect again.

Workaround
Create new database connection
Press Cancel
Database is now connected, but extension doesn't report database connection name.

Software Versions
Windows 10
Chrome 69
keepassxc-browser 1.30
keepass 2.40
keepassnatmsg 2.0.1

[https://github.com/keepassxreboot/keepassxc-browser/issues/277](keepassxc-browser related issue)

Support for Edge based on Chromium

Hi,
is it possible to support edge based on chromium?

I can not connect to the keepass database with the extension keepassxc from microsoft store.

KeePass doesn't quit until the browser is closed, on linux

tested in Fedora 27 Desktop with mono 4.8

Black Options window when opening Options twice on Ubuntu

after opening the options window once, then either pressing Ok or Cancel, then opening it again opens a Black window, which can't be closed.

AUR Package

I've created an aur package for this plugin: https://aur.archlinux.org/packages/keepass-natmsg/
Maybe link to it in the readme for arch users?

Can't connect to database KeePass 2.4.2, KeePassXC-Browser 1.4.3, Chrome 73.0.3683.103

Disregard; it seemed to work after hitting Install/Update a few times in the plugin options.

Timeout or not connected to KeePassXC

Since moving over to the KeePassNatMsg plugin with the Firefox add-on 'KeePassXC-Browser' I keep getting periods when the add-on reports

Timeout or not connected to KeePassXC

I suspect, but cannot prove, that this relates to the keepassnatmsg plug-in for KeePass in as much as I can occasionally resolve the problem by accessing the keepassnatmsg options and updating the Native Message Host.

However, the truth is that this is a hunch and nothing more.

I just fixed it this morning by deleting the plugin, reinstalling and then updating the Native Message Host. But that was with the same versions of everything previously installed.

I could switch the KeePassXC program and not use the plugin but there are several UI things I regularly use with KeePass that XC doesn't offer.

Has anyone else any experience of this. In an hour or two it is quite possible that all will be well again.

PlugIn Beta 10
Browser Add-on 1.0.1
KeePass 2.38
Firefox 59.0.2
Windows 10

Unable to connect to KeePassXC-Browser

Windows 10
Chrome 64
KeePass 2.38
keepassnatmsg 2.0.0.6
KeePassXC-Browser 1.0.0

After clicking the connect button on KeePassXC-Browser, nothing happens. On the extension debugging page, it shows Failed to connect: Access to the specified native messaging host is forbidden.

"The following plugin is incompatible with the current KeePass version"

Keepass 2.3.7 On windows 7 SP1
.NET Framework 4.7.1

What's not working?

pressing Cancel in the Associate dialog still associates with the browser extension

URL Matching is not working

Entry-URL Distance
http://www.host.com/ 16
http://www.host.com/subdomain1 6
http://www.host.com/subdomain2 7

Result: ALL are returned ! I have checked Return only the best matching entries !!!

Just doesn't seem to work with Chrome, Windows

Hi,

Re-installed windows yesterday, been using KeePassHttp extension for a while but figured I will try this one since the other one is no longer supported.

operating system & version: Windows 10 - latest
version of KeePass: 2.4.1
version of KeePassNatMsg: v2.0.5
error message (if available): none unfortunately
used clients and their versions: Chrome Version 74.0.3729.108 (Official Build) (64-bit)
URLs on which the problem occur (if available):
Here are some URL's that I am sure were working before and also have the top level domain as login page. All my URL's in KeePass include schemes.
https://insights.hotjar.com/
https://www.smartlook.com/sign/in
https://www.ups.com/lasso/login?loc=us_EN

Settings:

Not receiving any notifications, tried restarting chrome and keepass once more didn't help.

System.Net.Sockets.SocketException (0x80004005): Address already in use error after Native Clients installed.

KeePass 2.36, Fedora Core 27 64-bit, Mono 4.8, KeePassNatMsg 2.0.0.8 beta

After installing the KeePass native clients, the following error occurs:

$ keepass
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: cHRM chunk does not match sRGB

Unhandled Exception:
System.Net.Sockets.SocketException (0x80004005): Address already in use
at System.Net.Sockets.Socket.Bind (System.Net.EndPoint localEP) [0x0004c] in :0
at KeePassNatMsg.Protocol.Listener.UnixSocketListener.RunThread () [0x0000e] in <8796423c47e14fc1a650938792f80e72>:0
at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in <373b6e083d6e45e498c9082a8eebd27f>:0
[ERROR] FATAL UNHANDLED EXCEPTION: System.Net.Sockets.SocketException (0x80004005): Address already in use
at System.Net.Sockets.Socket.Bind (System.Net.EndPoint localEP) [0x0004c] in :0
at KeePassNatMsg.Protocol.Listener.UnixSocketListener.RunThread () [0x0000e] in <8796423c47e14fc1a650938792f80e72>:0
at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in <373b6e083d6e45e498c9082a8eebd27f>:0
at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in <373b6e083d6e45e498c9082a8eebd27f>:0

This error does not occur when starting keepass under sudo or running as root.

KeePassXC-Browser Save Options don't work

The following options don't actually do anything when set:

• Default group for saving new passwords
• Always ask where to save new credentials

todo:

• implement "get-database-groups" action
• implement "create-new-group" action
• update "set-login" action to support groups

Warning message after unlocking database

I grabbed the latest release and tried out the automatic database unlocking with keepassxc-browser. It works, except after unlocking the database, KeePass throws up a message box:

After acknowledging it, everything seems to work just fine. The KeePass database is unlocked and the browser integration works fine. I'm not really sure where the message box is coming from (beyond the keepass.exe process). Is it possible the KeePassNatMsg plugin is causing it? It just started happening with beta 5, and I've never seen it before with KeePassHttp.

Let me know if there is any other info I can provide.

Thanks,
Luke

Support for KeeTrayTOTP entries

In #22 @smorks mentioned that the TOTP auto fill requires KeeOtp to be installed.
I'd kindly ask for support for KeeTrayTOTP, too.
It's the successor/fork to TrayTOTP, and has comparable features to KeeOtp, but is under active development, allows copying TOTP codes via the tray icon etc.
It stores the relevant data in two extra fields, called TOTP Seed with only the key inside, and TOTP Settings with data like "30;6" inside, meaning 30 seconds, 6 digit code.

Thanks for your work on this!

Not work with the version 1.5.0

It does not work with the latest version of the browser extension for Keepassxc 1.5.0 browser

"Match URL schemes" doesn't work with http:// when "Search in all opened databases" is enabled

Hi!
As the title says when both Search in all opened databases for matching entries and Match URL schemes are enabled KeePassNatMsg doesn't return credentials for entries having an http:// scheme when visiting their respective websites.

I've tried the following, when both are enabled:

• https:// works and return entries from both databases
• http:// doesn't work and doesn't return any entry

When only Match URL schemes is enabled and Search in all opened databases for matching entries is disabled:

• https:// works and return entries from the "active" database
• http:// works and return entries from the "active" database

I don't know if this bug also happens with the upstream version because I don't use multiple databases with KeePassXC, only with KeePass 2 but I could test it later if needed!

I hope I've been clear enough with my explanation, if you need more information don't hesitate to ask!

Proxy settings for installation

When I try to install the Native Messaging Host I get a proxy error:

I tried several proxy settings in KeePass (2.41) itself and at path level (Windows). Both didn't work.
Can you please use the same proxy as KeePass or give a possibility to enter one?
I also found no way to fake the download (putting the keepassnatmsg-proxy.exe to C:\Users<username>\AppData\Local\KeePassNatMsg) and getting it to work behind a proxy. (I saw in the source code that you always check the version no.).

Automatically save after modifying permissions

When granting permission to an entry, the entry is modified (the "KeePassHttp Settings" string field), but the database is not saved, even if the KeePass option "Automatically save after modifying an entry using the entry editing dialog" is selected. It would be nice if KeePassNatMsg could (a) respect the same option, or (b) add its own option to "Automatically save after permissions are updated".

Incompatible with KeePass 2.40

Current version's binaries (2.0.1) do not work with newly available KeePass 2.40 and gives the following error message:

Probably just need to recompile.

Proxy download error

I get this error from screenshot on 2 clients than I install the Native Messaging Host.

System:

• Linux Mint 19 Cinnamon
• KeePass 2.41 and 2.42.1
• KeePassNatMsg 2.0.5
• Mono: mono_pkgs.txt

Steps to reproduce:

• download and extract KeePassNatMsg 2.0.5
• move into plugins directory
• start KeePass
• install Native Messaging Host

Add support for Lock/Unlock messages, should prompting to unlock when browser is opened

There should be an option to choose auto connection to keepass app while opening browser. It is very good experience if it will connect to keepass while autofilling user/pass. We can disable this auto connection to app. It can be manually do it while filling user/pass data. Because when i open browser or new tab it will ask me to unlock db. It is bad experience.

I cannot successfully install the Native Messaging HOST due to an SSL error on Proxy

Following the install instructions, I receive this response from the installer:

What do I need to do to resolve this? Or can I install these native bits manually?

Allow multiple URL's for a single password entry

Feature Request.

Would it be possible to implement extra URL's to be handled for a single password entry, probably via the "String Fields" page, similar to how KPH string entries work for additional password fields?

Something like KPURL and then the string value can be the URL.

It could hopefully then allow for regex matched URL's to be added as well.

Use case example:

HP have numerous login pages between Learner ID, channel services, partner portal, unison, passport, expert one, etc... And I've got separate entries (using references) for all these currently, as they all seem to want different URL's for credential entry.

Would be nice to tidy all that up.

Regex use case is that there is no wildcard support, which is troublesome when using the more exact URL detection - particularly when companies tend to do odd things like:
www.website.com
ww1.website.com
ww2.website.com
www.website.net

It'd be good to be able to have the URL field as https://www.website.com and then the ability to capture the variations using regex.

Custom strings error

If i add custom string KPH: 1gfhgd to my entry in keepass db no credentials are returned to KeepassXC plugin in firefox
If i remove KPH: from entry credentials are returned, but without no custom string :(

Locking the database through keepassxc-browser freezes KeePass

Hi again,
Not sure if this is the fault of KeePassNatMsg or not. I noticed that if you click the lock button in the keepassxc-browser extension, the KeePass process stops responding. After killing it, the keepassnatmsg-proxy process crashes. Then I have to relaunch KeePass.exe and restart Firefox for the two to communicate again.

Thanks,
Luke

Status doesn't seem to load, probably related to github deprecating tls 1.0 & 1.1

cannot install with keepass 2.43 (same as #52 with more info)

• operating system & version: Windows 10 Version 2004 OS build 19041.329
• version of .NET: 4.8
• version of KeePass: v2.43
• version of KeePassNatMsg: v2.0.10
• error message (if available)
  
• used clients and their versions: n/a
• URLs on which the problem occur (if available): n/a

I get the above message when starting KeePass after having copied the plugin. And there's no KeePassNatMsg entry in the tools menu.

I did verify my .net installation with the MS diagnostic tool, everything checks out.

Cannot connect with latest version

I gave beta 4 a try, but I cannot get KeePassXC-browser to connect to it at all. After I upgraded from beta 3, and restarted KeePass, the keepassnatmsg-proxy.exe process crashed. I deleted it and re-created it with the new version, but the browser extension still cannot connect to it at all, even after restarting Firefox. I just get a timeout error:

I tried taking a look at the crash dumps, but I don't have the symbols and I haven't look into how to build/deploy it myself.

I'm going to revert to using beta 3 for now, but let me know if there is any more info I can provide.

Use KeePassXC-Broswer custom data instead of KeePassHTTP attributes

KeePassXC 2.4.0 recommends to move KeePassHTTP attributes to KeePassXC-Broswer custom data, they also provide an option to move for all entries.

Related KeePassXC PR: keepassxreboot/keepassxc#1497

I'm using both of KeePassXC and KeePass on Windows, while I feel like it's hard and unnecessary to maintain both of KeePassHTTP attributes and KeePassXC-Broswer custom data in my db. This plugin can probably also do so, to better support both apps.

Following KeePassNatMsg's installation procedure: KeePass crashes when clicking "Tools -> KeePassNatMsg Options"

Title

Following KeePassNatMsg's installation procedure: KeePass crashes when clicking "Tools -> KeePassNatMsg Options"

Context

On Ubuntu 19.10, KeePass is installed from the package manager. KeePassNatMsg is downloaded and installed manually. Crash happens when accessing --- from KeePass --- the menu "Tools -> KeePassNatMsg Options".

Observed behaviour

A black window opens for a few seconds; KeePass crashes.

Expected behaviour

A window opens providing a "Install/Update Native Messaging Host" button.

Steps to reproduce

On Ubuntu 19.10, open a terminal:
0. Install KeePass: sudo apt install -y keepass2
Follows KeePassNatMsg installation instructions:

1. Download the latest KeePassNatMsg release
2. Unzip it to /usr/lib/keepass2/Plugins/
3. Install mono sudo apt install -y mono-complete
4. Restart KeePass
5. Go to Tools -> KeePassNatMsg Options

Crash.

Details & Versions

• OS version: Ubuntu 19.10 (cat /etc/os-release)
• Mono version: 5.18.0.240 (mono --version)
• KeePass version: KeePass 2.41 (keepass2 --version)
• KeePassNatMsg version: 2.0.9 (KeePassNatMsg-v2.0.9-binaries.zip)
• KeePassNatMsg files' rights:

yscialom@Kloe:/usr/lib/keepass2/Plugins$ ll
drwxr-xr-x 2 root root 4,0K févr. 21 22:34 KeePassNatMsg/
yscialom@Kloe:/usr/lib/keepass2/Plugins$ ll KeePassNatMsg/
-rwxr-xr-x 1 root root 105K févr. 21 22:34 KeePassNatMsg.dll
-rwxr-xr-x 1 root root  78K déc.  21  2017 Mono.Posix.dll
-rwxr-xr-x 1 root root 514K déc.  21  2017 Newtonsoft.Json.dll

KeepassXC-browser needs manually pressing reload to work and keepassnatmsg crashes when Keepass is being closed.

To start from have quite unusual Setup - Windows 7 pro with Firefox, but in Windows, I have 2 accounts (Admin and user), but FF profile is installed in the location accessible for both, so I have one KeepassXC-browser instance used in two Accounts.

Some time ago I installed KeepassXC-browser and KeepassNatMsg plug-in. I opened both in Admin account, checked KeepassNatMsg options, and pressed "Install/Update Native Messaging Host". It worked and browser-application connection was automatic.

Then I re-logged to user account. Connection was not automatic so I pressed reload - not working.
I entered the options KeepassNatMsg options from user account and pressed "Install/Update Native Messaging Host". It got installed and remains like that.

However, there are two issues:
Browser extension does not recognize that Keepass is running - I have to press reload to make it work.
When I close Keepass, I receive error message like the one below:
"Program keepassnatmsg-proxy has stopped to work"

Details screen shows this:

Podpis problemu:
  Nazwa zdarzenia problemu:	CLR20r3
  Podpis problemu: 01:	keepassnatmsg-proxy.exe
  Podpis problemu: 02:	0.0.6.36827
  Podpis problemu: 03:	5b7cbc06
  Podpis problemu: 04:	System.Core
  Podpis problemu: 05:	4.7.3221.0
  Podpis problemu: 06:	5b885a82
  Podpis problemu: 07:	533
  Podpis problemu: 08:	61
  Podpis problemu: 09:	System.IO.IOException
  Wersja systemu operacyjnego:	6.1.7601.2.1.0.256.48
  Identyfikator ustawień regionalnych:	1045
  Dodatkowe informacje 1:	35ac
  Dodatkowe informacje 2:	35acd98331d5de5a95eef5c6b00f8ca5
  Dodatkowe informacje 3:	291d
  Dodatkowe informacje 4:	291d5960c7b5535e8443bace076f326f

These issues are not deadly, as the program itself works, but I'd be glad if these are fixable :)

System: Windows 7 x64 professional PL
Browser: Firefox x64 current branch (currently 64.0.2)
Keepass: Keepass 2.40
KeepassXC-browser - current (1.3.2)
KeepassNatMsg - 2.0.3

Update documentation & screenshots

use proper screenshots and review all documentation.

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

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

KeePass opens and shows the information is accessible.

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

Change the native messaging host name

keepassxc-browser 0.4.5 is the last version using native messaging host name com.varjolintu.keepassxc_browser. Please change it to org.keepassxc.keepassxc_browser. The updated version of the browser extension using this host name has been already released.

KeePassXC-Browser will only work if KeePass2 is launched beforehand

KeePassXC-Browser can only see KeePass 2 when KeePass 2 was already running before the extension started. So in order to make the extension work, I need to shut the browser down, run KeePass and then launch browser again.

Cannot connect to database via keepassxc-browser 1.1.3

With the latest version of the keepasscx-browser extension, I cannot connect to the KeePass database anymore. Clicking the "Connect" button on the settings page in the browser extension does nothing.

OS: Windows 10 (1803)
Keepass version: 2.39(.1)
KeepPassXC-Browser: 1.1.3
Native Messaging Host: 0.0.5.38780

KeePassXC-Browser asks to be associated with database every few days

I believe this has started since the last update of the browser plugin on chrome (1/11/19). Roughly every day or 2, the browser plugin reports an error. When I click refresh to connect to the database, it says there is no association and I have to reconnect the database with a new key association.

Cannot decrypt message

This bug has been difficult for me to reproduce. Sometimes the keepassxc-browser extension reports this:

The Reopen button has no effect. KeePass is running and the database is unlocked. The only thing I've found to fix it is restarting Firefox entirely (even disabling/re-enabling the extension had no effect).

This has happened twice so far, and I'm not sure if this is actually a bug with the extension or KeePassNatMsg. What do you think? If I can narrow down repro steps I'll post here.

Thanks,
Luke

XC Browser pestering for new version of keepassxc

I am using KeePass (2.41) together with keepassnatmsg and Keepass-XCBrowser plugin with Firefox.

Over the weekend the XCBrowser plugin has begun pestering for the latest version of KeepassXC which I've never used preferring the original KeePass program.

I'm wondering if keepassnatmsg spoofs the version of KeepassXC or whether I am gradually being forced to use KeePassXC. the Firefox XC-Browser plugin reports that I have version 1.3.2 of KeePassXC installed although it is not installed at all.

Add support for the keepassxc-mail add-on in Thunderbird

KeePasXC-Browser doesn't work correctly for me in Thunderbird, so I decided to use the recently created keepassxc-mail add-on. This currently requires some manual interaction:

• Copy the file kpnm_firefox.json in %LocalAppData%\KeePassNatMsg to kpnm_thunderbird.json and change the name and allowed_extensions value (sample file)
• Add a new registry key de.kkapsner.keepassxc_mail under HKEY_CURRENT_USER\SOFTWARE\Mozilla\NativeMessagingHosts and point the (Default) value to the previously created file

Could you please add support for these steps in the KeePassNatMsg options dialog so that happens automatically?

Also, the add-ons author noticed a difference in behavior between how KeePassXC and KeePassNatMsg handle native messages: kkapsner/keepassxc-mail#11 (comment) This may be expected behavior, but it also could be a bug in KeePassNatMsg.