I don’t know if that’s really the case, given https://docs.google.com/document/d/11yHom20CrsuX8KQJXBBw04s80Unjv8zCg_A7sPAX_9Y https://docs.google.com/document/d

I don’t know if that’s really the case, given https://docs.google.com/document/d/11yHom20CrsuX8KQJXBBw04s80Unjv8zCg_A7sPAX_9Y https://docs.google.com/document/d/11yHom20CrsuX8KQJXBBw04s8... > Goals > * The option to encrypt to SSH keys, with built-in GitHub .keys support And lower on the page, it shows the use of built-in command-line syntax for “github:$recipientname”. It definitely works for keys that aren’t used for SSH, but support for SSH keys seems to be a large part of the rational for the ed25519 support (otherwise it would just be a tool that operated on X25519 keys directly).