Submit portable freeware that you find here. It helps if you include information like description, extraction instruction, Unicode support, whether it writes to the registry, and so on.
I support 2 different entries, since they are obviously 2 different beasts (for the record, I'm still using KeePass 1.x to store some of my passwords).
How about adopting the wishes of the KeePass developers and calling them "KeePass Classic 1.x" and "KeePass Professional 2.x"?
We can list the latter as a separate entry and if enough people vote for it to become public, so be it, dotnet or not, as long as it is portable.
Midas wrote:KeePass audit: no critical security vulnerabilities found
I'm very happy with the increasing commonality of security audits like this one. I do still wonder what credentials make one qualified to perform one, but it's still a good direction.
There's an easy way to make KeePass 2.35 (id=2829) write the PluginCache in the application folder and not AppData\Local\.
Not a native english speaking guy, so edit it if i made any mistakes.
How to extract:
1. Download the "Portable" ZIP package and extract to a folder of your choice.
2. Launch KeePass.exe and close it again.
3. Delete AppData\Local\KeePass.
4. Open KeePass.config.xml in Notepad and look for the first <Application> and insert the following line under it
I tried starshakur's idea three separate times about making a plugin not write to the Appdata\Local folder, but I watched the Appdata\Local write the KeePass folder every time I loaded Keepass. I don't know how you modified your OS to accept the method, starshakur, but it doesn't work for me. I must stay with the native encryption methods of Keepass, ChaCha20 and Rijndael.
Do you still use your backup script?
I like to use it also, how do i tell Keepass to start it?
Yes, I do. I use the 'classic' version of Keepass since it was the only natively portable one (which isn't true anymore!) and I stuck with it -- ATM, I'm behind in updating, so still at v1.30 while v1.32 is out.
All you have to do is execute the batch file AFTER Keepass closes -- the easiest way is to use a yaP launcher just to run Keepass and then the script once it closes...