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.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
'man iptables' , i've got mine set up to accept all connection's starting from a local point, reject everything else, and then log attemept's from remote location's. Then it's right's these attempt's to 'syslog', this way i can check everything at once!
Distribution: Slackware, VectorLinux, Smoothwall, and PCLinuxOS
If you are using your Linuxbox as a firewall/gateway it would be wise to use an antivirus (if more than one computer is behind it). For all of the small networks I configure, I purchase Kaspersky Antivirus for Linux.
Kaspersky is what I use for all of my Windows based operating systems and I use it on my Linux gateway at home. It is a bit pricey...but I don't have an antivirus BOGGING my system down...which is nice especially for gaming.
As far as a great and simple firewall script...I use endoshield. It's the easiest script I've ever run across and it configures things with simple questions. And here's the best part...when you change a setting...say, enabling an ftp server...you simply execute the startup script again...answer the questions...and BeWm...you're set. Find endoshield here
There ARE viruses for linux, do not let anyone tell you different. There are TONS of them. However, they work a bit different for linux than windows.
Favorites of the script kiddies are virus programs that will create root accounts on your machine, will change the way system commands work, will delete files... blah blah blah.
You should get a rootkit checker.
I know that Mandrake's security programs checked the filesystem for alteration, rootkits, changed permissions and so on. I dont think Slack has a homegrown security checker though.
I remember the first virus for Linux...Bliss, back in 1996-1997. The bottom line is that most viruses cannot survive in the hostile Linux environment. There are many...but none that are a serious threat. Tell you what...check out this link...it's a very good read and will help explain alot about Linux and viruses.