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. 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. All rights reserved.I'm strongly considering it just based on the community surrounding each project. ShortcutRecorder Copyright 2006-2013 all Shortcut Recorder contributors NSBundle Codesignature Check Copyright 2014 Jedda Wignall. MJGFoundation Licensed under BSD 2-Clause License. TransformerKit Licensed under MIT license. All rights reserved.ĭDHotKey Copyright Dave DeLong. KSPasswordField Copyright 2012 Mike Abdullah, Karelia Software. PXSourceList Copyright 2011, Alex Rozanski. KeePass Database Library Copyright 2010 Qiang Yu. MiniKeePass Copyright 2011 Jason Rush and John Flanagan. HNHUi Copyright 2012 HicknHack Software GmbH. KeePassKit Copyright 2012 HicknHack Software GmbH. This Project is based upon the following work: Please open an issue if you think someone is missing from this list! Art The following list might not be complete, please refer to merged Pull Requests on GitHub for more details. App Storeĭue to being licensed under GPLv3 it's not possible to publish a version of MacPass on the App Store.įor further details, take a look at the explanation of the Free Software Foundation. You should have received a copy of the GNU General Public LicenseĪlong with this program. ![]() GNU General Public License for more details. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This program is distributed in the hope that it will be useful,īut WITHOUT ANY WARRANTY without even the implied warranty of The Free Software Foundation, either version 3 of the License, or It under the terms of the GNU General Public License as published by This program is free software: you can redistribute it and/or modify MacPass, a KeePass compatible Password Manager for OS XĬopyright (c) 2012-2017 Michael Starke (HicknHack Software GmbH) and all MacPass contributors Since it's browser based you can pretty much run it anywhere. More Screenshots in the Wiki Alternatives The Status can be found on the dedicated Wiki page. MacPass 0.7 requires macOS 10.10 Yosemite or later.Įarlier versions of MacPass require macOS 10.8 Mountain Lion or later. Or follow the Twitter account System Requirement ![]() Some questions might be answered in the FAQĪnother place to look is the IRC channel #macpass on ![]() Xcodebuild -scheme MacPass -target MacPass -configuration Release CODE_SIGNING_REQUIRED=NO NO_SPARKLE=NO_SPARKLE
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |