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.
I just wanted to know when dealing with key loggers, What would be a normal routine for searching them out. I really don't know what I am looking for other than odd process. Also packet sniffers. What are signs?
I don't think there would be any signs. As you said, odd process might be the only clue.
I would assume that in rder to log keystrokes or log network traffic the process would have to be running as root.
The easiest way would be to obtain the list of running processes and then "googling" for the ones that look suspicious.
Yea I was going to sit down and google the majority of the processes. Since this is a university server though, I haven't a idea of half the stuff running so it would be alot to go through. The only thing I could come up with was some sort of shell wrapper that would log every thing.. I'm just scared for the obvious reasons, safety of my passwords and the usual talking bad about my boss. heh thanks for your reply
Let me point out a few things:
To log your keystrokes on unix, there are two possible paths to do it:
1) detectable
call a wrapper from your .profile or global .profile (or .bashrc etc.), or set your shell in /etc/passwd to a wrapper. You can see them running and you can discover them by looking into the above files
2) undetectable
use modified programs, like getty or shell. In that case you'll see what looks like legit process and you can't tell the difference unless you are the system administrator.
#2 usually means that the system has beed compromised. I don't think sysadmin would do that unless it was a company policy or something like that.
#1 is not very useful unless the user does not have a clue at all, otherwise it's pretty easy to figure it out.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.