KeePassRPC no compatible with the upcoming KeePass version 2.42

1

The subject says it all.
Look at https://sourceforge.net/p/keepass/discussion/329220/thread/5ef408ed35/

2

Thanks for the heads up.

Dominik contacted me to let me know too and I see he has already made a change to ensure backwards compatibility with KeePassRPC so there’s nothing we need to do.

I’ve previously thoroughly tested 2.42 and found no problems. I’ve now tested with the latest 2.42 snapshot in case any other last minute changes have caused a problem and it all looks good so far. I’ll post an update in the unlikely event that any issues are found but assume that no news is good news.

Note that I’m only testing KeePassRPC 1.9 (1.8 should work too, and it did with an earlier snapshot of 2.42).

2 Likes
3

Hello, same for me here :

1
1.JPG559×537 77.1 KB

4

I don’t understand the error message but regardless there are only two broad causes for this:

  1. You’re running a development snapshot of KeePass 2.42. In which case, upgrade to the official release to fix the problem.
  2. It’s unrelated to this issue. Probably you have a broken .NET installation on your computer. Try re-installing the latest version and/or restoring Windows to factory settings.
5

First of all: Hello everywhere! :wink:

Same problem with KeePass 2.43

While everything was perfectly fine with v2.42.1, KeePass reports incompatibility with KeePassRPC and KeeCloud and refuses to load them.

Major issue, as Firefox integration (using Kee) and synchronizing via DropBox is not possible without them …

Any suggestions?

Thanks a lot in advance!

6

My problem with KeePass 2.43 and Chrome Kee Extension 3.2.7 is that Kee does not connect to KeePass after restarting the browser.

If I reinstall the extension and authorize again it is reconnected again but after restart no connection.

7

As I spent a lot of time on this specific issue - it might be an idea to document it.
This issue is caused by some protection that blocked some DLLs or the compiler. (SRP - AppLocker - GPO - Antivirus) The PLGX uses a subfolder in the %temp% folder and in the %localAppData%\KeePass\PluginCache\ folder.
So the KeePass PLGX files work is they are compiled every run at start. The trick is to catch the compiled files and drop those in the plugin dir:

What I did to solve this:

  1. Use a PC where the plugin does work. I used a clean, private pc in my case.
  2. Download the addin and drop it in C:\Program Files\KeePass Password Safe 2\Plugins\
  3. Start Keepass. It start to compile the plugin at start.
  4. Copy the content of the subfolder in %localAppData%\KeePass\PluginCache to C:\Program Files\KeePass Password Safe 2\Plugins\
  5. Remove the plgx file.

Now the built DLLs are in the plugins folder, it’s more compatible with strong protections + no need to rebuild them every run. This needs to be redone once every new release.

%localAppData%\KeePass\PluginCache = C:\Users*yourusername*\AppData\Local\KeePass\PluginCache