Nothing has changed on our end. 

Sent from my  iPhone

> On Dec 23, 2020, at 13:57, Chris via clamav-users 
> <clamav-users@lists.clamav.net> wrote:
> 
> 
> Hello
> 
> I'm using ClamAV version 0.103.0 and recently whenever I try to update ClamAV 
> with freshclam, for some reason it spits out this error:
> 
> WARNING: Download failed (60) WARNING:  Message: SSL peer certificate or SSH 
> remote key was not OK
> WARNING: getpatch: Can't download daily-26002.cdiff from 
> https://database.clamav.net/daily-26002.cdiff
> 
> I Googled for some answers on this and a few of the answers said to make sure 
> my "ca-certificates" were updated.  For the record my OS is Linux Devuan 
> Beowulf (Debian 10) and it has the latest version of ca-certificates 
> available (20200601).  This also includes ca-certificates-java (20190405) and 
> ca-certificates-mono (5.18.0.240+dfsg-3).  Running "update-ca-certificates" 
> ran successfully, but I'm still getting that above error when updating ClamAV.
> 
> This never happened before, as running freshclam always updated the 
> definitions without any issues.  Is it something on my end I need to do or is 
> it an issue with ClamAV?
> 
> Thanks
> -- 
> Chris Garcia
> https://supersamplestar.bandcamp.com/
> https://www.bitchute.com/channel/supersamplestar/
> Securely sent with Tutanota. Claim your encrypted mailbox today! 
> https://tutanota.com
> 
> _______________________________________________
> 
> 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