as I understand, KeePass is GPLv2. I'm looking for a way to let users open kdbx files (read-only) and provide access to the entries in my application.
My application is shareware and not open source, so I'm wondering if there's a way to provide access to those entries without violating GPLv2. I'm not creating another keepass clone for money. My tool is a remote management tool (Royal TS http://www.royalts.com) which has its own credential repository but many users are already using keepass and they are looking for a way to use those credentials in my app.
I've found a way to reference the .exe file in c# and with a couple lines of code, I'm able to get everything out I need. So my question is, if the user is obtaining a version of keepass, installs it, points my app to the .exe location, am I violating GPL if I do a late-binding to the assembly and invoke the keepass API?
Thank you for your response!
If you don't use any KeePass code you can do what you like.
Alternatively create a plug-in that sits between the apps and release the plug-in under GPL.
thank you for taking the time to respond. So, just referencing the .exe and calling the API doesn't violate GPL, right? If so, I may go this route.
The GPL is about the code in KeePass. As it has external hooks you can call them as you like.
Understood, thank you!
It would be nice when there would a standard plugin under LGPL available separate from Keepass to avoid that all third party closed source each installs a different plugin.
What would a "standard" plug-in do? Is it only for access to existing passwords and if so, how do you decide what fields to use?
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.