Closed rootbeer closed 1 month ago
I'm pretty sure this was not a KeeAgent issue (other than the obtuse error).
I "migrated" my portable KeePass installation to my new machine by physically moving the drive from the old machine to the new one. However, my user identity changed on the new machine, so the KeePass directory and the Plugins directory were owned by a different user, I'd futzed this into a readable state with takeown
, but not fully fixed the ACLs up. Resetting the ACLs on the whole KeePass directory (with icacls KeePass /reset /T
) seems to have fixed the problem.
Currently when I start KeePass (I'm on Windows 11, KeePass v2.56), the Update Check dialog box suggests the new version of KeeAgent plugin (v0.13.7). However, when I do update KeeAgent to v0.13.7, I get an error from KeePass. I've successfully updated KeePass and KeeAgent many times in the past, but I have not done so on this machine (a new Windows 11 host).
Here are my steps to reproduce this:
KeeAgent.plgx
from the KeeAgent_v0.13.7.zip into my ("portable") KeePass/Plugins
directory. This overwrites the existingKeeAgent.plgx
plugin in that directory.KeeAgent.plgx
back and KeePass is fine.Some earlier bugs (#201, #154), those ran into a similar looking problem, but on Linux, and the fix seemed to be installing some Mono compatibility stuff. I'm not sure if there is an equivalent for Windows, but it seems unlikely?
I'm happy to get more logs or try additional steps to isolate the problem. Its very easy for me to reproduce. Let me know if there are any details or logs I can provide. I've never built KeeAgent from source, but I'm willing to give that a try if that helps test a patch or something like that.
Here's my current KeePass "About" dialog:![image](https://github.com/dlech/KeeAgent/assets/144684/fd2fa872-486f-4d65-bca7-89c6ca0b891f)
(The stale KeePassHttp warning has been that way for a long time, I think its not related.)