SlackwareThis Forum is for the discussion of Slackware Linux.
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.
First of all any action (and that includes wiping disks and re-installing the OS or any SW) without determining the cause first is inefficient and may well expose loopholes (if any) again. (That doesn't mean you shouldn't move to mitigate if a breach of security is suspected!)
I am glad that I recommended that the OP make sure that he is rooted before doing a wipe. Determining the root cause of an anomaly makes sense to prevent the event from reoccurring(thanks for that!). For a lot of us who are not professional system administrators (like me) determining the root cause of an anomaly will be a daunting task. I do try to prevent mishaps by patching my systems and having software and hardware firewalls in place.
As the maintainer of rkhunter and a security professional do you have any further(beyond what you mentioned) tips on how to harden a system?
Thanks in advance for any and all suggestions, links, and advice unSpawn. I am genuinely curious.
Sorry unSpawn. Marking this thread as solved. I would very much welcome your perspective in the Slackware hardening thread I recently started. If that interferes with your moderating duties I understand.
Happy New year.