Re: TLS Pool could add HTTPS to Privoxy

Hello Ian,

> Ian Silvester <mailto:[email protected]>
> 2 February 2016 at 23:02
> Thanks Rick,
>

> I suspect that this will be attractive to our project.

:-)

> When you say the C parallel do you mean that the code is developed in
> parallel in two different languages? Whilst clearly there exists
> HTTP(S) as a language-agnostic 'API' interface between the two
> softwares, I personally have a preference for compiled C over Python.

Same here.

The TLS Pool is a daemon written in C, communicating with TLS-using
applications like Privoxy over a UNIX domain socket (or a variation on
non-POSIX a.k.a. Windows).  Privoxy could directly use the sockets or
application-support wrappers in C and Python, the last of which is used
in this demo.

Simple example programs written in C, not an HTTPS proxy but a simple
chat client and server over TLS, are testcli and testsrv,
https://github.com/arpa2/tlspool/blob/master/tool/testcli.c
https://github.com/arpa2/tlspool/blob/master/tool/testsrv.c

The simplicity of the TLS Pool comes from separation of logic:
 * applications like Privoxy only know about streams and (to be) proven
identities
 * protocol settings are setup in databases, but not by the application
 * optional user-interfacing code can guide local identity selection and
PIN entry

Cheers,
 -Rick

P.S. This is work in progress, scheduled for release on July 1st. 
Specifically, the validation framework is something I still need to work
on; but that is all isolated from applications like Privoxy.


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140