While KeePassXC remembers all stored passwords, one should not forget the master password to unlock the safe. The previous version (*.kdb) may still be imported. This file should be backed up, for example to a thumbdrive or into the cloud. KeePassXC stores the entire database in one file with the extension *.kbdx at a location of your choice. It even introduces a new browser plugin called KeePassXC-Browser that integrates with Chrome/Chromium, Firefox and Vivaldi, providing improved security for the exchange of login data compared to its predecessor KeePassHTTP. Since KeePassX seems not really actively maintained, its fork KeePassXC is the recommended alternative to go for. It’s advantage is that is does not rely on Mono. Unlike the original KeePass program for Windows, which was also available as a Linux port, KeePassX is a complete rewrite.
My use case described above is one of possible use cases where a password in fact reasonably needs character exlusions.KeePassX is an open-source password safe for Linux, Windows and OS-X. I really encourage you to provide an option to exclude characters from the password generation. This can lead to a lot of try and error cases until a password is accepted by Ansible. Repsecting my current experiences I'm often generating a password multiple times (in my case passwords of a length of 50) until I can assure the password doesn't contain any unwanted characters. For example I experienced problems if the password includes characters like `, ^, \ and others.Ĭurrently KeepassXC provides options to activate very wide ranged sets of characters for new passwords. This requires to provide the Ansible Vault password by a shell script which can lead to unexpected side effects while the passwords can contain special shell interpreted characters. I'm actually using KeepassXC to provide ansible vault passwords in a vagrant provisioning process. But I really took care of your needs while writing my request.
I'm sorry I'm not able to provide you with an feature request in your desired way.
0 kommentar(er)
