Re:How to SSH Properly
by closeparen on Wednesday April 01, 2020 @03:27PM
(#22752631)
1) Programmatically issue certificates with short lifetimes after authenticating against your IdP. This way if a user is deactivated in LDAP their access will expire on its own after a few hours.
2) Firewall off all but a few bastion hosts and ProxyCommand through those. Immediate revocation can be assured by updating the CRLs on those specific hosts.
This is definitely the premise of what I was going for with the post. I'm a firm believer in the idea that short-lived certificates which expire by default are one of the best ways to provide access to infrastructure, and enforcing that access comes from a limited list of bastions gives you an easy choke point to withdraw access as desired when you need to.
Re:How to SSH Properly
by sytringy05 on Wednesday April 01, 2020 @10:55PM
(#22755844)
Isn't there a netflix ssh CA that does this?
yes, it's called bless.
https://github.com/Netflix/bless
there's also cashier
Buy why go through the extra effort compared to just having your servers ask the IdP for the user's keys?
If your IdP goes down, how will you SSH in to fix it?
Having been on the rough end of this during a huge LDAP outage, I can confirm that LDAP is great until such time as it isn't.
Re:How to SSH Properly
by sytringy05 on Wednesday April 01, 2020 @10:57PM
(#22755854)
+1 this is no fun.
Currently we use the root "physical" console. Generally we avoid IDP outages by keeping our LDAP servers clustered and geographically diversified. Because LDAP is 99.999% of the time reads, not writes, this makes clustering pretty simple.
What is your opinion on using a secret management system?
https://learn.hashicorp.com/vault/secrets-management/sm-ssh-...
I think that you can use intermediate proxy server. So everyone logs into that proxy server and logs into other server using key from proxy server. Key is protected with passphrase and unlocked with ssh-agent by someone after reboot. If you need to revoke access, you can just revoke access in the proxy server.
We do both and it seems to work well - normal users do LDAP, and machine users generate certificates out of Vault that are extremely short lived, 10-30 minutes for CI jobs.
How is the communication between servers lookup up keys and LDAP protected? Does it run over TLS?
Re:How to SSH Properly
by chupasaurus on Thursday April 02, 2020 @04:07PM
(#22763143)
I think any modern LDAP client has TLS support, same goes for servers.
The most important thing is to look at your attack surface realistically and plan accordingly. Just blinding putting in an SSH cert authority of an unsecured-non-redundant ldap cluster is worse than no key management at all.