On Monday 09 April 2018, Joel Esler (jesler) wrote:
> ClamAV 0.100.0 has been released!
> * Deprecating internal LLVM code support. The configure script has
> changed to search the system for an installed instance of the LLVM
> development libraries, and to otherwise use the bytecode interp
Am 17.07.2018 um 09:47 schrieb Sergey:
> On Monday 09 April 2018, Joel Esler (jesler) wrote:
>
>> ClamAV 0.100.0 has been released!
>
>> * Deprecating internal LLVM code support. The configure script has
>> changed to search the system for an installed instance of the LLVM
>> development li
Unsatisfying as it may seem, the problem went away as it came, without
any obvious reason.
For the record, we do have SELinux active on those systems, so it is
(was) very likely an SELinux issue.
Thanks,
Tilman
Am 16.07.2018 um 17:07 schrieb Micah Snyder (micasnyd):
> Hi Tilman,
>
> Sorry no on
On Tuesday 17 July 2018, tschmidt wrote:
> >> ClamAV 0.100.0 has been released!
> >
> >> * Deprecating internal LLVM code support. The configure script has
> >> changed to search the system for an installed instance of the LLVM
> >> development libraries, and to otherwise use the bytecode i
On Tue, Jul 17, 2018 at 01:34 AM, Sergey wrote:
> On Tuesday 17 July 2018, tschmidt wrote:
>
ClamAV 0.100.0 has been released!
>>>
* Deprecating internal LLVM code support. The configure script has
changed to search the system for an installed instance of the LLVM
develop
On Tuesday 17 July 2018, Al Varnell wrote:
> > Yes. But LLVM < 3.7 deprecated also.
>
> No, deprecated refers to the use of LLVM greater than 3.6 by
> ClamAV 0.100.0, not LLVM itself.
Deprecated refers to use deprecated LLVM 3.6 which can be absent
in modern distro. Therefore deprecating interna
On Tue, Jul 17, 2018 at 02:03 AM, Sergey wrote:
> On Tuesday 17 July 2018, Al Varnell wrote:
>
>>> Yes. But LLVM < 3.7 deprecated also.
>>
>> No, deprecated refers to the use of LLVM greater than 3.6 by
>> ClamAV 0.100.0, not LLVM itself.
>
> Deprecated refers to use deprecated LLVM 3.6 which ca
On Tuesday 17 July 2018, Al Varnell wrote:
> It's best to use the bytecode interpreter for ClamAV
> bytecode signatures, but if for some reason you feel
> you must use LLVM-JIT
I thought it was necessary to use llvm to use bytecode
signatures. Was I wrong? Is ClamAV not lost functionality
witho
Hello
properly you have an old version installed on your machine...
so you need go shure that the old version are uninstalled. i had last week the same error.
apt-get remove clamav = This are only remove the clamav - for me wasnt enought
apt-get remove --purge clamav = this remove cla
Is zlib 1.2.4 really significantly more processor intensive than 1.2.3? It is
rather trivial to install from http://www.zlib.net/fossils/
Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.
On Jul 16, 2018, at 11:37 PM, Al Varnell
mailto:alvarn...@mac.com>> wrote:
Micah said earlier t
ClamAV has 3 options for handling bytecode signatures:
1. Built-in LLVM (based on LLVM 2.8)
2. Built-in bytecode interpreter
3. System-installed LLVM (support limited to LLVM 3.6 at this time, although
Debian has had success with a set of patches that enabled support up to 3.9).
With 0.
> Am 17.07.2018 um 14:44 schrieb Micah Snyder (micasnyd) :
>
> ClamAV has 3 options for handling bytecode signatures:
> • Built-in LLVM (based on LLVM 2.8)
> • Built-in bytecode interpreter
> • System-installed LLVM (support limited to LLVM 3.6 at this time,
> although Debian
You're making an assumption that the LLVM 3.7-3.9 patches are ready-to-take.
Last time I worked with them I had some issues with the patches on systems
other than Debian. At the time, we were attempting to wrap up a _very_ long
development cycle with final bug fixes and regression testing. We
> Am 17.07.2018 um 15:47 schrieb Micah Snyder (micasnyd) :
>
> You're making an assumption that the LLVM 3.7-3.9 patches are ready-to-take.
Debian seems to use it since a while on all its stable and unstable branches...
> Last time I worked with them I had some issues with the patches on syste
On Tuesday 17 July 2018, Micah Snyder (micasnyd) wrote:
> If you don't provide the older LLVM 3.6 for ClamAV, it will use
> it's built-interpreter rather than just-in-time-compile the signatures.
Thanks.
--
Regards,
Sergey
___
clamav-users mailing l
An update, I got clamav-milter to run, from the clamav-milter logs:
Tue Jul 17 15:34:15 2018 -> +++ Started at Tue Jul 17 15:34:15 2018
Tue Jul 17 15:34:15 2018 -> Probe for slot 1 returned: success
Tue Jul 17 15:35:50 2018 -> +++ Started at Tue Jul 17 15:35:50 2018
Tue Jul 17 15:35:50 2018 -> Prob
Micah,
I installed zlib 1.2.4.5 (should I use an older version), replaced
libz.so.1.2.3 with
libz.so.1.2.4.5 (and renamed it) and copied libz.a to /lib.
Running freshclam without rebooting box got this:
root@centos zlib-1.2.4.5]# freshclam -v
Current working dir is /var/lib/clamav
Max retries ==
Wait... so it worked ok after upgrading to 1.2.4.5 before you rebooted but then
afterwards you're having the same error or a different error? I'm a little
confused, sorry.
Micah
Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.
On Jul 17, 2018, at 8:21 PM, Jay Hart mailto:jh...@kev
Micah,
It never worked...
The freshclam -v command output (previously posted) is what i got after I
installed the 1.2.4.5
libs. The last line: LibClamAV debug: in cli_tgzload()
just sat there for 10-15 mins until I killed the process.
I had manually downloaded main.cvd and daily.cvd prior to
19 matches
Mail list logo
