Hi there,
On Sat, 5 Oct 2019, Dennis Peterson wrote:
This particular hard requirement (libcurl) affects the communication channel
which is different than causing the code to fail to run at all. So the
question is do the new libcurl requirements immediately break existing
systems that are not
Hi there,
On Sat, 5 Oct 2019, Matus UHLAR - fantomas wrote:
On 05.10.19 15:57, alex mc via clamav-users wrote:
El sáb., 5 oct. 2019 a las 15:14, J.R. via clamav-users [...] escribió:
I had already seen all this, but the code itself does not know where it is
Are you talking about the virus
On 05.10.19 15:57, alex mc via clamav-users wrote:
I'm talking about the source code of the antivirus, but thanks.
your question has been answered then already:
https://lists.clamav.net/pipermail/clamav-users/2019-October/008635.html
This is super critical to the future of where ClamAV is headed. So, while I
understand it’s a pain in the butt, we need to work out, as a community, maybe
with an faq page contributed by all of us, how to get past this hurdle.
Sent from my iPhone
> On Oct 5, 2019, at 09:41, Dennis Peterson
I'm talking about the source code of the antivirus, but thanks.
El sáb., 5 oct. 2019 a las 15:14, J.R. via clamav-users (<
clamav-users@lists.clamav.net>) escribió:
> > I had already seen all this, but the code itself does not know where it
> is
>
> Are you talking about the virus definitions?
This particular hard requirement (libcurl) affects the communication channel
which is different than causing the code to fail to run at all. So the question
is do the new libcurl requirements immediately break existing systems that are
not yet updated with new libcurl functionality. It is kind
> I had already seen all this, but the code itself does not know where it is
Are you talking about the virus definitions? Those are also available
on the clamav download page. Once downloaded you can use sigtool to
extract all the raw files into something you can read.
