Repository navigation
Accept the key types existing communities already use #505
MarkAtwood
started this conversation in
Ideas
Replies: 0 comments
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.
Existing communities use existing keys in existing keystores, and can't or won't rekey when onboarding, so OpenVTC needs to accept at least the following key types.
SSH (git
gpg.format=ssh,ssh-keygen -Y):ssh-ed25519sk-ssh-ed25519@openssh.com(FIDO hardware keys such as YubiKeys)ecdsa-sha2-nistp256sk-ecdsa-sha2-nistp256@openssh.com(FIDO; the onlysk-type many older tokens support)ssh-rsa, 2048 bits and up, withrsa-sha2-256/rsa-sha2-512signaturesOpenPGP (existing keyrings and OpenPGP smartcards):
Why these:
Where it fails today: verify-trust accepts only
KeyData::Ed25519and reports everything else asmalformed(verifiable-git-infrastructure/crates/verify-trust/src/lib.rs:945). DID key extraction and the SSHSIG helpers invgi-coreare Ed25519-only too.ssh-key0.6 already parses the other SSH types asSkEd25519,Ecdsa,SkEcdsaSha2NistP256andRsa. Tracked in OpenVTC/verifiable-git-infrastructure#169.Questions:
did:key, are the multicodecsp256-pub(0x1200) andrsa-pub(0x1205) acceptable for the non-Ed25519 types?All reactions