stunnel-users

3306 discussions

help
by Maddalena.Pulcini＠seleniacomms.com 31 Mar '05

31 Mar '05

Hi Mike, Thank you for your precious help. I am using stunnel as SSL client. The SSL server runs in a router. As you suggested me, I have done these changes: at first I have modified the stunnel.conf with options = SSL_OP_TLS_BLOCK_PADDING_BUG stunnel.conf ============================== client = yes debug=7 options = SSL_OP_TLS_BLOCK_PADDING_BUG [telnet] accept = 23 connect = 10.36.3.144:4433 ============================= but I have got this error ======================================= file stunnel.conf line 5: Illegal SSL option 2005.03.31 13:26:48 LOG3[3396:3716]: Server is down ======================================= After I have changed the stunnel.conf in this way: stunnel.conf ============================== client = yes debug=7 ciphers = RC4-MD5 [telnet] accept = 23 connect = 10.36.3.144:4433 ============================== The problem I had is now solved. But my question is: how can I know more about this protocol incompatibility? Is there an accurate documentation about that and also about stunnel configuration? Sorry but sometimes it's difficult for me to find (in the FAQ or other sessions) the informations that I need. Thanks&Regards Maddalena

2 1

Terminal services and stunnel 4.09
by Mattias Olsson 31 Mar '05

31 Mar '05

Hi! Im tying to access an internal Win2003 terminal server from my Linux box (internet). As i understand it stunnel should do the work. I have read some documents but im not sure... This is my setup. Linuxbox ----> Linuxbox ssh server | Firewall | Terminal server i wish to access. Can this be done or do i have to open a port in the fw to access the TS directly? Should stunnel.conf look like this on my linuxbox (client) cert = /usr/local/etc/stunnel/mail.pem client = yes On the TS? [TS] accept = 3000 connect = 3389 Should it have cert = ? Or could i on my linux ssh server have a config looking like this: [TS-remote] accept = 3000 connect = <internal-ip>:3389 Should it have cert = ? A novice man sends his best regards and thanks! /Kaz

1 0

Re: [stunnel-users] Libssl32.dll and Libeay32.dll Patents
by Brian Hatch 30 Mar '05

30 Mar '05

> I live in Maryland, United States. Can somebody please tell me if there > is a patent or some kind of legal restriction on the Libssl32.dll and > Libeay32.dll files available in the > http://www.stunnel.org/download/stunnel/win32/ directory? I would > really like to avoid compiling OpenSSL manually...gave it a shot this > evening and it bombed. I need to use Stunnel for strictly internal > purposes and not for any profit. The IDEA algorithm is patented, but I don't think Mike included that in his builds. You can configure Stunnel to only use specific ciphers, in which case you wouldn't be using it regardless. Does that make it legal? Consult a lawyer. Software patents suck. I'd download the openssl.exe and the libs and run 'openssl.exe ciphers -v' and see exactly which ciphers it includes and avoid any from which your legal team suggess you run away. -- Brian Hatch If we aren't supposed Systems and to eat animals, why Security Engineer are they made of meat? http://www.ifokr.org/bri/ Every message PGP signed

1 0

Stunnel 4.09 released
by Michal Trojnara 26 Mar '05

26 Mar '05

New stunnel 4.09 can be found on my FTP site: ftp://stunnel.mirt.net/stunnel/ Here is the ChangeLog entry: * DLLs for OpenSSL 0.9.7f. * Bugfixes - Compilation problem with undeclarated socklen_t fixed. - TIMEOUTclose is not used when there is any data in the buffers. - Stunnel no longer relies on close_notify with SSL 2.0 connections, since SSL 2.0 protocol does not have any alerts defined. - Closing SSL socket when there is some data in SSL output buffer is detected and reported as an error. - Install/chmod race condition when installing default certificate fixed. - Stunnel no longer installs signal_handler on ignored signals. Best regards, Mike

1 0

help
by Maddalena.Pulcini＠seleniacomms.com 25 Mar '05

25 Mar '05

Hi, I downloaded libeay32.dll and linssl32.dll. I started stunnel (4.07) and I did telnet to my router; after handshake I had the same problem. Client Debug ================ 2005.03.24 15:03:28 LOG5[3392:3104]: stunnel 4.07 on x86-pc-mingw32-gnu WIN32+IPv6 with OpenSSL 0.9.7f 22 Mar 2005 2005.03.24 15:03:28 LOG7[3392:2524]: Snagged 64 random bytes from C:/.rnd 2005.03.24 15:03:28 LOG7[3392:2524]: Wrote 1024 new random bytes to C:/.rnd 2005.03.24 15:03:28 LOG7[3392:2524]: RAND_status claims sufficient entropy for the PRNG 2005.03.24 15:03:28 LOG6[3392:2524]: PRNG seeded successfully 2005.03.24 15:03:28 LOG7[3392:2524]: Certificate: clcert.pem 2005.03.24 15:03:28 LOG7[3392:2524]: Key file: clcert.pem 2005.03.24 15:03:28 LOG5[3392:2524]: No limit detected for the number of clients 2005.03.24 15:03:28 LOG7[3392:2524]: FD 144 in non-blocking mode 2005.03.24 15:03:28 LOG7[3392:2524]: SO_REUSEADDR option set on accept socket 2005.03.24 15:03:28 LOG7[3392:2524]: telnet bound to 0.0.0.0:23 2005.03.24 15:03:39 LOG7[3392:2524]: telnet accepted FD=148 from 127.0.0.1:2133 2005.03.24 15:03:39 LOG7[3392:2524]: FD 148 in non-blocking mode 2005.03.24 15:03:39 LOG7[3392:2524]: Creating a new thread 2005.03.24 15:03:39 LOG7[3392:2524]: New thread created 2005.03.24 15:03:39 LOG7[3392:2556]: telnet started 2005.03.24 15:03:39 LOG5[3392:2556]: telnet connected from 127.0.0.1:2133 2005.03.24 15:03:39 LOG7[3392:2556]: FD 224 in non-blocking mode 2005.03.24 15:03:39 LOG7[3392:2556]: telnet connecting 10.36.3.144:4433 2005.03.24 15:03:39 LOG7[3392:2556]: connect_wait: waiting 10 seconds 2005.03.24 15:03:39 LOG7[3392:2556]: connect_wait: connected 2005.03.24 15:03:39 LOG7[3392:2556]: Remote FD=224 initialized 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): before/connect initialization 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 write client hello A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 read server hello A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 read server certificate A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 read server certificate request A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 read server done A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 write client certificate A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 write client key exchange A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 write certificate verify A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 write change cipher spec A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 write finished A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 flush data 2005.03.24 15:04:11 LOG7[3392:2556]: SSL state (connect): SSLv3 read finished A 2005.03.24 15:04:11 LOG7[3392:2556]: 1 items in the session cache 2005.03.24 15:04:11 LOG7[3392:2556]: 1 client connects (SSL_connect()) 2005.03.24 15:04:11 LOG7[3392:2556]: 1 client connects that finished 2005.03.24 15:04:11 LOG7[3392:2556]: 0 client renegotiatations requested 2005.03.24 15:04:11 LOG7[3392:2556]: 0 server connects (SSL_accept()) 2005.03.24 15:04:11 LOG7[3392:2556]: 0 server connects that finished 2005.03.24 15:04:11 LOG7[3392:2556]: 0 server renegotiatiations requested 2005.03.24 15:04:11 LOG7[3392:2556]: 0 session cache hits 2005.03.24 15:04:11 LOG7[3392:2556]: 0 session cache misses 2005.03.24 15:04:11 LOG7[3392:2556]: 0 session cache timeouts 2005.03.24 15:04:11 LOG6[3392:2556]: SSL connected: new session negotiated 2005.03.24 15:04:11 LOG6[3392:2556]: Negotiated ciphers: AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 2005.03.24 15:04:27 LOG7[3392:2556]: SSL alert (write): fatal: bad record mac 2005.03.24 15:04:27 LOG3[3392:2556]: SSL_read: 1408F455: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac 2005.03.24 15:04:27 LOG5[3392:2556]: Connection reset: 17 bytes sent to SSL, 191 bytes sent to socket 2005.03.24 15:04:27 LOG7[3392:2556]: telnet finished (0 left) =============================================================================== How can I procede? Thanks&Regards Maddalena

2 1

error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number
by Theodore W. Hildebrandt 24 Mar '05

24 Mar '05

I was running stunnel-4.08 under Windows XP-Home, using MS IEX as browser and Netscape 4.6 for e-mail. My ISP is AT&T Worldnet and I am accessing it via DSL and home wireless NW. Here is stunnel.conf: client = yes [pop3] accept = 110 connect = ipostoffice.att.net:995 [smtp] accept = 25 connect = imailhost.att.net:465 As instructed by AT&T, the e-mail servers have been specified as "localhost", both POP-3 and SMTP. The problem is that while I can download messages, I am unable to send e-mail because the "peer disconnects", and the log file carries the following messages: 2005.03.24 10:18:00 LOG5[2960:232]: smtp connected from 127.0.0.1:2194 2005.03.24 10:18:00 LOG5[2960:2428]: smtp connected from 127.0.0.1:2197 2005.03.24 10:18:01 LOG3[2960:232]: SSL_connect: Peer suddenly disconnected 2005.03.24 10:18:01 LOG3[2960:2428]: SSL_connect: Peer suddenly disconnected 2005.03.24 10:18:09 LOG3[2960:2084]: SSL_connect: 1408F10B: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number 2005.03.24 10:18:09 LOG3[2960:3384]: SSL_connect: 1408F10B: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number I have been able to run "openssl version" with the result: "OpenSSL 0.9.7e 25 Oct 2004" but I am unable to obtain the other outputs specified under the instructions for the "Stunnel-Users Mailing List". I have tried replacing libssl32.dll and libay32.dll with versions more recently downloaded (but with the same origination dates) and no improvement. So I am sending this message from another system running Win98 and stunnel-4.05, also using Netscape 4.6, which seems to work o.k. Please tell me how to get the right version number to work with stunnel-4.08, and WinXP. Additionally, it would be nice to know how to obtain the outputs suggested in the instructions for Stunnel-Users Mailing List.

1 0

help
by Maddalena.Pulcini＠seleniacomms.com 24 Mar '05

24 Mar '05

Hi, I downloaded libeay32.dll and linssl32.dll (ftp://stunnel.mirt.net/openssl/binary-0.9.7f-zlib/) . I started stunnel (4.07) and I did telnet to my router; after handshake I had the same problem. Client Debug ================ 2005.03.24 15:03:28 LOG5[3392:3104]: stunnel 4.07 on x86-pc-mingw32-gnu WIN32+IPv6 with OpenSSL 0.9.7f 22 Mar 2005 2005.03.24 15:03:28 LOG7[3392:2524]: Snagged 64 random bytes from C:/.rnd 2005.03.24 15:03:28 LOG7[3392:2524]: Wrote 1024 new random bytes to C:/.rnd 2005.03.24 15:03:28 LOG7[3392:2524]: RAND_status claims sufficient entropy for the PRNG 2005.03.24 15:03:28 LOG6[3392:2524]: PRNG seeded successfully 2005.03.24 15:03:28 LOG7[3392:2524]: Certificate: clcert.pem 2005.03.24 15:03:28 LOG7[3392:2524]: Key file: clcert.pem 2005.03.24 15:03:28 LOG5[3392:2524]: No limit detected for the number of clients 2005.03.24 15:03:28 LOG7[3392:2524]: FD 144 in non-blocking mode 2005.03.24 15:03:28 LOG7[3392:2524]: SO_REUSEADDR option set on accept socket 2005.03.24 15:03:28 LOG7[3392:2524]: telnet bound to 0.0.0.0:23 2005.03.24 15:03:39 LOG7[3392:2524]: telnet accepted FD=148 from 127.0.0.1:2133 2005.03.24 15:03:39 LOG7[3392:2524]: FD 148 in non-blocking mode 2005.03.24 15:03:39 LOG7[3392:2524]: Creating a new thread 2005.03.24 15:03:39 LOG7[3392:2524]: New thread created 2005.03.24 15:03:39 LOG7[3392:2556]: telnet started 2005.03.24 15:03:39 LOG5[3392:2556]: telnet connected from 127.0.0.1:2133 2005.03.24 15:03:39 LOG7[3392:2556]: FD 224 in non-blocking mode 2005.03.24 15:03:39 LOG7[3392:2556]: telnet connecting 10.36.3.144:4433 2005.03.24 15:03:39 LOG7[3392:2556]: connect_wait: waiting 10 seconds 2005.03.24 15:03:39 LOG7[3392:2556]: connect_wait: connected 2005.03.24 15:03:39 LOG7[3392:2556]: Remote FD=224 initialized 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): before/connect initialization 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 write client hello A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 read server hello A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 read server certificate A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 read server certificate request A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 read server done A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 write client certificate A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 write client key exchange A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 write certificate verify A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 write change cipher spec A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 write finished A 2005.03.24 15:03:39 LOG7[3392:2556]: SSL state (connect): SSLv3 flush data 2005.03.24 15:04:11 LOG7[3392:2556]: SSL state (connect): SSLv3 read finished A 2005.03.24 15:04:11 LOG7[3392:2556]: 1 items in the session cache 2005.03.24 15:04:11 LOG7[3392:2556]: 1 client connects (SSL_connect()) 2005.03.24 15:04:11 LOG7[3392:2556]: 1 client connects that finished 2005.03.24 15:04:11 LOG7[3392:2556]: 0 client renegotiatations requested 2005.03.24 15:04:11 LOG7[3392:2556]: 0 server connects (SSL_accept()) 2005.03.24 15:04:11 LOG7[3392:2556]: 0 server connects that finished 2005.03.24 15:04:11 LOG7[3392:2556]: 0 server renegotiatiations requested 2005.03.24 15:04:11 LOG7[3392:2556]: 0 session cache hits 2005.03.24 15:04:11 LOG7[3392:2556]: 0 session cache misses 2005.03.24 15:04:11 LOG7[3392:2556]: 0 session cache timeouts 2005.03.24 15:04:11 LOG6[3392:2556]: SSL connected: new session negotiated 2005.03.24 15:04:11 LOG6[3392:2556]: Negotiated ciphers: AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 2005.03.24 15:04:27 LOG7[3392:2556]: SSL alert (write): fatal: bad record mac 2005.03.24 15:04:27 LOG3[3392:2556]: SSL_read: 1408F455: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac 2005.03.24 15:04:27 LOG5[3392:2556]: Connection reset: 17 bytes sent to SSL, 191 bytes sent to socket 2005.03.24 15:04:27 LOG7[3392:2556]: telnet finished (0 left) =============================================================================== How can I procede? Thanks&Regards Maddalena

2 1

Proxy support with stunnel
by Andrei Emeltchenko 24 Mar '05

24 Mar '05

Hi! I am new to stunnel and just wanted to check is there possibility to use proxy? Assume I want to connect to secure news with NNTPS. I need something like ProxyCommand in ssh. Regards, Andrei

1 0

help
by Maddalena.Pulcini＠seleniacomms.com 24 Mar '05

24 Mar '05

Hi, someone could help me? I am using stunnel (4.07) as ssl client to do telnet to my router with ssl server (openssl 0.9.7d). After protocol handshake I get this error: SSL_read: 1408F455: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac problem Stunnel is configured in this way: ========================== client = yes debug=7 cert=clcert.pem [telnet] accept = 23 connect = 10.36.3.144:4433 ========================== My router's configuration is: ========================== -Verify 4 -cert cert.pem ========================== The exchange of packets: ========================== client sends=======> Client Hello server sends======> Server Hello,Certificate, Certificate Request,Server Hello Done client sends======> Certificate, Client Key Exchange, Certificate Verify, Change Cipher Spec, Encrypted Handshake Message server sends=====> Change Cipher Spec, Encrypted Handshake Message and then Application Data. After sending a number of Application Data by the server, client sends Encrypted Alert and closes the connection. Having debug on stunnel client I can see: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2005.03.15 11:13:44 LOG5[2040:3964]: stunnel 4.07 on x86-pc-mingw32-gnu WIN32+IPv6 with OpenSSL 0.9.8-dev XX xxx XXXX 2005.03.15 11:13:44 LOG7[2040:2376]: Snagged 64 random bytes from C:/.rnd 2005.03.15 11:13:44 LOG7[2040:2376]: Wrote 1024 new random bytes to C:/.rnd 2005.03.15 11:13:44 LOG7[2040:2376]: RAND_status claims sufficient entropy for the PRNG 2005.03.15 11:13:44 LOG6[2040:2376]: PRNG seeded successfully 2005.03.15 11:13:44 LOG7[2040:2376]: Certificate: clcert.pem 2005.03.15 11:13:44 LOG7[2040:2376]: Key file: clcert.pem 2005.03.15 11:13:44 LOG5[2040:2376]: No limit detected for the number of clients 2005.03.15 11:13:44 LOG7[2040:2376]: FD 188 in non-blocking mode 2005.03.15 11:13:44 LOG7[2040:2376]: SO_REUSEADDR option set on accept socket 2005.03.15 11:13:44 LOG7[2040:2376]: telnet bound to 0.0.0.0:23 2005.03.15 11:13:54 LOG7[2040:2376]: telnet accepted FD=192 from 127.0.0.1:1589 2005.03.15 11:13:54 LOG7[2040:2376]: FD 192 in non-blocking mode 2005.03.15 11:13:54 LOG7[2040:2376]: Creating a new thread 2005.03.15 11:13:54 LOG7[2040:2376]: New thread created 2005.03.15 11:13:54 LOG7[2040:3588]: telnet started 2005.03.15 11:13:54 LOG5[2040:3588]: telnet connected from 127.0.0.1:1589 2005.03.15 11:13:54 LOG7[2040:3588]: FD 224 in non-blocking mode 2005.03.15 11:13:54 LOG7[2040:3588]: telnet connecting 10.36.3.144:4433 2005.03.15 11:13:54 LOG7[2040:3588]: connect_wait: waiting 10 seconds 2005.03.15 11:13:54 LOG7[2040:3588]: connect_wait: connected 2005.03.15 11:13:54 LOG7[2040:3588]: Remote FD=224 initialized 2005.03.15 11:13:54 LOG7[2040:3588]: SSL state (connect): before/connect initialization 2005.03.15 11:13:55 LOG7[2040:3588]: SSL state (connect): SSLv3 write client hello A 2005.03.15 11:13:55 LOG7[2040:3588]: SSL state (connect): SSLv3 read server hello A 2005.03.15 11:13:55 LOG7[2040:3588]: SSL state (connect): SSLv3 read server certificate A 2005.03.15 11:13:55 LOG7[2040:3588]: SSL state (connect): SSLv3 read server certificate request A 2005.03.15 11:13:55 LOG7[2040:3588]: SSL state (connect): SSLv3 read server done A 2005.03.15 11:13:55 LOG7[2040:3588]: SSL state (connect): SSLv3 write client certificate A 2005.03.15 11:13:55 LOG7[2040:3588]: SSL state (connect): SSLv3 write client key exchange A 2005.03.15 11:13:55 LOG7[2040:3588]: SSL state (connect): SSLv3 write certificate verify A 2005.03.15 11:13:55 LOG7[2040:3588]: SSL state (connect): SSLv3 write change cipher spec A 2005.03.15 11:13:55 LOG7[2040:3588]: SSL state (connect): SSLv3 write finished A 2005.03.15 11:13:55 LOG7[2040:3588]: SSL state (connect): SSLv3 flush data 2005.03.15 11:14:26 LOG7[2040:3588]: SSL state (connect): SSLv3 read finished A 2005.03.15 11:14:26 LOG7[2040:3588]: 1 items in the session cache 2005.03.15 11:14:26 LOG7[2040:3588]: 1 client connects (SSL_connect()) 2005.03.15 11:14:26 LOG7[2040:3588]: 1 client connects that finished 2005.03.15 11:14:26 LOG7[2040:3588]: 0 client renegotiatations requested 2005.03.15 11:14:26 LOG7[2040:3588]: 0 server connects (SSL_accept()) 2005.03.15 11:14:26 LOG7[2040:3588]: 0 server connects that finished 2005.03.15 11:14:26 LOG7[2040:3588]: 0 server renegotiatiations requested 2005.03.15 11:14:26 LOG7[2040:3588]: 0 session cache hits 2005.03.15 11:14:26 LOG7[2040:3588]: 0 session cache misses 2005.03.15 11:14:26 LOG7[2040:3588]: 0 session cache timeouts 2005.03.15 11:14:26 LOG6[2040:3588]: SSL connected: new session negotiated 2005.03.15 11:14:26 LOG6[2040:3588]: Negotiated ciphers: AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 2005.03.15 11:14:41 LOG7[2040:3588]: SSL alert (write): fatal: bad record mac 2005.03.15 11:14:41 LOG3[2040:3588]: SSL_read: 1408F455: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac 2005.03.15 11:14:41 LOG5[2040:3588]: Connection reset: 17 bytes sent to SSL, 190 bytes sent to socket 2005.03.15 11:14:41 LOG7[2040:3588]: telnet finished (0 left) >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This client is now running using an updated library: libeay32.dll obtained compiling openssl-SNAP-20050304 that seemed to be the solution of the problem (after searching on Internet I deduce that). Not having solution to the problem, I know that my conclusion is not right. This morning I tryed with new library available in your home page (New compiled Windows DLL libraries for 0.9.7d) but I get the same error. So if someone knows how to procede, please help me. Thanks&Regards Maddalena Pulcini

3 2

Problems using STunnel with a non-default port - Please Help
by Chetan Rao 22 Mar '05

22 Mar '05

I have a personal webserver running on Win2K Pro SP4 that listens on port 17875. This server is accessible through my NAT and software firewall (ZoneAlarm Pro). I then installed STunnel with the following conf: [https] accept=4430 connect=17875 TIMEOUTclose=0 Now, when I access https://<server>:4430, I get a HTTP 400 (Bad Request) error message, with both Internet Explorer 6 and FireFox 1.01. However, if I change the accept port from 4430 to 443 (and make the appropriate changes on the NAT for port forwarding), and use https://<server>, it works. I don't want to use the standard port. What am I doing wrong? Here's the log that STunnel generated: 2005.03.16 08:33:26 LOG5[1044:288]: stunnel 4.08 on x86-pc-mingw32-gnu WIN32+IPv4 with OpenSSL 0.9.7e 25 Oct 2004 2005.03.16 08:33:26 LOG7[1044:1096]: RAND_status claims sufficient entropy for the PRNG 2005.03.16 08:33:26 LOG6[1044:1096]: PRNG seeded successfully 2005.03.16 08:33:26 LOG7[1044:1096]: Certificate: stunnel.pem 2005.03.16 08:33:26 LOG7[1044:1096]: Key file: stunnel.pem 2005.03.16 08:33:26 LOG5[1044:1096]: No limit detected for the number of clients 2005.03.16 08:33:26 LOG7[1044:1096]: FD 168 in non-blocking mode 2005.03.16 08:33:26 LOG7[1044:1096]: SO_REUSEADDR option set on accept socket 2005.03.16 08:33:26 LOG7[1044:1096]: https bound to 0.0.0.0:4430 2005.03.16 08:34:08 LOG7[1044:1096]: https accepted FD=180 from 192.168.0.2:4864 2005.03.16 08:34:08 LOG7[1044:1096]: FD 180 in non-blocking mode 2005.03.16 08:34:08 LOG7[1044:1096]: Creating a new thread 2005.03.16 08:34:08 LOG7[1044:1096]: New thread created 2005.03.16 08:34:08 LOG7[1044:896]: https started 2005.03.16 08:34:08 LOG5[1044:896]: https connected from 192.168.0.2:4864 2005.03.16 08:34:08 LOG7[1044:896]: SSL state (accept): before/accept initialization 2005.03.16 08:34:08 LOG7[1044:896]: SSL state (accept): SSLv3 read client hello A 2005.03.16 08:34:08 LOG7[1044:896]: SSL state (accept): SSLv3 write server hello A 2005.03.16 08:34:08 LOG7[1044:896]: SSL state (accept): SSLv3 write certificate A 2005.03.16 08:34:08 LOG7[1044:896]: SSL state (accept): SSLv3 write server done A 2005.03.16 08:34:08 LOG7[1044:896]: SSL state (accept): SSLv3 flush data 2005.03.16 08:34:08 LOG7[1044:896]: SSL state (accept): SSLv3 read client key exchange A 2005.03.16 08:34:08 LOG7[1044:896]: SSL state (accept): SSLv3 read finished A 2005.03.16 08:34:08 LOG7[1044:896]: SSL state (accept): SSLv3 write change cipher spec A 2005.03.16 08:34:08 LOG7[1044:896]: SSL state (accept): SSLv3 write finished A 2005.03.16 08:34:08 LOG7[1044:896]: SSL state (accept): SSLv3 flush data 2005.03.16 08:34:08 LOG7[1044:896]: 1 items in the session cache 2005.03.16 08:34:08 LOG7[1044:896]: 0 client connects (SSL_connect()) 2005.03.16 08:34:08 LOG7[1044:896]: 0 client connects that finished 2005.03.16 08:34:08 LOG7[1044:896]: 0 client renegotiatations requested 2005.03.16 08:34:08 LOG7[1044:896]: 1 server connects (SSL_accept()) 2005.03.16 08:34:08 LOG7[1044:896]: 1 server connects that finished 2005.03.16 08:34:08 LOG7[1044:896]: 0 server renegotiatiations requested 2005.03.16 08:34:08 LOG7[1044:896]: 0 session cache hits 2005.03.16 08:34:08 LOG7[1044:896]: 1 session cache misses 2005.03.16 08:34:08 LOG7[1044:896]: 0 session cache timeouts 2005.03.16 08:34:08 LOG6[1044:896]: SSL accepted: new session negotiated 2005.03.16 08:34:08 LOG6[1044:896]: Negotiated ciphers: RC4-MD5 SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 2005.03.16 08:34:08 LOG7[1044:896]: FD 200 in non-blocking mode 2005.03.16 08:34:08 LOG7[1044:896]: https connecting 127.0.0.1:17875 2005.03.16 08:34:08 LOG7[1044:896]: connect_wait: waiting 10 seconds 2005.03.16 08:34:08 LOG7[1044:896]: connect_wait: connected 2005.03.16 08:34:08 LOG7[1044:896]: Remote FD=200 initialized 2005.03.16 08:34:08 LOG7[1044:896]: Socket closed on read 2005.03.16 08:34:08 LOG7[1044:896]: SSL write shutdown 2005.03.16 08:34:08 LOG7[1044:896]: SSL alert (write): warning: close notify 2005.03.16 08:34:08 LOG7[1044:896]: SSL_shutdown retrying 2005.03.16 08:34:08 LOG7[1044:896]: s_poll_wait timeout waiting for SSL close_notify 2005.03.16 08:34:08 LOG5[1044:896]: Connection closed: 208 bytes sent to SSL, 389 bytes sent to socket 2005.03.16 08:34:08 LOG7[1044:896]: https finished (0 left) Any help much appreciated. Thanks.

2 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

stunnel-users