SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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)?
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:
Quote:
Searching for suspect PHP files...
/tmp/SBo/package-wxPython/usr/lib64/python2.6/site-packages/wx-2.8-gtk2-unicode/wx/tools/Editra/tests/syntax/php.php
/tmp/SBo/wxPython-src-2.8.11.0/wxPython/wx/tools/Editra/tests/syntax/php.php
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?
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
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):
Quote:
Searching for suspect PHP files...
/tmp/SBo/package-wxPython/usr/lib64/python2.6/site-packages/wx-2.8-gtk2-unicode/wx/tools/Editra/tests/syntax/php.php
/tmp/SBo/wxPython-src-2.8.11.0/wxPython/wx/tools/Editra/tests/syntax/php.php
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?
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.