61–70 of 105 posts
I highly recommend https://keeweb.info/ if you're looking for an attractive, easy to use, cross-platform and Open Source solution. I've been using it on Windows and MacOS for years without any major issues. It's by far the best looking front-end for keepass databases I've seen.
Electron apps ...
Earlier quoted context omitted.
I store the .kdbx (database) file on a network synced folder (e.g. like dropbox or gdrive). However, I use a "key file" in addition to a password. The key file is not synced and remains on computers that I control. I also have a backup copy on external media.
Aren't you worried about that fact that any program you run could potentially read all your passwords using the key file?
Anybody have thoughts about where to store the encrypted database for backup? Would it be foolish to keep the database somewhere publicly accessible?
Just ensure you have a few million key transformation iterations to really harden it against bruteforcing attempts.
In reality, though, given that you can never be 100% sure you don't have a keylogger or other malware, you shouldn't really volunteer half the keys to the kingdom (= the database) to the world.
Actually, if you handle third party data this could even be a breach of regulations (think HIPAA)
If you use Keepass on something like Dropbox it's a blessing.
Is it worth to migrate from Keepass2 to this? Any interesting user experiences?
I'm strongly considering it just based on the community surrounding each project. 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. The [Sourceforge repo][1] 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. As a result I'm not…
They do make the source available with each release, and a user has mirrored them onto GitHub [3]. I also cannot find the source for older releases.
[1] https://sourceforge.net/p/keepass/discussion/329220/thread/0...
[2] https://sourceforge.net/p/keepass/discussion/329220/thread/b...
Earlier quoted context omitted.
I'm strongly considering it just based on the community surrounding each project. 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. The [Sourceforge repo][1] 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. As a result I'm not…
source code is available at https://keepass.info/download.html (scroll down to "Other Downloads and Resources")
With KeePassXC for example, even though the latest release came out less than a day ago I can see that there have already been [14 commits][1] to the `develop` branch since that release. I can't find the equivalent of such a branch for KeePass 2.
[1]: https://github.com/keepassxreboot/keepassxc/compare/2.3.0......
Previous 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
Also macPass is compatible with Keepass database 1.0, unlike KeepassXC.
Does anyone know what the license is for this software? It looks like there are NINE different license files in the repo: https://github.com/keepassxreboot/keepassxc Did they just copy paste every different license they could find into the repo?
This comment is really funny and made me laugh.
Anyway we are following the Debian guidelines. The full copyright for each component and file is specified in the COPYING file in the root of the repository along side with each author.