mirror of
https://github.com/ovh/the-bastion.git
synced 2026-05-09 08:25:27 +02:00
[GH-ISSUE #475] Feature Request: *-sk keys supporting PIV-like policies #121
Labels
No labels
answered
bug
documentation
enhancement
enhancement
feature
feature
kept-open-for-info
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/the-bastion#121
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @codyro on GitHub (Apr 23, 2024).
Original GitHub issue: https://github.com/ovh/the-bastion/issues/475
Now that The Bastion supports
*-skkeys, it would be nice to have PIV-like policies available to limit keys to an account to PIV/SK/FIDO2, grace periods, etc. It could potentially utilizePubkeyAuthOptionsin some capacity.Please close this if it seems like a stinker of an idea :).
@speed47 commented on GitHub (May 22, 2024):
Well, that would completely make sense indeed!
Contrary to e.g. "RSA GPG keys used as SSH keys through
gpg-agent'sssh-agentcompatibility layer", where, on server side, we have no way to differentiate between such a (hardware) key and an RSA key stored in a file, the*-skseries does guarantee that, as PIV does.I'll check the feasibility, but I like the idea!