Replies: 1 comment 1 reply
|
This is actually supported (SSH certificates) – you can just put the cert in the public key folder next to the public key for the original key. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Support for signed SSH keys would enable integration with Github's CA support. Where each key can be signed and tied to a particular Github user.
Here is an example:
ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@github.com=USERNAME ./user-key.pubhttps://docs.github.com/en/enterprise-cloud@latest/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#issuing-certificates
Maybe support for this might be coupled with CLI support for secretive? To avoid having to build UI for all of it, and to support automation.
Example of CLI usage for a native app
All reactions