I am trying to use the protocol entries in the config file as shown below (xyz substituted to protect employer & vendor). Below is the log. Stunnel abends as it is trying to authenticate to our corporate proxy. The network guys are seeing the attempt to authenticate but it does not appear to complete. Any thoughts?
key=maxstpb.crt
debug=7
output=stunnel.log
client=yes
[MarketAxess]
accept=127.0.0.1:12345
delay=yes
TIMEOUTbusy=120
TIMEOUTconnect=120
connect=xyz.xyz.com:80
protocol=connect
protocolHost=xyz.xyz.com:443
protocolCredentials=xyz:xyz
2006.08.21 15:13:24 LOG5[2520:1312]: stunnel 4.15 on x86-pc-mingw32-gnu with
OpenSSL 0.9.7i 14 Oct 2005
2006.08.21 15:13:24 LOG5[2520:1312]: Threading:WIN32 SSL:ENGINE
Sockets:SELECT,IPv4
2006.08.21 15:13:24 LOG5[2520:3184]: No limit detected for the number of clients
2006.08.21 15:13:24 LOG7[2520:3184]: FD 192 in non-blocking mode
2006.08.21 15:13:24 LOG7[2520:3184]: SO_REUSEADDR option set on accept socket
2006.08.21 15:13:24 LOG7[2520:3184]: MarketAxess bound to 127.0.0.1:12345
2006.08.21 15:14:00 LOG7[2520:3184]: MarketAxess accepted FD=200 from
127.0.0.1:4200
2006.08.21 15:14:00 LOG7[2520:3184]: Creating a new thread
2006.08.21 15:14:00 LOG7[2520:3184]: New thread created
2006.08.21 15:14:00 LOG7[2520:2560]: MarketAxess started
2006.08.21 15:14:00 LOG7[2520:2560]: FD 200 in non-blocking mode
2006.08.21 15:14:00 LOG5[2520:2560]: MarketAxess connected from 127.0.0.1:4200
2006.08.21 15:14:00 LOG7[2520:2560]: FD 416 in non-blocking mode
2006.08.21 15:14:00 LOG7[2520:2560]: MarketAxess connecting xyz.xyz.xyz.xyz:80
2006.08.21 15:14:00 LOG7[2520:2560]: connect_wait: waiting 120 seconds
2006.08.21 15:14:00 LOG7[2520:2560]: connect_wait: connected
2006.08.21 15:14:00 LOG7[2520:2560]: Remote FD=416 initialized
2006.08.21 15:14:00 LOG5[2520:2560]: Negotiations for connect (client side)
started
2006.08.21 15:14:00 LOG7[2520:2560]: -> CONNECT xyz.xyz.com:443 HTTP/1.1
Alan R. Hutchison
515-362-1272
-----Message Disclaimer----- This e-mail message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply email to Connect@principal.com and delete or destroy all copies of the original message and attachments thereto. Email sent to or from the Principal Financial Group or any of its member companies may be retained as required by law or regulation. Nothing in this message is intended to constitute an Electronic signature for purposes of the Uniform Electronic Transactions Act (UETA) or the Electronic Signatures in Global and National Commerce Act ("E-Sign") unless a specific statement to the contrary is included in this message. While this communication may be used to promote or market a transaction or an idea that is discussed in the publication, it is intended to provide general information about the subject matter covered and is provided with the understanding that The Principal is not rendering legal, accounting, or tax advice. It is not a marketed opinion and may not be used to avoid penalties under the Internal Revenue Code. You should consult with appropriate counsel or other advisors on all matters pertaining to legal, tax, or accounting obligations and requirements.