Skip to content

Conversation

jon4hz
Copy link
Contributor

@jon4hz jon4hz commented Sep 19, 2025

Hi again,

This PR introduces an option to ensure users can only add ingress keys which have been signed by a predefined, trusted CA.

If an admin configures the new pivValidationCA to point to a CA certificate, the user will be prompted to upload his certificate, instead of the ssh public key. The Bastion then validates the certificated against the configured CA.

The yubico-piv-checker will generate the ssh pubkey based on the provided certificate and returns it in the JSON output. There's also a new prompt to ask for "from" IPs, since that information can't be passed with the certificate that easily.

A PR with the required changes for the yubico-piv-checker is here: ovh/yubico-piv-checker#9

Currently everything is implemented in a none breaking way. Please let me know if you want any changes or have any suggestions.

@jon4hz jon4hz force-pushed the feat-piv-ca-validation branch 3 times, most recently from 69b9068 to 2a88d84 Compare September 20, 2025 09:26
Signed-off-by: Jonah Zürcher <jonah.zuercher@adfinis.com>
@jon4hz jon4hz force-pushed the feat-piv-ca-validation branch from 2a88d84 to b1e4b25 Compare September 22, 2025 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant