Incomplete setup mis-detected because of naming of plugins directory

[schnittchen]

Sorry if this is a duplicate, I quickly searched for the problem but couldn't find it anywhere. This problem trips me up about every time a KeePass update happens.

As advised by the setup page, I have KeePass extracted to ~/KeePass and the plugin copied to the plugins subdirectory. However,

I always mess this step up because

• while the setup page clearly instructs to place the .plgx into the plugins subdirectory,
• KeePass (standalone) comes with and honors a Plugins subdirectory.
• and I usually don't read things exactly to the letter and rely on tab expansion in the shell instead.

I don't know how and when this discrepancy appeared, maybe it is there for a good reason.

Maybe it is feasible to support detection of the .plgx file in both subdirs. Possibly the plugins subdirectory should be deprecated.

[freaksterrao]

I think its an issue with KeePass. KeePass detects and loads the plugins from plugins folder. KeeFox connects to KeePass via TCP.

[schnittchen]

Oh right, I mixed the two together...

Which of these is the case:

1) KeeFox advises the wrong directory 2) KeePass extracts with a wrongly cased plugins directory

Or is there a third case?

[luckyrat]

Hi,

I've not had time to review this issue in detail but have chosen to paste this standard message below so that anyone interested can understand if no activity occurs until next year and why at that time we may close the issue.

First, please see http://keefox.org/news/detail/2017/09/19/introducing-kee-20

The issues that affect Kee 2.0 will be different to KeeFox 1.7 and even where the same issues affect both versions, the cause will usually be different.

This issue will not be addressed here unless it is specific to Thunderbird or a serious problem affecting Firefox 52 ESR. Please get in touch privately if you find a security flaw regardless of which Mozilla application it affects to ensure a process of responsible disclosure can be followed.

If the issue is still relevant in Kee 2.0 please raise an issue in the new repository. For issues relating to the web browser add-on, or when you are not sure, please use https://github.com/kee-org/browser-addon/issues. For issues that affect the KeePass plugin (KeePassRPC) please use https://github.com/kee-org/keepassrpc/issues

I appreciate this might be disappointing for some people watching tickets involving things you feel would be great improvements or fix irritating bugs and limitations with KeeFox 1.x but I hope you'll understand that it's not wise to spend time on a version of the add-on which will cease to function in the latest version of Firefox in a month.

If you want to express an opinion or emotion relating to this comment, please use the "reaction" buttons rather than writing a new comment if possible - that will make it easier to tidy things up in 2018 so we can spend more time improving KeeFox instead of managing project admin.

If you'd like to comment or ask about the more general migration plan and reasoning for Kee 2.0, please join in the discussion at https://github.com/kee-org/browser-addon/issues/1 if there is no more specific issue or forum for discussion.

Thanks, Chris

[github-actions[bot]]

Following the recent announcement of the end of critical security patch support for this old software - https://forum.kee.pm/t/keefox-critical-security-support-ends-30th-september-2020-kee-is-unaffected/3219 - this issue has been automatically marked as stale. We will soon close this issue and then archive this repository in early October 2020.

If you think that the issue contents may still be relevant to the actively maintained Kee project, the successor of KeeFox, please search the community forum for help and post a new topic if appropriate: https://forum.kee.pm

Please do not reply to this comment / notification - it won't be seen.