Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The rule of thumb seems to be don't let 'root' login under ssh. ssh login via a normal account and then 'su' to 'root'. Ok great ... but ...
Basically, it looks like a remote SSH connection always maintains the same SSH_TTY parm. So if I log in as 'another' and then 'su' to 'root', 'another' will remian the owner of the device SSH_TTY. Isn't this a security risk???
Any other login (or hacker) of 'another' logged in can now access the SSH_TTY of root and send some nasty control characters.
ok, but assuming someone (a hacker) has gotten the password of the 'another' account. The ssh encryption will not stop this hacker from being able to access the SSH_TTY device, since this user is perfectly able to access their own files.
Then, if by chance the legitimate user 'another' decides to 'su' to 'root' ... the hacker could easily send commands to 'root''s screen:
cat "hello" >> /dev/ttypa2
However, I guess "hello" would not be the hacker's first step!
ok, but assuming someone (a hacker) has gotten the password of the 'another' account. The ssh encryption will not stop this hacker from being able to access the SSH_TTY device, since this user is perfectly able to access their own files.
Hmm. How can you contribute the effects of abusing a compromised account to what is "regular" OpenSSH behaviour?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.