Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
Hey folks. One of our new clients has a redhat 6.1 server, and I'd assume that there are probably a number of services that are insecure on it. Does anyone have any suggestions in particular in terms of upgrading this machine and locking it down? I'm used to using current distros and simply upgrading the packages as the security holes are announced. I'm not sure what approach to take on an older machine that probably needs a number of things fixed.
If you didn't discover any legacy stuff that would break under upgrade, definately go for an upgrade I'd say. The major reason I can offer is the newer RH's upgrade facilities (dunno if that would really count like for lowering TCO tho), newer kernel for better performance, plus RH6.1 having the largest stock of xploits readily available :-]
Map out what the box *should* be serving, *who* it should be serving to, this and the usual CERT/SANS hardening docs should give you an overview what has to be there and what has to go.
Thanks, I'll look at all those docs. I ran chkrootkit and it didn't turn up anything. I did check the list of dependencies for upgrading to the rh 7.3 kernel, and down the chain I would have to upgrade glibc which would break a number of packages. Pretty much I would have to upgrade everything... I'd be too worried that something would end up broken in the end. I can't really risk downtime with this server as it hosts their email and web. I think I'll probably just put the latest 2.2.x kernel on there, and upgrade sendmail and popd (I've already put the latest apache, sshd, and proftpd on there). Then a good ipchains rulset will hopefully hide all of the other security holes.
Does this seem like a good alternative, or is there something I'm missing?