Curl is used for both TCP sockets and local unix sockets.
Outside of building a newer version of curl yourself, or installing using our RPM for ClamAV 0.104.1 from https://www.clamav.net/downloads, I don't have a good solution for you.
As Ged noted, other RHEL users on the list may have another recommendation.
Regards,Micah
Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.
From: clamav-users <clamav-users-bounces@lists.clamav.net> on behalf of G.W. Haywood via clamav-users <clamav-users@lists.clamav.net>
Sent: Thursday, December 16, 2021 3:22 AM
To: Jonathan Prater via clamav-users <clamav-users@lists.clamav.net>
Cc: G.W. Haywood <clamav@jubileegroup.co.uk>
Subject: Re: [clamav-users] clamAV On-Access Scanning problemHi there,
On Wed, 15 Dec 2021, Jonathan Prater via clamav-users wrote:
> If I understand correctly, the curl requirement is solely to support file
> descriptor passing via a local Unix socket. If I use a TCP socket
> (listening only on localhost) for clam, does that eliminate the curl
> requirement?
That's the way it reads. Having said that I haven't used a Red Hat
system for nearly twenty years so YMMV. There are probably RHEL users
on the mailing list, so if you're patient you might get a more useful
response from one of them or even from somebody at Sourcefire.
--
73,
Ged.
_______________________________________________
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