Protecting Slackware
 

Hello,

I know Slackware probably doesn't require too much protection from viruses or spyware, but I'm wondering if there's anything I can do to help protect it (other than Common Sense).

I ask this for 2 reasons:

1. I'm Paranoid
2. Every now and then I mistype a website I go to and it takes me to a completely different website which frightens me because of my paranoia.

So is there anything I can do to help protect Slackware, and in the rare case I get a virus is there a way to remove it directly?

Is it also possible to use Slackware (currently Master drive) to remove a virus on Windows (slave drive)?

Take a look at
http://www.slackbook.org/html/security.html
http://www.chkrootkit.org/

Kind regards

Thank you. ^^

Okay, for those who did see what this post actually was, I fixed it but I have another quick question about chkrootkit. After using it, I came out with this:

Does this mean it's infected, or was it just the file it was checking?

Also, if a file wasn't executed and therefore not testable, should I be worried?

You can use sbopkg to install it.
http://sbopkg.org/

Another good tool you can use is rkhunter to see if you've picked up any root kits.

http://slackbuilds.org/repository/13...stem/rkhunter/

Use slackpkg to keep your unit up to date with the latest slackware security patches. Also, having a firewall is a good idea.

http://connie.slackware.com/~alien/efg/

Thanks hitest.

I've actually tried this, but it didn't produce a text document as it says it does. It just took me back to the top of the page.

That's odd. I just tried Eric's page and it works just fine.

1. Select DHCP or static IP (enter IP address if static IP selected.
2. Select Single system and use IRC if you use that protocol.
3. Click on the Generate firewall button.

Then a new web page will open with the firewall script. Copy and paste that script into a blank text document. Save as rc.firewall. Then as root make that script executable.
# chmod +x rc.firewall

Put that script into /etc/rc.d

# cp rc.firewall /etc/rc.d

Start-up your firewall with:

# /etc/rc.d/rc.firewall start

Oh okay, I see. I didn't put in my IP address lol. Thank you again.

One final question: Doesn't chkrootkit also look for root kits? Which, if it does, what purpose would I have with rkhunter?

You're welcome. :)
Yes, chkrootkit also checks for rootkits. It can't hurt to have more than one security utility in my opinion (another layer of protection).

Oh, this is the last thing (primarily because it was lost in our posts):

I asked if this means it's infected or not since this was my first time using chkrootkit. Also if it says it wasn't scanned because something wasn't executable, does that also mean that program/file is infected too?

Does anybody know? ^^ It's important to the security of my computer. ^^

I imagine the fact that there is a PHP file in the /tmp directory that it looks like something malicious, the /tmp directory is a notorious directory for dropping code and other exploits as it's usually configured with lax permissions and is usually the entry point for many local attacks. I could be wrong, but knowing rootkits and how they work, I imagine that since the code is related to sbopkg and is calling tgz and other archive file types, it just looks suspicious.

I'm worried whether I should delete directly or not.

Try scanning your unit with rkhunter and see if it finds anything odd. After you've installed rkhunter it runs on the command line from /usr/bin

Update rkhunter as root by

# rkhunter --update

then scan your system by

# rkhunter --checkall