Hmm, that is a nice option, I agree. However, what stops you from making a proxying filter that pipes with stunnel?
Incidently, you might want to take a look at ftp://ftp.stacken.kth.se/pub/httpproxy/. It's a hack that implements the above suggestion. [[EMAIL PROTECTED] - Tue Sep 3 15:50:37 2002]: > I had to test a couple of proxy servers lately which had problems passing > CONNECT connections. I was missing a tool "like s_client but using a > proxy", so I added a quick hack to s_client. This patch adds a switch > $ openssl s_client -proxy myproxy:8080 -connect remoteserver:443 > ---------------------^^^^^^^^^^^^^^^^^^^ > which tunnels the secure connection over an HTTP proxy tunnel. > > I call it a "hack" because > a) I think there must be better ways to receive the response > "HTTP/1.x 200 OK" from the proxy but read()ing it directly > b) the echo of the proxy response should be filtered to display > only for the appropriate -verbosity level. > c) no attempt is made to catch connection errors or responses > other than "200 OK" from the proxy (think of -proxyauth user:pass) > > Anyway, I thought someone might find this useful, so feel free to improve! > > Martin -- Richard Levitte ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
