<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 2/13/2017 18:41, Salz, Rich wrote:<br>
<blockquote
cite="mid:8d0d983f0d2640ab9327910aeb266d9f@usma1ex-dag1mb3.msg.corp.akamai.com"
type="cite">
<blockquote type="cite">
<pre wrap="">It is a home grown HTTPS server.
</pre>
</blockquote>
<pre wrap="">
Well, then what does your server do?
To be very very clear: TLS is a *send the bytes* protocol. It knows nothing about EBCDIC, ASCII, text, etc.
</pre>
</blockquote>
<br>
To back up what Rich has said I pass a LOT of data, including HTTPS
and binary protocols between different machines (which may contain
any particular set of bytes in a packet format) using OpenSSL as the
encryption method for said transport and I've had no issues
whatsoever with whatever I stuff in the pipe coming out the other
end unmolested.<br>
<br>
Do be aware of the semantics and exceptions (which you must handle
-- or else) described in the documentation however -- especially for
non-blocking sockets. Due to the potential for renegotiations and
similar failing to pay attention to those can result in some pretty
interesting "surprises".<br>
<br>
<div class="moz-signature">-- <br>
Karl Denninger<br>
<a href="mailto:karl@denninger.net">karl@denninger.net</a><br>
<i>The Market Ticker</i><br>
<font size="-2"><i>[S/MIME encrypted email preferred]</i></font>
</div>
</body>
</html>