Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update docs of age about ssh support #9

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

update docs of age about ssh support #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion content/en/docs/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down