From 8abf9e42367695a879492f066218a1bb9357866f Mon Sep 17 00:00:00 2001 From: Pierre Penninckx Date: Sun, 19 Nov 2023 09:00:37 -0800 Subject: [PATCH] Update README.md --- examples/homeassistant/README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/examples/homeassistant/README.md b/examples/homeassistant/README.md index dddfc2c..e2dda9f 100644 --- a/examples/homeassistant/README.md +++ b/examples/homeassistant/README.md @@ -34,7 +34,7 @@ in the `/run/secrets` folder on the VM. We thus need one private key for you to [`secrets.yaml`](./secrets.yaml) file and one in the VM for it to decrypt the secrets. Your private key is already pre-generated in this repo, it's the [`sshkey`](./sshkey) file. But when -creating the VM in the step above, a new private key and its accompanying public key was +creating the VM in the step above, a new private key and its accompanying public key were automatically generated under `/etc/ssh/ssh_host_ed25519_key` in the VM. We just need to get the public key. @@ -52,6 +52,8 @@ skipped key: got ssh-rsa key type, but only ed25519 keys are supported age1l9dyy02qhlfcn5u9s4y2vhsvjtxj2c9avrpat6nvjd6rjar3tflq66jtz0 ``` +Now, make the `secrets.yaml` file decryptable in the VM. + ```bash SOPS_AGE_KEY_FILE=keys.txt nix run --impure nixpkgs#sops -- \ --config sops.yaml -r -i \