Clamd is for on-demand scanning and purpose built for email scanning. It runs as
an unprivileged user which makes it awkward for scanning arbitrary files.
Clamscan is for user initiated or scheduled scanning of arbitrary files, and can
be run as any system user. Clamscan is undesirable as an on-
Unfortunately there are certain standards that information systems have to
adhere to regardless of the logic under specific deployments (I.E. FIPS,
FISMA).
Considering there are other technical controls that would impact operations
much more significantly than running antivirus on a Linux system,
On Wednesday 10 February 2016 10:22:44 Kris Deugau wrote:
> Gene Heskett wrote:
> > But, I do wish that clamd would send me a substitute email advising
> > that it has stashed a suspect incoming email into the
> > mailfile /var/spool/mail/virii. I try to look that file over for
> > FP's, but quic
Gene Heskett wrote:
> But, I do wish that clamd would send me a substitute email advising that
> it has stashed a suspect incoming email into the
> mailfile /var/spool/mail/virii. I try to look that file over for FP's,
> but quickly get lost in the visual garbage because its probably a zip'd
>
On Wednesday 10 February 2016 05:29:19 Brad Scalio wrote:
> I've seen a lot of fodder on clamd vs clamscan, running 0.99 on
> RHEL6.7 exit/entry points ... While it's easy enough to use clamscan
> via cron, is there any good stepwise SOP on getting clamd to work
> permission wise to scan all files
On 10.02.16 05:29, Brad Scalio wrote:
I've seen a lot of fodder on clamd vs clamscan, running 0.99 on RHEL6.7
exit/entry points ... While it's easy enough to use clamscan via cron, is
there any good stepwise SOP on getting clamd to work permission wise to
scan all filesystem?
For the case of an
I've seen a lot of fodder on clamd vs clamscan, running 0.99 on RHEL6.7
exit/entry points ... While it's easy enough to use clamscan via cron, is
there any good stepwise SOP on getting clamd to work permission wise to
scan all filesystem? I like the ability to have it all controlled via the
daemon
