[GH-ISSUE #12] Cannot use certificates where private key is on a hardware token #1

Open
opened 2026-02-26 17:38:01 +03:00 by kerem · 0 comments
Owner

Originally created by @Crosse on GitHub (Oct 28, 2022).
Original GitHub issue: https://github.com/Crosse/resync/issues/12

Originally assigned to: @Crosse on GitHub.

Adding a certificate to your SSH agent requires that the private key be available on-disk. For hardware tokens, where the private key resides only in the token, certificates cannot be added to ssh-agent. (There's an enhancement request for this.) Currently, there is no way to tell resync to use a specific public key, which is how you typically get around this issue.

Originally created by @Crosse on GitHub (Oct 28, 2022). Original GitHub issue: https://github.com/Crosse/resync/issues/12 Originally assigned to: @Crosse on GitHub. Adding a certificate to your SSH agent requires that the private key be available on-disk. For hardware tokens, where the private key resides only in the token, certificates cannot be added to ssh-agent. (There's [an enhancement request](https://bugzilla.mindrot.org/show_bug.cgi?id=2472) for this.) Currently, there is no way to tell `resync` to use a specific public key, which is how you typically get around this issue.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/resync#1
No description provided.