Skip to content

understanding keys.txt  #297

@techhazard

Description

@techhazard

When looking at the part of the tutorial to convert an existing ~/.ssh/id_ed25519 private key into an age key, this requires removing the password from a temporary copy and using that to create ~/.config/sops/age/keys.txt. This makes me have a few questions:

In keys.txt a plaintext private key?

Does this mean that the private key used for the sops encryption decryption is stored in plaintext?
I don't think this is explicitly stated as such in the guide, it might be a good idea to make that clear.

Is it possible to derive my original ssh private key from this file?

How is de age key derived from id_ed25519?

Why are encrypted keys not supported?

Age itself seems to support it: https://github.com/FiloSottile/age#passphrase-protected-key-files
It looks like an upstream limit? https://github.com/mozilla/sops#encrypting-using-age
But support seems to be coming: getsops/sops#1134

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions