OK, I'm pretty certain that field 5 of the DNS response is a flag indicating
that a warning should be issued if the engine is out-of-date. It's currently
set to "1". What happens if you change that value to indicate that the warning
should not be issued?
-Al-
On Fri, Dec 14, 2018 at 03:52 AM,
It’s not a service we can turn off. This is a string match.
Sent from my iPhone
> On Dec 13, 2018, at 19:17, Scott Kitterman wrote:
>
> 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
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
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)
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
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
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,
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
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
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
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
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
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
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
A larger issue in this case is that 0.100.0, as released is not suitable for
distribution use to to shared library header issues (mentioned on this list a
few days ago - I appreciate Cisco being forthcoming and warning people). I
don't know what EPEL/CentOS will do, but 0.100.0 won't be in
Issue is in CentOS repo (not sure if standard or EPEL additional repo)
that, still, do not ship the latest stable.
On this topic, AMZ Linux is still have 0.99 in standard repo
Luca
Il 13/12/2018 07:42, Al Varnell ha scritto:
Not sure what comment you are looking for. The warning is pretty
16 matches
Mail list logo
