Hi,
I've just copied the KeePass2 portable files to X:\PortableApps\KeePassPortable\ , and my problem is the KeePass v1 exe is originally called KeePassPortable.exe but KeePass v2 exe is called KeePass.exe if I rename it to KeePassPortable the V2 plugins are not working at all, how can I modify the PortableApps menu to open KeePass.exe by default?
Thanks is advance!
Regards,
Zoltán
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
First of all you are copying the app to the wrong location, you need to copy it to install dir/App/keepass.
Secondly - Even then KeePass and KeePass 2 are two completely different apps - the original is coded in C++ (which has little to no requirements on the host system) while KeePass 2 is coded in C# (which requires the .NET Framework on every computer you want to run it on).
It may also mean that KeePass 2 will not be portable (in regards to settings and personal data) when placed in the KeePass Portable package. It may also mean that KeePass 2 won't even work without significant changes to the portable package.
Also I believe that the database format of KeePass is not compatible with KeePass 2 (although I may be wrong) so any databases you had in KeePass will not work with KeePass 2.
I think you can import a database(v1) into v2, so they will work in fact...
Never tried it though, I stick with Keepass2 portable (from site) myself and KeePassDroid
Yes, I set the working directory!
Last I checked, nothing supported the new KeePass 2 database format except KeePass 2. Did KeePassDroid add support for it? I thought it was difficult in non-.NET languages.
Sometimes, the impossible can become possible, if you're awesome!
KeePassDroid did add support for KeePass2 databases (read and recently write). I didn't test it yet, since I didn't need it yet, but others did test it and it seems to work.
from here:
Do you support KeePass version >=2, .kdbx databases?Yes. Beta read-only support for .kdbx databases was added in KeePassDroid 1.5.
also here.
Yes, I set the working directory!
Ah, it's still considered a beta. Last I checked everything supported kdb and nothing at all supported kdbx. Beta support is a start. I use it directly off my microSD, so both KeePassDroid and KeePass Portable use the same database, but I wouldn't want to trust it to beta support.
Sometimes, the impossible can become possible, if you're awesome!
The KeePass Droid app has had read-only support for kdbx for some time; the write support is a new feature not yet considered fully stable. (Not surprising; the consequences of something going wrong in read-only mode are obviously a lot easier to control and less dire if they do strike.)
If the government wants us to respect the law, it should set a better example.
How about this one:
https://www.keepassx.org/
It is KeePass 2 database compatible, can import KeePass 1 databases, it is Open Source and does not use .Net.
Cheers
Gremlin
Any chance of this being revisited?
The compatibility for other OS's has picked up significantly.
The .Net requirements is built in for Windows 7+.
KeePassDroid now also supports read/write for KDBX databases
Portability is meant to come out of the box for the portable ZIP version provided by the main dev.
PortableApps.com Advocate
I don't suppose it'd be possible to "portablize" .net, or would you want to ?
Blessed_Healer
Ok, so we have an official portable version of KeePassv2, and we're unable to add it in to the Portable Apps launcher is pretty much strictly because of .net framework is not portable, is this correct? The launcher is not able to just execute KeePassv2 and get out of the way, or what exactly? Do I need to just add it to my flash drive and launch it independently?
Blessed_Healer
The problem is that (at the moment) the Launcher has no way of knowing if the .NET dependencies of any given app are met, so on one PC you could launch a .NET app and have it run just fine, then on the next PC the same app would silently die, no errors, no warnings, thus giving a terrible user experience that we are not willing to introduce into an officially released app.
.NET detection is on the list of upcoming features, but so are a lot of other things too, and with only one person really working on the programming side of PortableApps, sometimes new features can be a long time coming.
Unfortunately we also cannot legally make the .NET Framework portable, although the relicensing of a subset of the .NET Framework earlier this year (or was it late last year? I forget) gives some hope for the possibility (but no certainty) of a legally portable .NET dependency in the future.
.NET 2.0 has been included in Windows since Vista, and since Microsoft ended support for XP everyone has since moved on to keep getting security updates. Since all Windows boxen have .NET 2.0 wouldn't that fulfill the requirements for KeePass v2 being portable?
Not everyone has upgraded their Windows. There are still a large number of XP installations around the world in corporate environments, hotel business centres, internet cafes etc.
We still accomodate quite a few users who need to make use of outdated computers on a regular basis, so we aren't willing to change our current acceptance criteria just yet.
.NET 2.0 is in Vista and 7 by default. It is disabled on Windows 8 and 10 by default and can only be enabled by an administrator. So the same situation applies. .NET is effectively neutered in terms of portable software.
That said, some .NET 2.0 apps can be written well and checked against .NET 3.5 and 4 and then bundled with a manifest allowing them to run on all 3 major versions without modification. KeePass 2 does this. So, we're going to shortly be releasing these so-called universal .NET apps as portable and available in the standard directory by default since they'll run on Vista through 10 without any changes to the host PC. I just need to finish coding the platform checks for this to happen. Then later we'll release standalone .NET apps that require a specific version but have them hidden by default.
Sometimes, the impossible can become possible, if you're awesome!
Could you please reconsider this?
We're talking about security measures here and 2.x version gives much better security against key loggers.
It can be something experimental or something like Chrome 64.
Thank You.
I second this request. KeepassXC isn't extensible enough to cover al everyday use and keepass 1 is just unsafe. Please make it possible to use keepass 2.