The process with real dice is quite fun to do and feels meaningful enough that it's adhered to and memorised. After all, a solid passphrase is required for the password database, so learn two (or three - quick local system login might also handy). 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).Īdditionally, I don't think using a Diceware passphrase is a bad idea so long as it's never reused.
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.Īccessible 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. The website looks clean, is user-friendly with up-to-date documentation, and a is plainly visible in the README on GitHub.Īs a result, I feel a bit better about the long-term prospects of KeePassXC over KeePass 2. In contrast, KeePassXC is hosted on GitHub, development is done out in the open, and it's trivial to see that in just the last year there were. Similarly, the website is ancient and doesn't seem to have kept up with the times I seem to recall it was only recently that it even got HTTPS support.
As a result I'm not really sure how to gauge the level of activity on the project itself. The seems to be an outdated SVN repo which was last updated in 2009, and I don't see any description of how to contribute code to the project anywhere. KeePass 2 seems to still be hosted on Sourceforge, and I'm not even sure where to get a copy of the latest (non-release) version of the source. I'm strongly considering it just based on the community surrounding each project.
0 kommentar(er)
