Re: TLS Pool could add HTTPS to Privoxy

Hi Fabian,

> Interesting.

That's the most important thing I was hoping to hear  :)

>> Would this be a good solution for Privoxy?
>
> Without additional information that's hard to tell.
>
> Are you proposing to provide patches or that other people write them?

We have an open source development fund for TLS Pool and could probably
fund its integration into Privoxy, if it is considered useful.  That
could take the shape of an external code donation, or ask someone in the
Privoxy project to do it for us.  We're open to any proposal that is
reasonable.  As I said, the most important thing to me is that it is not
considered "too foreign" to be acceptable.  We can talk details, but the
main idea is that TLS is concentrated into a daemon of general use,
rather than having yet another application that requires its own TLS
implementation/configuration -- that is what the TLS Pool in general
wants to get away from.

As for our motivation for cooperation :- our project would be
demonstrable with Privoxy, making the authentication/encryption
mechanisms we added to the TLS Pool available to at least web users; we
cannot currently demonstrate that without an HTTPS proxy.  Privacy
filtering is an added value that fits well with this kind of
demonstration, I think.
> I briefly looked at the tlspool repository and it's not obvious to me
> that it's free software. Where and what is the license?

Excellent question.  It *definately is* open source software, but you
are right, I should pick one of BSD, GPL, LGPL.  These are in fact the
only three options that we'd consider for the TLS Pool.  What you're
seeing is that the software isn't in a 1.0 yet (although its
functionality is tested).  I will see to this.

Cheers,
 -Rick

------------------------------------------------------------------------------