I've been using clamav for a long time. Works great, runs just fine and is supported on Solaris 11.3 (x86_64) (from opencsw.org), Linux (packaged into distro), and FreeBSD (from FBSD ports) although I haven't tried that one in awhile. Never any charges/payments required to anyone of course. Presently owned by cisco.
Was also available for awhile for OpenVMS (DEC Alpha) but apart from a couple well-known benign worms exploiting default system account passwords in the 1980s and long since patched, there's never been a 'virus' on native VMS files mostly due to extensive designed-in security levels. The most recent OS release (9.2, in 2021) runs on Alpha hardware (as well as x86-64 now), but no virus has ever been detected on recent OpenVMS on Alpha hardware so no current (2021) projects are known to exist to port clamav onto 9.2. It would make a great network area storage (NAS) server but all files put onto it would have to be scanned first. The Solaris version however can scan for malware on its own files and guest files.
So having Solaris as a NAS server to connect client machines to via NFS allows you to launch a clamav virus scan on the Linux client and any of its NFS-mounted zfs pools on the Solaris machine. 'cron'-launching clamav on the Solaris NAS covers any files in the root pool or user pools of that machine, including attached offsite backup pools. So you can keep most user files from all sorts of attached machines on Solaris zfs pools on one NAS machine, and back up any tightly-bound client app user files to it as well. Together with SAS-based zfs raid and offsite-based 'zfs send' snapshots you get a very bulletproof data protection setup. In 10 years I've not had a single positive virus hit.
I've been thinking about firing up the Alpha server again now that OpenVMS 9.2 is out and stable, and setting up a similar configuration using FreeBSD nfs-mounted to it. The FreeBSD clients would launch clamav conceptually similarly to the Linux ones above, but no clamav would be needed on the Alpha server as it is passively immune. zfs however has more relevant admin features than anything in OpenVMS I'm aware of, so the Alpha would have to be pretty much an off-site storage box like an external hard drive instead.
So you end up with any solid multiuser GUI client front-end operating system/machine such as Suse Linux or FreeBSD set up with clamav virus-scanning, then nfs-connected to Solaris's zfs pools carrying most of the client systems' user data, which can also be virus-scanned periodically with Solaris' copy of clamav, and then zfs-snapshot backed up to the OpenVMS Alpha (or x86-64) server and an external drive as two different offsites. The client front-ends could even run a different virus scanner than Solaris so their files get scanned by two different AV softwares if you don't trust one or the other 100%.
Last edited by Arty; 12-08-2021 at 03:49 PM.
|