The oldest version that is currently supported is the 0.101.x line, but that 
will be EOL in January.  So I would recommend 0.103.x or higher.

— 
Sent from my  iPad

> On Dec 2, 2021, at 13:10, novpenguincne via clamav-users 
> <clamav-users@lists.clamav.net> wrote:
> 
> Thank you for the quick response.  So that would lead into the logical next 
> question.  What would be the earliest client version that would work?  I 
> tried installing the 103.x client on that box but 103.x requires SystemD and 
> this older box is still using SystemV.  So is there a version of the client 
> that is new enough to accept the new definition files but still old enough to 
> install on a SystemV-based o/s?
> 
> James
> 
> Sent with ProtonMail Secure Email.
> 
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> 
>> On Thursday, December 2nd, 2021 at 10:49 AM, Joel Esler (jesler) 
>> <jes...@cisco.com> wrote:
>> 
>> James,
>> 
>> Thanks for your email. ClamAV definitions won’t even work on those older 
>> versions anymore. The Flevel for the main.cvd and daily.cvd are now set 
>> higher than that, so those systems shouldn’t be able to load the newer 
>> definitions.
>> 
>> —
>> 
>> Sent from my  iPad
>> 
>>>> On Dec 2, 2021, at 11:08, novpenguincne via clamav-users 
>>>> clamav-users@lists.clamav.net wrote:
>>> 
>>> To facilitate bandwidth issues, I've set up an internal clam proxy server 
>>> on SLES15 running the 103.x client. I have successfully connected to it 
>>> using a different SLES15 box also running the 103.x client and downloaded 
>>> updates to it.
>>> 
>>> However, I still have an older SLES11 box running the 98.x client. Due to 
>>> extenuating circumstances, this box is not a candidate for an o/s upgrade. 
>>> I also know from CLAM documentation that clients older than 100.x are no 
>>> longer supported. But I would still like to have some a/v on this box until 
>>> its retirement so I was trying to have it download from the proxy server as 
>>> well.
>>> 
>>> When I first attempted, it failed because it was trying to download 
>>> main.cld which didn't exist on the proxy. So I turned off "scripted 
>>> updates" on both the proxy and the target SLES11 box which is now forcing 
>>> everything to use cvd files only. But now when I run freshclam on the 
>>> SLES11 box, I'm getting different errors. It downloads the daily.cvd 
>>> successfully. Then it tries to load signatures from daily.cvd. And then I 
>>> get a sequence of errors:
>>> 
>>> ERROR: During database Load
>>> 
>>> WARNING: [LibClamAV] cli_ac_addsig: Signature for 
>>> Win.Backdoor.SystemBC-9885562-0 is too short
>>> 
>>> ERROR: Failed to load new database: Malformed database
>>> 
>>> WARNING: Database load exited with status 55
>>> 
>>> ERROR: Failed to load new database
>>> 
>>> Do I need to make a change in the freshclam.conf to get this to work? Or is 
>>> it a matter of the 98.x client unable to read datafiles designed for 103.x 
>>> clients?
>>> 
>>> James
>>> 
>>> clamav-users mailing list
>>> 
>>> clamav-users@lists.clamav.net
>>> 
>>> https://lists.clamav.net/mailman/listinfo/clamav-users
>>> 
>>> Help us build a comprehensive ClamAV guide:
>>> 
>>> https://github.com/vrtadmin/clamav-faq
>>> 
>>> http://www.clamav.net/contact.html#ml
> 
> _______________________________________________
> 
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Reply via email to