3 ms·
I don't see how the authentication used for a user on a local machine has anything to do with the authentication of a user on a remote machine unless both are u
by inetknght 9y ago
I don't see how the authentication used for a user on a local machine has anything to do with the authentication of a user on a remote machine unless both are using the same domain authentication (RADIUS, Active Directory, etc). Even then, there can be cache involved.
- closeparen 9y agoThere could be a local compromise that exposes the SSH keys (for login) but not the remote password (for sudo).
- inetknght 9y agoMy parent comment indicates that the password needs to be different. Your comment does not support that. First, sudo should not be cached for this very reason. Second, agent caching should never be enabled for this very reason. Third, agent forwarding should never be enabled for this very reason. Indeed, using key authentication to log in and then using a password to upgrade to sudo is, I think, very reasonable.
- merb 9y ago> Indeed, using key authentication to log in and then using a password to upgrade to sudo is, I think, very reasonable. which most often is not the default on vps/root/clouds, that's basically my point. if you use sudo, use it with a password.
- deleted 9y ago[deleted]