From ce202352b46dacedb29447122f39b4fb18e337ec Mon Sep 17 00:00:00 2001 From: haoqixu Date: Tue, 3 Dec 2024 13:32:40 +0800 Subject: [PATCH] update docs of age about ssh support Signed-off-by: haoqixu --- content/en/docs/_index.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/content/en/docs/_index.md b/content/en/docs/_index.md index a83c207..f7d6b35 100644 --- a/content/en/docs/_index.md +++ b/content/en/docs/_index.md @@ -232,7 +232,13 @@ one per line. Lines beginning with `#` are considered comments and ignored. Each identity will be tried in sequence until one is able to decrypt the data. -Encrypting with SSH keys via age is not yet supported by SOPS. +Encrypting with SSH keys via age is also supported by SOPS. You can use SSH public keys +("ssh-ed25519 AAAA...", "ssh-rsa AAAA...") as age recipients when encrypting a file. +When decrypting a file, SOPS will look for `~/.ssh/id_ed25519` and fallbacks to +`~/.ssh/id_rsa`. You can specify the location of the private key manually by setting +the environment variableuse **SOPS_AGE_SSH_PRIVATE_KEY_FILE**. + +Note that only `ssh-rsa` and `ssh-ed25519` are supported. ## Encrypting using GCP KMS