I've used this utility to scan for rootkits. I prefer rkhunter.

http://www.slackbuilds.org/repositor...em/chkrootkit/

Rootkit Hunter is a bit outdated (February 20th 2018).
Chkrootkit is updated once or twice a year.

Utilities like clamav and chrootkit are good for scanning for existing problems, but they're also more about being reactive than proactive. As already referred to, implement a firewall service, and you might also want to use lynis, a security auditing utility that you can use to help lock down your Slackware install:
https://slackbuilds.org/repository/1.../?search=lynis

2 members found this post helpful.

@bamunds check here
I have been fighting for about a month with the people from Sophos support to make them understand that not all distributions use systemd and to add support for SysV for the new Sophos Protection for Linux.
When I thought they understood, now the Product Project Manager (PM) wants an evaluation of the number of requests for this feature request. Maybe you can add your request to the respective thread if you still use Sophos and maybe there are other Sophos users on this forum who will do this.
If Sophos fails as a scanning solution for Amavis and Squid, there are no other options. From my research, almost all manufacturers of commercial antivirus products only support systemd and .deb or .rpm packages. Does anyone know another solution besides Clamav, which still has many problems to solve in order to become a useful product?

4 members found this post helpful.

I've added a comment also. Thanks for the heads up. I just don't think our comments will go very far without a corporate sponsor saying they have x000 desktops that don't use SystemD. Cheers, BrianA_MN

2 members found this post helpful.

Thanks, I saw that!
I think the same, but it doesn't hurt to try.
I proposed the integration of Sophos Protection for Linux in Amavis (Merge request), maybe I can draw the attention of the PM to think a little about the open source community.

Merge request was corrected and approved.

1 members found this post helpful.

I see Joerg Zopes just updated his Qt5 interface for ClamAV.

https://www.linux-apps.com/p/1127892/

a previous version works fine for me as single user on an old system, but might also be of use for a system administrator?

In the end, the software companies really cares about market and sales. As much of admirable is "doing the things in the old way" seems that today there's not a real market with those who loves this.

That's the real issue there: seems not worth for them to support anything else than systemd based Linux distributions. No market there for something else.

BUT, there is still a hope for you, if you can't live without antiviruses:

https://github.com/Dlackware/systemd

Yes, fortunately for you, there's a systemd build for Slackware, brought to us by the non-typical guys of Dlackware.

I know, I know, it's a bit older set of slackbuilds, BUT certainly the system administrators like you will be capable to update them.

Eventually with publishing your changes, you know...

PS. For the Jihadi Johns lurking around: I for one, I do NOT advocate the adoption of systemd in Slackware, BUT as well we have "alternatives" like S6 or UnitD and other craps like this, why not to have systemd as alternative, for the Special Purpose Systems usually known as servers?

1 members found this post helpful.

Market is no god nor unbearable force even if some find it evil. You can resist to the market.

Might be the good way. Might not.

I talked from the POV of businesses and for them The Market is their Holly Grail, if not even one of their Gods.

Because the businesses aren't charities and they never was - their sole purpose is to sell goods and make moneys.

@LuckyCyborg you are right, the PM from Sophos Protection for Linux categorized (when he had no other arguments) my case as a niche situation and conditioned the re-adding of support for SysV depending on the number of requests to add this feature.
The previous versions of Sophos Antivirus for Linux only had support for SysV, but after the acquisition of Sophos by Thoma Bravo, the americans quickly EOLed the free version, as well Sophos Anti-Virus Dynamic Interface - SAVDI, the basic piece in antivirus scanning for mail (through Amavis) and trafic scanning in proxy (for Squid).
I can live without antiviruses but at my main job, many years ago I boasted that I could provide a perfectly functional mail service, installed and configured by myself and now I am left with no options because Clamav is still far from having a functional product, Cisco with the current team cannot even update the existing components and by no means add new improvements.
At my age, the servers still give me a reason to keep active and afloat.
Some time ago I didn't want the adoption of systemd either (neither PAM or GRUB) but look we have PAM in Slackware, we will soon have GRUB and if we don't insist on going against the current we will have systemd in case the german Lennart Poettering don't give up now if he left Red Hat for Micro$oft.
That would really be a good idea to have systemd as an alternative, I studied a bit the Sophos files for systemd (to see how I could adapt them for init.d) and it's not such a great philosophy, the biggest problem is how to trick the installation script into not stopping the installation because it doesn't find systemctl.

Would we need the fauxd - the fake systemd that tricks software into running.

Now imagine a down the road zeroday leaning heavy on everything running systemd on one of these fauxd boxes

As expected (well guessed by @bamunds) Sophos doesn't bother to add support for System V (SysV) init system because they say there is a small user base that still uses it.

https://community.sophos.com/sophos-...ithout-systemd

Funny British company, calling someone a minority.
Wonder what happens if someone lands in UK and persists with driving on the 'right' side, because you know, the left side is where minorities drive at.
Why can't you use a non discriminating AV like Clam? Or just move the Sophos scanner into a virtual machine, bypassing the host PID1 requirement completely?