[
Date Prev
][
Date Next
] [
Thread Prev
][
Thread Next
] [
Date Index
] [
Thread Index
]
Re: ClamAV Best Practices
To
:
debian-isp@lists.debian.org
Subject
: Re: ClamAV Best Practices
From
: "Joel Merrick" <
joel.merrick@gmail.com
>
Date
: Thu, 30 Oct 2008 10:13:34 +0000
Message-id
: <
[🔎]
543a57a80810300313n66250cb1g50a289edcd2802dd@mail.gmail.com
>
In-reply-to
: <
[🔎]
20081030074031.5ebaad9b@ws.in.tiger-computing.com
>
References
: <
[🔎]
20081030012758.GA18911@mail.braingia.org
> <
[🔎]
20081030074031.5ebaad9b@ws.in.tiger-computing.com
>
On Thu, Oct 30, 2008 at 7:40 AM, Keith Edmunds
<
kae@midnighthax.com
>
wrote:
Volatile. Clamav is exactly why volatile was conceived in the first place.
+1 for Volatile here too... happily chugging away on about 10 of our bastions
--
$ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe 's/(.)/chr(ord($1)-1)/ge'
Reply to:
debian-isp@lists.debian.org
Joel Merrick (on-list)
Joel Merrick (off-list)
Follow-Ups
:
Re: ClamAV Best Practices
From:
Steve <steves@braingia.org>
References
:
ClamAV Best Practices
From:
Steve <steves@braingia.org>
Re: ClamAV Best Practices
From:
Keith Edmunds <kae@midnighthax.com>
Prev by Date:
Re: ClamAV Best Practices
Next by Date:
Re: ClamAV Best Practices
Previous by thread:
Re: ClamAV Best Practices
Next by thread:
Re: ClamAV Best Practices
Index(es):
Date
Thread