Re: TLS Pool could add HTTPS to Privoxy
Ian Silvester <[email protected]> Wed, 3 Feb 2016 15:59:02 -0500
| Newsgroups | gmane.comp.web.privoxy.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============2582625385946991315== Content-Type: multipart/alternative; boundary="------------000906000208070605060001" This is a multi-part message in MIME format. --------------000906000208070605060001 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit That's great Rick, thanks for the detailed info. We will discuss internally (well, likely on this list) and, if there is general agreement, move forward with interoperability testing. If that goes well there is the potential to document TLS Pool as our recommended method for implementing HTTPS filtering support in Privoxy. Cheers, Ian On 2016-02-03 02:05, Rick van Rein wrote: > 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. > -- My PGP public key <http://diem.serveftp.net:8080/IanSilvesterPGPPublicKey.asc>. --------------000906000208070605060001 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> That's great Rick, thanks for the detailed info.<br> <br> We will discuss internally (well, likely on this list) and, if there is general agreement, move forward with interoperability testing. If that goes well there is the potential to document TLS Pool as our recommended method for implementing HTTPS filtering support in Privoxy.<br> <br> Cheers,<br> <br> Ian<br> <br> <br> <br> <div class="moz-cite-prefix">On 2016-02-03 02:05, Rick van Rein wrote:<br> </div> <blockquote cite="mid:[email protected]" type="cite"> <pre wrap="">Hello Ian, </pre> <blockquote type="cite"> <pre wrap="">Ian Silvester <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><mailto:[email protected]></a> 2 February 2016 at 23:02 Thanks Rick, </pre> </blockquote> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap="">I suspect that this will be attractive to our project. </pre> </blockquote> <pre wrap=""> :-) </pre> <blockquote type="cite"> <pre wrap="">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. </pre> </blockquote> <pre wrap=""> 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, <a class="moz-txt-link-freetext" href="https://github.com/arpa2/tlspool/blob/master/tool/testcli.c">https://github.com/arpa2/tlspool/blob/master/tool/testcli.c</a> <a class="moz-txt-link-freetext" href="https://github.com/arpa2/tlspool/blob/master/tool/testsrv.c">https://github.com/arpa2/tlspool/blob/master/tool/testsrv.c</a> 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. </pre> </blockquote> <br> <div class="moz-signature">-- <br> <a href="http://diem.serveftp.net:8080/IanSilvesterPGPPublicKey.asc">My PGP public key</a>.</div> </body> </html> --------------000906000208070605060001-- --===============2582625385946991315== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ 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=272487151&iu=/4140 --===============2582625385946991315== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ijbswa-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ijbswa-developers --===============2582625385946991315==--