Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
Hi all
I had a call from a technician on a remote site with a Linux server (redhat ES 5.3) for which I assist with technical help.
What has happened for no apparent reason is that the entire /tmp directory was cleaned out (all files deleted) and file permissions of /tmp changed so that only root could write to it. Similar at the same time a number of sub directories in /var also disappeared.
To make things worse is that the affected machine won't let me make an ssh connection and GDM does not work either, so my only way to see what's going on is to ask the local technician to type command line commands and tell me the results over the phone. (the site is 1500 km away from me!)
What on earth could do something like that? I would consider it unlikely that the local technician could have done it, even unknowingly.
If local utilities have been replaced, or an obfuscation module added to the kernel, you MAY not be able to tell what is happening for certain even AFTER you recover access (if you even can).
Restoring ssh access is one start. If that fails, you might have him boot up and grant access using a live-cd image, then get ssh access, mount the drive, and do forensics from there. Running something like ROOTKITHUNTER may help you detect the cause of your issue IF it is malware triggered.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.