<html><body><div>Rich,</div><div><br></div><div>Yeah, I have industrial strength Tylenol standing by. I'm expecting this to be painful, but not insurmountable for the handshake. If I'm unable to even get at the ultimate source/sink, I can't get anywhere.</div><div><br></div><div>I can deal with the HTTP side and the plethora of application-specific and threading issues, but I'm lost on the BIO part. I'll take any pointers or suggestions you can offer.</div><div><br></div><div>Thanks for responding and, hopefully, for responding again soon...</div><div><br></div><div>W</div><div><br>On Feb 19, 2015, at 06:52 PM, "Salz, Rich" <rsalz@akamai.com> wrote:<br><br></div><div><blockquote type="cite"><div class="msg-quote"><div class="_stretch"><blockquote class="quoted-plain-text" type="cite">I've been tasked with wrapping OpenSSL encrypted traffic in another protocol (HTTP).</blockquote><span class="body-text-content"><br>That's going to be a bit tricky, and require some pretty detailed knowledge of the protocol. For example, the initial setup -- the hello messages -- will require a couple of POST and reply messages. Even if you are only ever sending encrypted application data from A to B, you need bidirectional exchanges between the two parties.<br><br>-- <br>Principal Security Engineer, Akamai Technologies<br>IM: <a href="mailto:rsalz@jabber.me" data-mce-href="mailto:rsalz@jabber.me">rsalz@jabber.me</a> Twitter: RichSalz<br><br><br>_______________________________________________<br>openssl-dev mailing list<br>To unsubscribe: <a href="https://mta.openssl.org/mailman/listinfo/openssl-dev" data-mce-href="https://mta.openssl.org/mailman/listinfo/openssl-dev">https://mta.openssl.org/mailman/listinfo/openssl-dev</a><br></span></div></div></blockquote></div></body></html>