Re: [Clamav-users] Comment on TCP option in clamd

2004-11-04 Thread Scott Ryan
On Wed, 2004-11-03 at 09:48 +1300, Jason Haar wrote: > Hi there > > I think the TCP option needs some more explicit documentation, as I have > begun seeing RPMs of clamav where the Socket option is *disabled* and the > TCP option is *enabled* as the defaults. > > As far as I'm aware, that is *not

RE: [Clamav-users] Comment on TCP option in clamd

2004-11-04 Thread Samuel Benzaquen
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Andy Fiddaman > Sent: Thursday, November 04, 2004 6:49 AM > > > > On Wed, 3 Nov 2004, Jason Haar wrote: > > ; Hi there > ; > ; I think the TCP option needs some more explicit documentation, as I have > ;

Re: [Clamav-users] Comment on TCP option in clamd

2004-11-04 Thread Andy Fiddaman
On Wed, 3 Nov 2004, Jason Haar wrote: ; Hi there ; ; I think the TCP option needs some more explicit documentation, as I have ; begun seeing RPMs of clamav where the Socket option is *disabled* and the ; TCP option is *enabled* as the defaults. ; ; As far as I'm aware, that is *not* a good idea.

[Clamav-users] Comment on TCP option in clamd

2004-11-03 Thread Jason Haar
Hi there I think the TCP option needs some more explicit documentation, as I have begun seeing RPMs of clamav where the Socket option is *disabled* and the TCP option is *enabled* as the defaults. As far as I'm aware, that is *not* a good idea. Not only are there now network security issues you s