Time sink 2 1. Find the KeePassXC-Browser plugin, install it: Go to the Settings: Default group for saving new passwords – usually, I’m disabling the default KeePassXC-Browser Passwords and enabling this option to be always asked where I’d like to save a new password as in my database everything is divided over groups. An installable version is also available: KeePassXC runs on: Windows 10 32/64 bit Windows 8 32/64 bit Windows 7 32/64 bit Windows Vista 32/64 bit file size: 42.5 MB filename: KeePassXC-2.6.1-Win32.
Team
The KeePassXC team is formed by
Keepassxc 2 5 1000 Btu
Contact
You can contact us via [matrix], a free chat protocol. We have two channels, one for user questions and one for development-related discussions:
#keepassxc:matrix.org
Element.io web chat (user's channel)#keepassxc-dev:matrix.org
Element.io web chat (developer's channel)
Please be patient when asking a question! You may not get an immediate answer, but someone will respond to you eventually.
In case you prefer it old-school, we also have the two equivalent IRC channels
#keepassxc
and #keepassxc-dev
on chat.freenode.net
, which are synced with the [matrix] channels above.#keepassxc
web chat (user's channel)#keepassxc-dev
web chat (developer's channel)
Antetype 1 7 1. Please note that due to excessive spam in the past, you need to register your nickname with NickServ before you can talk.
If you need to report a security issue, please email us. We prefer these reports be sent with PGP-signed/encrypted email. Please do not (!) send user questions, bug reports or support requests to that address (that's what [matrix], IRC, and our GitHub issue tracker are for).
Legal Info / Impressum
Janek Bevendorff
Friesstr. 1
99423 Weimar, Germany
legal 'AT` keepassxc ^DOT' org
No user questions, please! Legal or otherwise confidential correspondence only!
Friesstr. 1
99423 Weimar, Germany
legal 'AT` keepassxc ^DOT' org
No user questions, please! Legal or otherwise confidential correspondence only!
![1000 1000](https://1.bp.blogspot.com/-4I1rCUZMycA/Xbg8uf5nJFI/AAAAAAAADdo/hJEorXvtWcw1xk9-4pujEynpYR6b5o3KACLcBGAsYHQ/s1600/keepassxc.png)
Team email PGP key:
105D 8D57 BB97 46BD
Please note: We are an international team who speak a few different languages and we will use Google Translate if needed (mind your privacy!), but it's easiest for us to respond to English emails. Thank you!
Keepassxc 2 5 1000 Mg
(Full disclosure: I contribute to KeePassXC)In fact, KeePassXC has shown to have better memory protection than KeePass: https://keepassxc.org/blog/2019-02-21-memory-security/ (note the article is from February, some things have changed since then, see below).The only thing we do not have at the moment is in-memory encryption. We do, however implement the following security measures on all platforms:
- prevent swapping of master key hashes (using gcry_malloc_secure)
- prevent non-root / admin access to our process memory (KeePass does NOT have this)
Keepassxc 2 5 1000 Meters
- overwrite all dynamically allocated memory with zeros on free
- disable any kind of coredump or crash reporting
A patch for in-memory encryption is being worked on, but needs further testing before it can be merged: https://github.com/keepassxreboot/keepassxc/pull/3055
Please note that this still cannot fully prevent swapping out of secrets. As soon as things are to be displayed somewhere in the GUI, they are basically out of our hands. We also cannot fully protect everything while the database is being loaded or written. However, the same applies to KeePass. There is just too much going on with memory management on modern operating systems.