Re: [clamav-users] Licensing & DLLs

2012-05-14 Thread Török Edwin
On 05/15/2012 12:26 AM, Paul Smith wrote: > > We could talk to clamd using TCP/IP, but since the clamd protocol doesn't > seem to be clearly documented, that would involve reverse engineering > clamdscan and rewriting it. The protocol is described in: man 8 clamd --Edwin __

Re: [clamav-users] From a newbie: ClamAV scans shut down Google Chrome

2012-05-14 Thread Jim Preston
On 05/14/2012 12:18 PM, Teresa K. Fowler wrote: [snip] I do hope I have clarified things for you, if not just ignore this posting except for the etiquette of not top posting. -- Jim Preston Dear Jim Preston, You have explained everything beautifully, clearly even for me, a right-brain writer,

Re: [clamav-users] Licensing & DLLs

2012-05-14 Thread Paul Smith
On 14/05/2012 20:57, Chuck Swiger wrote: On May 14, 2012, at 12:02 PM, Simon Hobson wrote: Chuck Swiger wrote: What if WE made an AV plugin DLL to link our software with libclamav? If your software license isn't GPL-miscible, then you should not redistribute the combination of your software

Re: [clamav-users] Licensing & DLLs

2012-05-14 Thread Joel Esler
On May 14, 2012, at 11:55 AM, Paul Smith wrote: > OK, I know this will probably have come up over and over, but I couldn't find > anything in the archives. > > We produce a commercial mail server (not GPLed) which has a defined DLL > interface to allow people to create plugins to integrate with

Re: [clamav-users] Licensing & DLLs

2012-05-14 Thread Chuck Swiger
On May 14, 2012, at 12:02 PM, Simon Hobson wrote: > Chuck Swiger wrote: >>> What if WE made an AV plugin DLL to link our software with libclamav? >> >> If your software license isn't GPL-miscible, then you should not >> redistribute the combination of your software, the plugin, and ClamAV. > >

Re: [clamav-users] Licensing & DLLs

2012-05-14 Thread Simon Hobson
Chuck Swiger wrote: > What if WE made an AV plugin DLL to link our software with libclamav? If your software license isn't GPL-miscible, then you should not redistribute the combination of your software, the plugin, and ClamAV. Isn't this a case where the component they've linked with (in

Re: [clamav-users] From a newbie: ClamAV scans shut down Google Chrome

2012-05-14 Thread Teresa K. Fowler
-Original Message- From: clamav-users-boun...@lists.clamav.net [mailto:clamav-users-boun...@lists.clamav.net] On Behalf Of Jim Preston Sent: Monday, May 14, 2012 2:39 AM To: ClamAV users ML Subject: Re: [clamav-users] From a newbie: ClamAV scans shut down Google Chrome On 05/13/2012 03:00

Re: [clamav-users] Licensing & DLLs

2012-05-14 Thread Chuck Swiger
On May 14, 2012, at 8:55 AM, Paul Smith wrote: > We produce a commercial mail server (not GPLed) which has a defined DLL > interface to allow people to create plugins to integrate with virus scanners > (I'll call that an 'AV plugin DLL'). It's not specifically designed for > ClamAV, but for any

Re: [clamav-users] Licensing & DLLs

2012-05-14 Thread Michael Orlitzky
On 05/14/12 11:55, Paul Smith wrote: > > If we made our software link directly with libclamav, then, as far as I > can see we'd need to GPL our software, which isn't desirable Yup. > What if another person made an AV plugin DLL to link our software with > libclamav? I presume that by doing so,

[clamav-users] Licensing & DLLs

2012-05-14 Thread Paul Smith
OK, I know this will probably have come up over and over, but I couldn't find anything in the archives. We produce a commercial mail server (not GPLed) which has a defined DLL interface to allow people to create plugins to integrate with virus scanners (I'll call that an 'AV plugin DLL'). It's