If you're going to expose clamd TCP sockets to your network, please protect
those sockets with SSH tunneling/port forwarding. Clamd sockets are not
secured. The connection is neither encrypted nor authenticated.
-Micah
On 4/4/19, 4:21 AM, "clamav-users on behalf of Matus UHLAR - fantomas"
<clamav-users-boun...@lists.clamav.net on behalf of uh...@fantomas.sk> wrote:
On 03.04.19 18:38, Tom Brady via clamav-users wrote:
>I have tried using the tcpsocket parameter on the clamd.conf. I have tow
> different clamd instances running on different servers. While I can get
> the clamdscan to talk to the local (on the same server) clamd instance, I
> cannot get clamdscan to talk to an remote instance of clamd running on a
> different server and different port.
is clamd really listening on TCP on the second server?
isn't the second server firewalled?
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Save the whales. Collect the whole set.
_______________________________________________
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
