Actually it's cool that it was forked. But qt5 apps have pretty bad fonts view on my xfce desktop especially with black themes like Ark dark. That's why I am on KeepassX so far.
KeePassXC 2.3.0 released
101–105 of 105 posts
Re: KeePassXC 2.3.0 released
#102Earlier quoted context omitted.
Last week I started reverse engineering the KDBX 3.1 file format (for fun) . Does anyone knows where is the specification for KDBX 4.0? EDIT: Found it — https://github.com/keepassxreboot/keepassxc-specs
I don't believe the XML format has changed at all. Just the key derivation, stream cipher, and some changes to the binary header.
The XML Format has changed. Entries and Groups now support custom data. This was only supported on the database in KDBX3.1. Also, the settings now have a modified date which makes synchronising them when merging databases a lot easier.
The other changes are done to the binary format as you say. Also to make the file smaller, attachments are now stored compressed "as is" instead of encoding them in base64 and adding them to the XML structure.
Re: KeePassXC 2.3.0 released
#103Serious question: why should I leave KeePassX ?
It's in my opinion just a straight upgrade from KeePassX. Not a significant upgrade, but switching is probably not going to require significant effort either.
Re: KeePassXC 2.3.0 released
#104Anybody have thoughts about where to store the encrypted database for backup? Would it be foolish to keep the database somewhere publicly accessible?
There is one gotcha that you need to think about that hasn't been mentioned. If you back up your password database online, and your master file is lost in a fire, you need to be able to access the online backup service without requiring your password manager. You either need to remember the password for the online backup service, or you need to have another copy of the file in a remote location that you can access ph…
That's a good one to be prepared for.
I don't know what Dropbox's account recovery procedure is (which does have a support ticket system available), but if you also back it up to Google Drive; you can recover the Google account by an automated phone call to a specified number.
Accessible off-site backups are obviously good, but for various reasons it's unlikely everybody does this so I think the method above should be reasonable.
If it's something as dire as a fire where all devices including the phone are lost (by the way, for Android I favour Keepass2Android which comes with Dropbox syncing & fingerprint reader support), you would probably need to get replacement identity documents as well as a new phone & SIM card for the same number (it's probably quicker in the meantime to have the Google Account Recovery robot call another number you've previously listed to reset a 2FA/password).
Additionally, I don't think using a Diceware passphrase is a bad idea so long as it's never reused. After all, a solid passphrase is required for the password database, so learn two (or three - quick local system login might also handy). The process with real dice is quite fun to do and feels meaningful enough that it's adhered to and memorised.
I think a combination of no more than a few Diceware passphrases combined with password manager-generated passwords for all other sites is a balanced option. For typed passphrases, I no longer use anything except Diceware - not only are they easier to remember and enter, they're also more "expendable" and don't require any particular attachments to be formed since the generation process is robust and unbiased (unlike "hashed" passages from books and song lyrics).
For English-speakers, I recommend the EFF's list linked at http://world.std.com/~reinhold/diceware.html
Re: KeePassXC 2.3.0 released
#105Previous thread about KeepPassXC 2.2.0: https://news.ycombinator.com/item?id=14633576 I used KeePassXC for a period, but from these release notes, the UI/UX still isn't great. If you're on macOS, I recommend MacPass, which feels more native to the system, is compatible with existing KBDX databases and most-importantly, is also open-source: https://github.com/MacPass/MacPass
I was a little confused by your comment at first, maybe you didn't intend it that way, but I got the impression that you meant MacPass is open source, unlike KeePassXC. Except that KeepassXC is in fact open source: https://github.com/keepassxreboot/keepassxc/
I suppose you meant that MacPass is open source, unlike some other Mac password managers?
I didn't really check until someone downthreads mentioned that KeePassXC is (basically) a superset of KeePassX, which I know is open source because I use it as my password manager. So that means it's time for me to check out KeePassXC :) See what it does for me :)