Resident SSH key comments #732
-
I'm not sure this is an openssh level issue or a libfido2/Yubikey layer issue. I've tested this on MacOS Sonoma and the compiled provider as referenced here #464. Additionally I have tried this on older MacOS variants using a brew installed version of openssl. The behavior is consistent in all cases. I've not tested on a Linux system but I'd suspect the same. I'm trying to utilize the standard ssh-keygen -C comment to help identify my resident keys over time. I issue the following command to create my key:
This creates my resident key in a fido slot called ssh:commenttest. Additionally it creates the I intend to either load the key via When loading into the agent via
When extracting via
I can at least get by with naming my slots in a way that is descriptive but it requires me still to extract the resident key/.pub to even see this and does not help at all in the agent side of things. Again, I'm not exactly sure which layers may or may not be dealing with the comments in the ssh keys. I'm not entirely sure the comment is even in the private key stored on the Yubikey. I would hope for at least the slot name to be visible in the agent and exported .pub keys. Or possibly merge the slot name and the comment in some consistent way. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
While perhaps more of a question for OpenSSH -- no, the comment is not stored on the authenticator. As an aside, storing arbitrary extra data along with a credential on an authenticator requires a CTAP 2.1 extension ( |
Beta Was this translation helpful? Give feedback.
While perhaps more of a question for OpenSSH -- no, the comment is not stored on the authenticator.
As an aside, storing arbitrary extra data along with a credential on an authenticator requires a CTAP 2.1 extension (
credBlob
) or optional feature (largeBlobs
).