5 ms·
such is the curse of privileged access.. Even if they hadn't enabled AD, a privileged admin could have stolen ssh keys, or passwords by launching nefarious sshd
by spydum 6y ago
such is the curse of privileged access.. Even if they hadn't enabled AD, a privileged admin could have stolen ssh keys, or passwords by launching nefarious sshd's or other daemons.
You could make the argument "but that would have been detected", but then so could watching for "strace" or "ptrace" invocations. At some point, you have to trust the people with privileged access, and make sure they aren't abusing it.
- lmilcin 6y agoSSH keys not so much, because you keep your private key on your local machine. With poorly implemented AD (think telnet/ssh login app asking for password), on the other hand, you get password transmitted to the other box. At some point some application performs read() to actually receive it.
- shawnz 6y agoYou could use GSSAPI auth with SSH. This is also a good argument for having a test AD domain to use in your test environment.
- rcxdude 6y agoI think the point is that using AD would mean the OP would be forced to use the same password to access the test system as the prod system. Otherwise, they would use different passwords and no matter how nefarious any admin on the test system was they wouldn't get access to the prod system through it.