On Monday 14 September 2020, Joel Esler (jesler) via clamav-users wrote:

> Bug fixes
>
> Fixed behavior of freshclam --quiet option. Patch courtesy of Reio Remma.

What has been fixed? I keep seeing the message "Connecting via proxy" and
the virusdb update reports.

# freshclam --version
ClamAV 0.103.0/25943/Wed Sep 30 17:54:21 2020

without update:

# /usr/bin/freshclam --quiet --daemon-notify
Connecting via proxy

with update (a snippet):

# /usr/bin/freshclam --quiet --daemon-notify
Connecting via proxy
*   Trying x.x.x.x:3128...
* TCP_NODELAY set
* Connected to proxy (213.156.192.11) port 3128 (#0)
* allocate connect buffer!
* Establish HTTP proxy tunnel to database.clamav.net:443
> CONNECT database.clamav.net:443 HTTP/1.1
Host: database.clamav.net:443
User-Agent: ClamAV/0.103.0 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64)
Proxy-Connection: Keep-Alive

< HTTP/1.1 200 Connection established
....
> GET /daily-25943.cdiff HTTP/2
....
* Connection #0 to host proxy left intact


without proxy and with update (a snippet):

# /usr/bin/freshclam --quiet --daemon-notify
*   Trying 104.16.219.84:443...
* TCP_NODELAY set
* Connected to database.clamav.net (104.16.219.84) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
....
> GET /daily-25943.cdiff HTTP/2
....
* Connection #0 to host database.clamav.net left intact


-- 
Regards, Sergey

_______________________________________________

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