Show HN: SSH Permit A38 – Central Managment and Deployment for SSH Keys
1–10 of 28 posts
Re: Show HN: SSH Permit A38 – Central Managment and Deployment for SSH Keys
#2Re: Show HN: SSH Permit A38 – Central Managment and Deployment for SSH Keys
#3Re: Show HN: SSH Permit A38 – Central Managment and Deployment for SSH Keys
#4An alternative (but also imperfect) solution that I've relied on in the past is using certificate-based authentication:
https://www.digitalocean.com/community/tutorials/how-to-crea...
This still requires the generation of certificates for users but it doesn't require updating the key material on the servers themselves. Having short-lived user certificates then gives the admin an easy way to revoke access to a server without changing any keys there by simply not issuing a new certificate to the user (and in urgent cases to also revoke the certificate as well before it expires, which requires intervention on the server though).
I really hope that OpenSSH keeps improving their (still largely incomplete) PKI implementation, as I think it's a great feature for larger organizations.
Re: Show HN: SSH Permit A38 – Central Managment and Deployment for SSH Keys
#5Very interesting project, I've been confronted with this kind of problem (managing SSH access for a large number of users) several times and don't think there's a perfect solution for it yet. An alternative (but also imperfect) solution that I've relied on in the past is using certificate-based authentication: https://www.digitalocean.com/community/tutorials/how-to-crea... This still requires the generation of certif…
Along with something like Packer to bake the cert right into the image.
Re: Show HN: SSH Permit A38 – Central Managment and Deployment for SSH Keys
#6Re: Show HN: SSH Permit A38 – Central Managment and Deployment for SSH Keys
#7With Ansible, one can put the SSH keys into a .yml file in a format that is very similar to the examples in the OP, then the authorized_key module can be used to ensure that the key is present (or absent) on the remote servers. It's really-really trivial. Maybe the difference is that you can paste the SSH key into the CLI instead of a file... hm.
Re: Show HN: SSH Permit A38 – Central Managment and Deployment for SSH Keys
#8Very interesting project, I've been confronted with this kind of problem (managing SSH access for a large number of users) several times and don't think there's a perfect solution for it yet. An alternative (but also imperfect) solution that I've relied on in the past is using certificate-based authentication: https://www.digitalocean.com/community/tutorials/how-to-crea... This still requires the generation of certif…
Re: Show HN: SSH Permit A38 – Central Managment and Deployment for SSH Keys
#9Genuine question: what functionality does this provide that e.g. Ansible doesn't? With Ansible, one can put the SSH keys into a .yml file in a format that is very similar to the examples in the OP, then the authorized_key module can be used to ensure that the key is present (or absent) on the remote servers. It's really-really trivial. Maybe the difference is that you can paste the SSH key into the CLI instead of a f…
Re: Show HN: SSH Permit A38 – Central Managment and Deployment for SSH Keys
#10Very interesting project, I've been confronted with this kind of problem (managing SSH access for a large number of users) several times and don't think there's a perfect solution for it yet. An alternative (but also imperfect) solution that I've relied on in the past is using certificate-based authentication: https://www.digitalocean.com/community/tutorials/how-to-crea... This still requires the generation of certif…
If you're managing large amount of servers and don't want to update configs on the servers themselves then use e.g. OpenLDAP.
Now of course this is both a trust and a escalated privilege issue. But a lot harder(impossible) with keys.