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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i'm looking for way to secure my /tmp directory
i have fedora core 2 work as web server with apache
sometimes crackers puts binary files in my /tmp directory
also i find some processes runs as http and when i restart the serveice i found that these prcesses are still working.
i want to find something to monitor my /tmp directory and to take action.
Create a partition large enough to hold /tmp, then edit /etc/fstab to show the new partition. Mount it noexec to prevent executable files from running in /tmp.
The problem is not with /tmp. You need to investigate what web content on your servers are allowing people to upload to your system. Secure your applications. Creating a larger /tmp without fixing the hole is only giving people more storage space on your system.
sometimes i find that the load average is high then when i make #top -c to show what are the most processes that consumes more cpu cycles and memory,i find normal processes nobody with http and when i restart the httpd service i found that everything is cool and the load average reduced.
and sometimes when i stop the service httpd i find running http service and i don't know what is it?
i think that it is some of processes that crackers wants to execute from /tmp.
Like Stickman says, harden the box. If I understand correctly what you write then in your case you have to check your system, auth and daemon logs because it sounds like your box is/was a target. Did you run any auditing apps like Tiger, Chkrootkit / Rootkit Hunter?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
