The blog post concerning OpenSSL being required for ClamAV only has one reason as to why it might *benefit* ClamAV, the other reasons are why OpenSSL *itself* in good.
That single reason is: "We will be able to provide a better freshclam experience in a future release." What exactly does this mean? (The phrase "freshclam experience" is marketing speak, not a technical explanation.) Since adding complexity to a system tends to increase bugs and decrease security, I am leery of seeing ClamAV become even more complicated than it already has become. Paul On Wed, 26 Feb 2014 12:00:00 -0500 clamav-users-requ...@lists.clamav.net wrote: > > Message: 1 > Date: Wed, 26 Feb 2014 16:08:03 +0000 > From: "Joel Esler (jesler)" <jes...@cisco.com> > To: ClamAV users ML <clamav-users@lists.clamav.net>, > "clamav-de...@lists.clamav.net" > <clamav-de...@lists.clamav.net> Subject: [clamav-users] Introducing > OpenSSL as a dependency to ClamAV Message-ID: > <78e5f452-24f0-4e9d-91aa-5918e4241...@cisco.com> Content-Type: > text/plain; charset="us-ascii" > > On Friday last week I put a blog post up about introducing OpenSSL > into the ClamAV ecosystem. I wanted to make sure everyone saw it, > so please have a look at the blog post here: > > http://blog.clamav.net/2014/02/introducing-openssl-as-dependency-to.html > > -- > Joel Esler | Threat Intelligence Team Lead | Open Source Manager | > Vulnerability Research Team _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/support/ml
