Kyrodan / KeeAnywhere

A cloud storage provider plugin for KeePass Password Safe

Home Page:https://keeanywhere.de

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

plgx version 2.0.3 will not work under Keepass v2.54

alabamatoy opened this issue · comments

Keepass 2.54 installed on Ubuntu 20.04.6 will not work, gives following error upon starting Keepass:
Screenshot from 2023-07-10 09-45-32
Keepass was installed using

sudo add-apt-repository ppa:ubuntuhandbook1/keepass2
sudo apt install keepass2

If the graphic is not visible, its a dialog box that states:

The following plugin is incompatible with the current Keepass version: /usr/lib/keepass2/plugins/KeeAnywhere-2.0.0.plgx

Have a look at the plugin's website for an appropriate version.

On some systems, the "mono-complete" package may be required for plugins to work properly.

I am reluctant to install a complete development environment, as I am not sure of what side-effects may occur.

Any help would be appreciated.

I had a similar issue in Windows 7 with Keepass 2.54 64-bit when I tried to load the last plugin version. I believe could be the same issue.

imagen

me too
keepass 2.54 and 2.53

image

window 10 64 bit

same issue windows 8.1 32bit

same issue windows 8.1 32bit

I did find solution. Install newer dot net. I installed 4.7.1 and it works.
there is probably version read problem. Because installed 4.7.1 but in regedit is this 4.7.03062.
The same was with 4.6.1 which is minimum acording release note, but in regedit was shovn 4.6.10? and after instalation 4.6.2 was shown 4.6.15?
KeeAnywhere has probably problem with version translation.
edit:
so still not working. plugin is loaded but any try to connect to cloud ends with freeze.
edit2:
it is needed to start keepass as administrator and than is possible to connect to cloud
This is really terrible user expearience :D I also ended with dot net 4.8

From my recent experience with KeePass 2.55 on Windows 11, it requires that KeePass is started with 'Admin' or 'root' privileges when initializing the plugin for the first time. My guess is it's because it needs access to the system's secure credentials storage. Once you have the credentials of your cloud provider authenticated and saved, you can start KeePass normally.

Windows 7 SP1 (64-bit) - Keepass 2.56 (64-bit) same incompatibility problem message.
Only works with .NET Framework 4.8 and need to run as admin the first time for compiling and for adding a new Google Drive account. Once installed and configured runs well with normal user.

@gabrielballone @cacophobe
To those who have found you need admin to connect, I have two questions:

  1. Is your user account capable of admin privileges or do you have to authenticate as a different user to run as admin? (for example, at home I click "run as admin" and the box just asks yes or no; at work, I click run as admin, and the box forces me to enter another username/password which I don't have so I have to call IT)
  2. What cloud provider are you using? Google Drive, by chance?
  • Is your user account capable of admin privileges or do you have to authenticate as a different user to run as admin? (for example, at home I click "run as admin" and the box just asks yes or no; at work, I click run as admin, and the box forces me to enter another username/password which I don't have so I have to call IT)

In my case, my user has admin privileges. I've just need to select "run as admin" and click yes.

  • What cloud provider are you using? Google Drive, by chance?

I'm using Google Drive. To get clear, I only need to "run as admin" to add a storage location and do the authentication process. Not for compiling/installing the plug-in. I need to do same procedure for any other cloud provider that I want to add. I've test it with Dropbox too.

@gabrielballone , maybe you and @mailyspamy are seeing the same issue as #301? That's my first thought when people say they needed admin rights to add an account. I'm not sure if KeeAnywhere actually uses the Windows credential storage, but I know I've never needed admin access to add accounts (except for the issue I linked of course), just for installing the plugin.

I'm not sure @cacophobe is seeing the same thing though. That issue has never been seen to affect Windows 10 (or later) before.