[QCLUG] QCLUG

David Hinkle hinkle@cipafilter.com
Tue, 30 Sep 2008 09:24:40 -0500


This is a multi-part message in MIME format.

---------------------- multipart/alternative attachment
Very interesting.  I'll have to look this over.

David


-----Original Message-----
From: qclug-bounces@qclug.org on behalf of Dave Bergert
Sent: Mon 9/29/2008 10:07 PM
To: qclug@qclug.org
Subject: Re: [QCLUG] QCLUG
=20
Also: I ran into this links related ot real time scanning on windows =20
using ClamAV.

How to Enable Real Time Virus Scanning for ClamAV
http://www.techmalaya.com/2008/05/10/clamav-real-time-scan/

But -- this is really off-topic for our group ? right ?  :)


On Sep 29, 2008, at 10:02 AM, David Hinkle wrote:

> Unfortunately what actually prevents a real time anti-virus engine =20
> for windows from being released to the wild under the GPL is that =20
> fact that in order to write such an engine, a person needs =20
> Microsoft's specialized dev kit for interfacing with the hard drive =20
> device layer.  Such device drivers are called file system filters or =20
> minifilters.  This dev kit is only offered under terms that are very =20
> hostile to anybody releasing a GPL real time anti-virus engine.  I =20
> don't think anybody with the wherewithal to write such an engine has =20
> had the guts to test Microsoft in court.
>
> What we did, was to write a standalone application called a =20
> "minifilter" that is loaded like a device driver.  Another =20
> standalone application that is a tray client and user interface.   =20
> Then I ported the clamav engine to windows and turned it into a =20
> service that accepts requests to scan over a named pipe.  The source =20
> code for the clamav port is available, of course, but the other two =20
> applications are proprietary.   I am actually going to propose to my =20
> company that we open source this project, but the decision is not =20
> mine alone.
>
> Before we wrote this, we actually tried working with clamwin project =20
> instead.  I offered to work with them on the port and they accepted =20
> my offer but then they just strung me along for months without =20
> giving me access to their repositories.  We couldn't afford to wait =20
> for them so we had to develop our own, which was a very expensive =20
> and time consuming project, as you may imagine.
>
> David
>
> -----Original Message-----
> From: qclug-bounces@qclug.org on behalf of Aaron Johnson
> Sent: Mon 9/29/2008 7:59 AM
> To: qclug@qclug.org
> Subject: RE: [QCLUG] QCLUG
>
> I noticed that your appliance (CIPAFilter) uses a real-time =20
> antivirus client
> based on the open source ClamAV engine.
>
> Does DerbyTech contribute to the ClamWin project at all? I know one =20
> thing
> that ClamWin has been talking about for a LONG time is developing an
> on-access real-time scanning function...
>
> -----Original Message-----
> From: qclug-bounces@qclug.org [mailto:qclug-bounces@qclug.org] On =20
> Behalf Of
> David Hinkle
> Sent: Monday, September 29, 2008 12:46 AM
> To: qclug@qclug.org
> Subject: RE: [QCLUG] QCLUG
>
> CIPAFilter uses a lot of open source for our basic functionality, =20
> such as
> firewall, routing, NAT, etc... We use Ubunto Linux for the OS.  We =20
> do use
> ClamAv, but not freeswan or squid. (We did use freeswan in the past).
>
> However, our core features (such as the proxy, reporting, =20
> greylisting), are
> implemented with proprietary non-gpl software we developed.  We also =20
> use
> spamassassin and sendmail in conjunction with a proprietary milter we
> developed for our mail features and to implement some extensions to =20
> SPF,
> greylisting and some additional header analysis.
>
> There's no download link, but of course our customers can request =20
> any GPL
> software from us that we distribute with our product.  In some cases =20
> third
> parties can also make requests from us, but you need to be in =20
> possession of
> the binaries and request a specific software package used in the =20
> product by
> name. (See GPLv3 6-b).
>
> We're very careful about licensing, none of our proprietary software =20
> is
> linked with GPL binaries or libraries, and as a company we focus on =20
> the
> development of our proprietary software.  Linux is a platform for =20
> us, not an
> end to itself.  It does, however, make an excellent platform.
>
> But all that being said, we also believe in being in compliance with =20
> the
> spirit of the GPL.  For example, if someone wants the source for a GPL
> package I've actually modified I'll be happy to provide it via email =20
> at no
> charge,  and I don't much care if they're a customer or not.  But =20
> you'd have
> to tell me what package you want the source for.
>
> David
>
>
> -----Original Message-----
> From: qclug-bounces@qclug.org on behalf of Dave Bergert
> Sent: Sun 9/28/2008 10:41 PM
> To: qclug@qclug.org
> Subject: Re: [QCLUG] QCLUG
>
> Welcome, the list have been quite of late.
>
> I was looking at CIPAFiler ..  It appears that CIPAFilter uses some
> GPL'ed open source projects, e..g FreeSwan, ClamAV, squid.  -- do you
> have a link to download the source of CIPAFilter ?  I'm interested in
> learning more about it.
>
> Regards.
>
>
> On Sep 28, 2008, at 9:23 PM, David Hinkle wrote:
>
> >
> > Active? Alive?  What's your status.  I'm David Hinkle, Sr.
> > Programmer for CIPAFilter.  CIPAFilter is a Quad Cities company that
> > specializes in products using embedded linux.  I'm interested in
> > becoming involved with the LUG.
> >
> > David
> >
>
>
>
>
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.169 / Virus Database: 270.7.4/1695 - Release Date: =20
> 9/27/2008
> 1:11 PM
>
> _______________________________________________
> QCLUG mailing list
> QCLUG@qclug.org
> http://qclug.org/mailman/listinfo/qclug
>
>

Dave Bergert
dbergert@gmail.com





---------------------- multipart/alternative attachment
An HTML attachment was scrubbed...
URL: http://qclug.org/pipermail/qclug/attachments/d681ff50/attachment.htm

---------------------- multipart/alternative attachment--