Ask HN: Avoid Manipulation of .ssh/Authorized_keys
Recently I asked the question how you handle ssh keys of your teams: https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=24157180<p>I received many good ideas of how to do this, in particular to use signed certificates instead of public-private keys.<p>One big question remains for me: how do you avoid that users who get access via a certificate to a server, simply add a public key to .ssh&#x2F;authorized_keys and then can access the server also without a certificate from then on?<p>If a user has root access via the certificate on a server, they could always manipulate that, right?