Multiple Keepass connections

[Red Dwarf]

I run multiple Firefox browsers with KeeFox but Keepass only supports one connection to the database according to the KeeFox plugin writer, so multiple instances of Keepass need to be run, one for each browser. This is a lot less than ideal both for a memory usage reason and for a database management reason. Updating the database in one Keepass instance won't sync with the other Keepass instances unless the database is saved, which is quite slow. This makes it pretty unusable with multiple browsers which are run for security reasons with different levels of security and different cookies depending upon sites.

Therefore is it possible to allow Keepass to make multiple connections, either only to KeeFox, or on pre-defined ports, or number of connections specified in the database/keepass options? Maybe this could be allowed as an option for security reasons.

BTW My Firefox browsers are Sandboxed so different KeeFox ports should be able to be used, having different settings for each browser/Keefox instance. It should also be possible using Firefox profiles if not sandboxed.

[pfn]

I don't think this is a limitation of KeePass itself, but KeePassRPC which is the plugin KeeFox uses to communicate with KeePass (speaking from the perspective of an unrelated observer).

[Luckyrat]

Spot on pfn0.

KeePassRPC needs a dedicated connection for each client that connects to it (in this and the only known case, KeeFox). To keep development simpler I've assumed only one of each "type" of client can be connected at the same time. This has probably led to the limitation of support for only one connection.

I haven't worked on that bit of code for around a year or more but IIRC it will be possible to change this; I just don't want to go messing with this part of KeePassRPC without thinking about the ramifications very carefully and I simply don't have time for that at the moment. It's certainly on my radar for a potential future improvement but right now there are other improvements that will have wider benefit to more people which I'll want to work on first (not to mention all the documentation and final polish I need to do before releasing version 1.0!).

Thanks,
Chris