The way we do this is with an in-memory ‘agent’ that listens on a 127.0.0.1 port Store the master key on disk somewhere, but that’s a bad idea. This needs to be kept “safe”, but this is a CLI program. Like this:īitwarden works by having a “master key” that is computed from your email and
What I found to be a possible viable solution is to work with tokens. As said, I’m not that technical enough for this. But that must be confirmed by someone with a decent knowledge on this. Good point which I assumed would be possible to mitigate. What do you guys think? I believe this could increase the security heavily. I’m not too technical on this aspect, but there’s a powerful, full-featured command-line interface (CLI) tool to access and manage your Bitwarden vault: My Feature request is to enable Home Assistant requesting passwords from Bitwarden, like we currently can via credstash. The addon from is purely to make it easy to self-host the Bitwarden Vault. This Feature request is NOT the same like this addon: Home Assistant Community Add-on: Bitwarden RS. Both self-hosted as Bitwarden’s web vault compatible.Approve which passwords can be requested by HA and which not (could be done by adding the approved ones into an organisation for example).Get username/password/token/… from Bitwarden vault.This would also make it possible to change any password, without changing the configuration file of HA. That’s why I would be very interested in having an integration with eg Bitwarden to automatically get my password out of the Bitwarden Vault. I always found it quite strange and not very secure to just put my plaintext passwords into a configuration file.
0 kommentar(er)
