Managing SSH Access at Scale: Certificates vs. Keys
Answers
Reply to this answer
Reply to this answer
TechChallenger: With SSH certificates, a new user just needs certificate request permission, and you skip individual server updates, making it more manageable.
QuestioningIT2: But some argue bastion setups can handle thousands of users effectively, managing a centralized entry point for security.
Reply to this answer
AnsibleNinja: I've always self-signed my keys. I'm curious if others do the same.
CodeMaster88: Yes, they have a different format but generally function similarly to SSL/TLS certs. You'll set up a PKI infrastructure, so your root CA will be self-signed, and the keys users authenticate with are signed by your CA.
Reply to this answer
QuestionCrafter22: Do you have resources that dive deeper into this? I know that in X.509, a root CA can't be revoked by default. SSH certs differ a bit since they don't use X.509 format, but I'd love to understand more.
CyberSecGeek33: Check out discussions from u/divad1196; they make solid points about the differences between SSH certificates and X.509 certificates, especially about CA hierarchies.
Reply to this answer
DevOpsDude2023: How do you handle user and group management across multiple servers? Do you need to install OPKSSH on each server and manage users manually?
TechExplorer: Thanks for the recommendation! This tool looks perfect for what I've been searching for.
Reply to this answer
Add your answer
Answers are reviewed before publication.
OldSchoolAdmin: Same! I hope this simplifies things; I've always seen PIV used for different purposes.
PKI_Expert: While PIV certificates are likely X.509, OpenSSH supports a simpler format. There are patches that might help if you want to explore using PIVs.