I saw this myself last week, so downloaded the new sources and built ->
installed them myself. No problems and no warnings now.
0.101.0 is the latest stable version
robert
> On 13 Dec 2018, at 07:54, Scott Kitterman wrote:
>
> A larger issue in this case is that 0.100.0, as released is not su
Sorry, that's the version I meant, 0.101.0
Thanks for noticing,
Scott K
On Thursday, December 13, 2018 08:12:32 AM Robert Chalmers wrote:
> I saw this myself last week, so downloaded the new sources and built ->
> installed them myself. No problems and no warnings now.
>
> 0.101.0 is the latest
Hi all.
I was wondering if there is the possibility of creating a signature DB using
hashes extracted from SSDeep
(ref: https://ssdeep-project.github.io/ssdeep/index.html).
We are from time to time pestered by spam email with fake invoices as
attachments, like the ones reported here:
https://w
Kaushal Shriyan skrev den 2018-12-13 07:30:
I am running CentOS Linux release 7.6.1810 (Core) with ClamAV
installed. When i am running freshclam i am seeing a Warning message
and the details are described below:-
WARNING: Local version: 0.100.2 Recommended version: 0.101.0
DON'T PANIC! Read ht
Hi Joel,
This appears to be a oversight in a new feature. The message in question
should be printed at the debug log level instead of error.
Sorry!
Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.
On Dec 12, 2018, at 9:23 PM, Joel Pettis
mailto:joelpet...@gmail.com>> wrote:
Greet
Because of the libclamav header issue I disclosed last week, most package
managers are holding off on packaging 0.101.0. Some projects that rely on
ClamAV will be unable to build with the new libclamav version until ClamAV
0.101.1 is published (and until they update to use the API changes).
We
If you're looking at the CLD it will be bigger, because the CLD is not
compressed and the CVD is compressed. When you use diffs, it will store the
database in CLD format.
Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.
On Dec 12, 2018, at 11:23 PM, Dennis Peterson
mailto:denni...@
Yeah, I tried to build the latest (i.e. rather old) HAVP against
0.101.0 and it failed due to missing cltypes.h. I haven't had time to
look into this -- rather expected -- problem.
On Thu, 13 Dec 2018 02:54:08 -0500
Scott Kitterman wrote:
> A larger issue in this case is that 0.100.0, as releas
That's the exact issue Cisco warned about. Hopefully we see a 0.101.1 soon.
Scott K
On December 13, 2018 3:56:55 PM UTC, Paul Kosinski
wrote:
>Yeah, I tried to build the latest (i.e. rather old) HAVP against
>0.101.0 and it failed due to missing cltypes.h. I haven't had time to
>look into this
Would it be possible to turn off the outdated warning until that happens?
Scott K
On December 13, 2018 3:02:59 PM UTC, "Micah Snyder (micasnyd)"
wrote:
>Because of the libclamav header issue I disclosed last week, most
>package managers are holding off on packaging 0.101.0. Some projects
>that
It, unfortunately, is not. If we did, then users who have installed from
source will see the outdated warning. The warning is a dumb string-compare,
and doesn't actually compare the integer values in the version string.
Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.
On Dec 13, 20
Scott Kitterman skrev den 2018-12-13 18:28:
Would it be possible to turn off the outdated warning until that
happens?
why ?
___
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
Hel
ClamAV cannot control when the package distros update their packages. Also,
some of the package maintainers, I suspect, rely on updates like that to tell
them when they need to go update packages.
> On Dec 13, 2018, at 12:28 PM, Scott Kitterman wrote:
>
> Would it be possible to turn off the
As memory serves, there used to be a code number that represented the necessity
to upgrade. Many years ago they used to wait several days/weeks before turning
that up on routine updates, which then caused the warnings to show up.
-Al-
On Thu, Dec 13, 2018 at 09:35 AM, Micah Snyder (micasnyd) w
Good Morning!
I have set up a PrivateMirror on an internal repository server. However, this
server is not single-use. I have several YUM/RPM repositories, a copy of the
CPAN repository, etc. So, in a perfect world, I could set
PrivateMirror repository.int/clamav
so `freshclam` knows which dire
If they are relying on it, it'd be a service to turn it off until 0.101.1 is
released.
Scott K
On Thursday, December 13, 2018 06:49:08 PM Joel Esler wrote:
> ClamAV cannot control when the package distros update their packages. Also,
> some of the package maintainers, I suspect, rely on updates
thank you for your reply Micah. No worries! Now that i know I can just
ignore it, it's no big deal.
thanks,
Joel
On Thu, Dec 13, 2018 at 9:52 AM Micah Snyder (micasnyd)
wrote:
> Hi Joel,
>
> This appears to be a oversight in a new feature. The message in question
> should be printed at the d
17 matches
Mail list logo
