On Tue, 12 Sep 2023, Joel Esler via clamav-users wrote:
Curl won’t work at all.
But it definitely points to a dns problem.
— Sent from my iPhone
On Sep 11, 2023, at 13:07, Serge Slivitzky via
clamav-users wrote:
Hi all,
I'm using clamav on 2 systems built the same way:
Curl won’t work at all. But it definitely points to a dns problem. — Sent from my iPhoneOn Sep 11, 2023, at 13:07, Serge Slivitzky via clamav-users wrote: Hi all,I'm using clamav on 2 systems built the same way: the first one is behind a firewall and freshclam is not working, the other one is u
* Al Varnell via clamav-users :
> Sent from my iPad
>
> On Sep 12, 2023, at 01:29, Ralf Hildebrandt via clamav-users
> wrote:
> > should sigtool --decode-sigs really throw an error in that case?
>
> Perhaps not, but it's been the case for as long as I've been using
> clamav...decades now.
Yea
Sent from my iPad
On Sep 12, 2023, at 01:29, Ralf Hildebrandt via clamav-users
wrote:
> should sigtool --decode-sigs really throw an error in that case?
Perhaps not, but it's been the case for as long as I've been using
clamav...decades now.
Just my approach, but I always start with -f (or --
I found a rejection based on vhxtdQ.sigs.InterServer.net.SHA256.21881
in my mail.log and wanted to check what the signature searches for.
So I took out ye olde sigtool - and failed:
# /usr/local/bin/sigtool --find-sigs vhxtdQ.sigs.InterServer.net.SHA256.21881 |
/usr/local/bin/sigtool --decode-si
