Improve path_to_fido2_key #83

Closed
opened 2025-10-13 11:33:18 +02:00 by mfocko · 1 comment
Owner

Currently path_to_fido2_key script deduces at least one connected Yubikey, but my git setup supports multiple sources of keys:

  • implicit SSH agent (for macOS default from nixpkg, for Linux-based keyrings) that handles Yubikeys as well
  • Bitwarden SSH agent
  • 1password SSH agent
  • GPG SSH agent

Notes

It may not be possible to support 1password's for git signing, as it has additional setup within gitconfig.

GPG SSH agent should be fine, as it enrolls the key in the SSH agent.

Probably the best approach is taking whatever's enrolled in the current SSH agent.

Currently `path_to_fido2_key` script deduces at least one connected Yubikey, but my git setup supports multiple sources of keys: - implicit SSH agent (for macOS default from nixpkg, for Linux-based keyrings) that handles Yubikeys as well - Bitwarden SSH agent - 1password SSH agent - GPG SSH agent ## Notes It may not be possible to support 1password's for git signing, as it has additional setup within gitconfig. GPG SSH agent should be fine, as it enrolls the key in the SSH agent. Probably the best approach is taking whatever's enrolled in the current SSH agent.
Author
Owner

Probably the best approach is taking whatever's enrolled in the current SSH agent.

I call bullshit, doesn't mean that key can be used for signing 🤦

> Probably the best approach is taking whatever's enrolled in the current SSH agent. I call bullshit, doesn't mean that key can be used for signing 🤦
Sign in to join this conversation.
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
mfocko/dotfiles#83
No description provided.