Thanks for the answer. I think I have to choose from one of these: ;) 1/ write a CRL patch myself 2/ become a paying customer 3/ explore newest stunnel, which seems to have CRL checking implemented
-D > -----Original Message----- > From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 29, 2004 4:49 PM > To: David Hajek > Cc: [EMAIL PROTECTED] > Subject: RE: [squid-users] CRL status in squid > > On Thu, 29 Apr 2004, David Hajek wrote: > > > Hm. Seems strange to me. Can't believe that anyone from opensource > > world don't use certificate authentication. > > I developed the simple client certificate authentication you > can find in Squid-3.0 as a prototype for a customer > investigating the use of client certificates, they however > concluded that password authentication was sufficient for now > and CRL never got implemented. > > As in all other Open Source projects the bulk of the Squid > development is driven by people having needs and making sure > their needs is fulfilled. > This is how the Open Source world works. > > The main difference from proprietary software is that you > have the choice to see things implemented and are not locked > down by the product plan of the provider. > > In Free Software (which Squid classifies as, together with > any other GPL > software) there is also some restrictions in how > modifications may be done if not done direcly by the end-user > to guarantee that a Open Source provider does not lock down > his customers. > > You can find more information about the history and status of > the SSL support in Squid at http://devel.squid-cache.org/ssl/ > > Regards > Henrik > >
