New release w/ age ssh key support?

[cdanis]

Hi,

Any idea of the timeline for a new release that includes the support for using ssh keys via age?

[felixfontein]

There's no concrete timeline yet, but my guess is that there will be a new feature release somewhen this month.

[squeige]

Does this mean the documentation is behind? I been trying to setup sops with age but keep getitng failed to parse input as Bech32-encoded age public key: malformed recipient "ssh-ed25519....

"
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 falls back 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."

[cdanis]

The README is ahead, actually. You need to build from source if you want to use the new feature, until a release is created.

[pomdtr]

Can't wait for this to release. The ssh key feature will be really useful in my project.

[felixfontein]

3.10.0 is out with this feature! 🎉

[izissise]

Documentation still says its unsupported https://getsops.io/docs/#encrypting-using-age

Encrypting with SSH keys via age is not yet supported by SOPS

[felixfontein]

The official documentation is here: https://github.com/getsops/sops/blob/main/README.rst