Results 1 to 1 of 1
Thread: Centralized authorized_keys file
Enjoy an ad free experience by logging in. Not a member yet? Register.
- Join Date
- Apr 2008
Centralized authorized_keys file
user1 can ssh firstname.lastname@example.org and not be challenged for a password.
user2 can ssh email@example.com and not be challenged for a password. Unfortunately user2 can also ssh as user1 to server foo.com and not be challenged for a password AND is logged in as user1. Thus user2 could login and do bad things and it looks like user1 did it.
Is there any way to have one authorized_keys file that users authenticate with but only allows users to login as themselves?