, issues a HTTP
CONNECT call.
4) We now need to do a SSL handshake inside the first tunnel
The application is an HTTPS proxy server with support for transparent
decryption of HTTP connect calls.
--
*David Hinkle*
*Senior Software Developer*
*Phone:* 800.243.3729x3000
*Email:* hin
Engineer
Akamai Technologies, Cambridge MA
IM: rs...@jabber.me Twitter: RichSalz
--
*David Hinkle*
*Senior Software Developer*
*Phone:* 800.243.3729x3000
*Email:* hin...@cipafilter.com
*Hours:* Mon-Fri 8:00AM-5:00PM (CT)
? Or am I wrong and this shouldn't be happening?
--
*David Hinkle*
*Senior Software Developer*
*Phone:* 800.243.3729x3000
*Email:* hin...@cipafilter.com
*Hours:* Mon-Fri 8:00AM-5:00PM (CT)
, suboptimal and you have to do this. A patch to update the doc (where
should we put it?) would be appreciated.
--
Principal Security Engineer
Akamai Technologies, Cambridge MA
IM: rs...@jabber.me Twitter: RichSalz
--
*David Hinkle*
*Senior Software Developer*
*Phone:* 800.243.3729x3000
Just so I make sure I understand, I just need to do something like:
while ((err = ERR_get_error()));
When I switch work and everything will be ok?
On Thu, Aug 14, 2014 at 4:44 PM, David Hinkle hin...@cipafilter.com wrote:
This is where I would have expected to find it:
https
-ssl-wbio
$7 = {method = 0x7f136db8a5e0, callback = 0, cb_arg = 0x0, init = 1,
shutdown = 0, flags = 9, retry_reason = 0, num = 91, ptr = 0x0, next_bio =
0x0, prev_bio = 0x0, references = 1, num_read = 7752, num_write = 2188,
ex_data = {sk = 0x0, dummy = 862740789}}
--
*David Hinkle*
*Senior
of this communication is prohibited. If you
have received this communication in error, please erase all copies of the
message and its attachments and notify us immediately
--
*David Hinkle*
*Senior Software Developer*
*Phone:* 800.243.3729x3000
*Email:* hin...@cipafilter.com
*Hours:* Mon-Fri
to improperly conclude that there was an option I was missing in the
code.
So, thanks very much for you time and effort in helping to dispel my
confusion.
- David
On Tue, Jan 22, 2013 at 3:39 PM, Dave Thompson dthomp...@prinpay.comwrote:
From: owner-openssl-us...@openssl.org On Behalf Of David Hinkle
:7b:fc:ee:7f:
a2:16:52:b5:67:67:d3:40:db:3b:26:58:b2:28:77:3d:ae:14:
77:61:d6:fa:2a:66:27:a0:0d:fa:a7:73:5c:ea:70:f1:94:21:
65:44:5f:fa:fc:ef:29:68:a9:a2:87:79:ef:79:ef:4f:ac:07:
77:38
--
*David Hinkle*
*Senior Software Developer*
*Phone:* 800.243.3729x3000
hello, and from
there decide if I want to engage the openssl library on the connection.
Any recommendations for how I can stuff the client hello that I've
previously read into the SSL object so that when I call SSL_accept
everything is cool?
--
*David Hinkle*
*Senior Software Developer*
*Phone
10 matches
Mail list logo