[clamav-users] ClamAV® blog: ClamAV 0.100.0 has been released!
Micah Snyder (micasnyd)
micasnyd at cisco.com
Tue Jul 17 09:47:36 EDT 2018
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 decided it was more important to get the release out. The LLVM patches were pushed to the next release (aka 0.101).
For reference, our Bugzilla ticket to apply the LLVM 3.7, 3.8, 3.9 patches is here. Please bare in mind if you read the ticket that our product versioning changed. Our previous lead didn't recognize a need for security/patch releases. 0.99.3 and 0.99.4 ended up being security patch releases. In the ticket, "0.99.3" refers to 0.100, and "0.99.4" refers to 0.101:
Cisco Systems, Inc.
On Jul 17, 2018, at 9:15 AM, Sierk Bornemann <sierkb at gmx.de<mailto:sierkb at gmx.de>> wrote:
Am 17.07.2018 um 14:44 schrieb Micah Snyder (micasnyd) <micasnyd at cisco.com<mailto:micasnyd at cisco.com>>:
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 has had success with a set of patches that enabled support up to 3.9).
Concerning your last item „Debian has had success with a set of patches that enabled support up to 3.9", you mean
And why not _at least_ take these successful and ready-to-take patches and merge them by the clamav team into the official clamav upstream sources to _at least_ officially support LLVM up to version 3.9?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the clamav-users