When bootstrapping self hosted infrastructure, you cannot rely on the presence of the services which you have not yet set up. So while your normal devops scripts can count on an OpenBao instance, your bootstrap scripts need something smaller and self contained.
Keepassxc has been perfect for this. A clean UI allows humans to navigate if needed, and keepassxc.cli provides enough surface to let a script generate a .env file as part of a bootstrap or disaster recovery process.
Can't imagine it would be too hard to make it support Vaultwarden as a backend? Surely an effort but with Bitwarden potentially going full commerical in near future, it would be nice to have a fully open stack as an alternative.
Part of the appeal of keepass is that it isn’t attached or involved with any other player in the space. If I wanted vaultwarden compatability i’d use something that already has it
When bootstrapping self hosted infrastructure, you cannot rely on the presence of the services which you have not yet set up. So while your normal devops scripts can count on an OpenBao instance, your bootstrap scripts need something smaller and self contained.
Keepassxc has been perfect for this. A clean UI allows humans to navigate if needed, and keepassxc.cli provides enough surface to let a script generate a .env file as part of a bootstrap or disaster recovery process.
Can't imagine it would be too hard to make it support Vaultwarden as a backend? Surely an effort but with Bitwarden potentially going full commerical in near future, it would be nice to have a fully open stack as an alternative.
Definitely would be doable, since PleasantPassword uses a modified KeePass client that's able to talk with their server.
EDIT: Apparently they're rebranding to KeePass Hub.
Part of the appeal of keepass is that it isn’t attached or involved with any other player in the space. If I wanted vaultwarden compatability i’d use something that already has it