21–30 of 132 posts
This release looks great. Unfortunately I had to switch to LastPass to get sharing, real sync support rather than blob syncing in, and also easy usage on mobile.
Earlier quoted context omitted.
There doesn't seem to be active development on KeePass/KeePassX, hence the KeePassXC fork. The C in the fork title apparently stands for 'community'. It has a lot of support behind it.
No active development? I'm using KeePass on Windows (and have been for years) and I've just had a new update pushed (2.36)... Am I missing something?
So there's KeePass, KeePassX, and now KeePassXC? (And two different variants of KeePass that have nothing to do with each other.) Not that there's anything wrong with that. I'm just curious if KeePassXC is yet another fork, or if it's from the same people who did KeePassX. KeePassX has an excellent security reputation, so it'd suck if an unrelated fork ruined that.
There doesn't seem to be active development on KeePass/KeePassX, hence the KeePassXC fork. The C in the fork title apparently stands for 'community'. It has a lot of support behind it.
I'm getting the feeling that this uses the older protocol?
I got a good answer to the above question from desdiv so I'm adding an edit:
Is there a reason to use this (and not use this) in place of KeePass2 on Windows?
This release looks great. Unfortunately I had to switch to LastPass to get sharing, real sync support rather than blob syncing in, and also easy usage on mobile.
Decent mobile support is the only thing holding me back from switching. The current 3rd party options are underwhelming.
As someone using Keepass2 (mono on Linux), can someone knowledgeable briefly tell me (and probably others) why should and why should not I switch to KeePassX? I'm getting the feeling that this uses the older protocol? I got a good answer to the above question from desdiv so I'm adding an edit: Is there a reason to use this (and not use this) in place of KeePass2 on Windows?
Of course there could be other reasons.
This is by far the best of the KeePassX* lot, incorporating loads of enhancements which, disappointingly after years of development, never made it into KeePassX 2.x proper, and some 1.x features which simply disappeared in the upgrade. [Edit: missing word]
I say almost because I'm used to the original interface, but I'm sure after getting used to it, it will supersede it on my systems.
Physical object authentication is great except physical objects are less durable than brain memory (or at least, if my brain memory is gone then I probably would have no use for the password anyway).
Earlier quoted context omitted.
There doesn't seem to be active development on KeePass/KeePassX, hence the KeePassXC fork. The C in the fork title apparently stands for 'community'. It has a lot of support behind it.
KeePass (the original C# version) appears to actively developed. KeePassX (the C++ rewrite) appears to have slowed down. KeePassXC (the fork of the C++ rewrite) is the one under discussion here.