stunnel-users

3 participants
3308 discussions

Patch to fix: Wildcard SSL certificates + SNI broken on Firefox
by Stephen Balukoff 28 Nov '12

28 Nov '12

Hello! I noticed that when dealing with wildcard certs in stunnel where an SNI configuration is being used, unless a specific servername context that exactly matches the browser's requested servername is in the stunnel.conf, stunnel responds to the client (web browser in this case) with a SSL_TLSEXT_ERR_ALERT_FATAL. Most browsers fall back to a non-SNI request, at which point, stunnel responds with whatever the master service's certificate is (which, if it's a wildcard cert, just works). However, at least one popularly-used web browser (Firefox) does not do this, and instead returns an error message to the user which they cannot (and should not need to) override to view the site contents. Since it's impractical to list all the possible servernames that can match at wildcard cert, and it's also impractical to expect the Firefox developers to change the behavior of their browser (when they shouldn't have to), and even more impractical to expect all the current users of Firefox to upgrade in a timely manner... I went ahead and wrote a patch for stunnel which instructs it to look for a matching wildcard certificate, if an exactly-matching servername isn't found. I've attached this patch to this message. Beyond fixing the stunnel+wildcard cert+SNI+firefox problem above, the secondary benefits of this patch are: * stunnel now responds immediately with a matching cert in the case of a wildcard cert, thus eliminating that first exchange which results in the SSL_TLSEXT_ERR_ALERT_FATAL error above. For stupid browsers and configurations with keepalive turned off + lots of requests per page and high latency, this should help to significantly improve performance. * stunnel will still choose an exactly matching cert if it's available and configured. (ie. if the browser requests 'subdomain.example.com', and there's a certificate configured in stunnel for 'subdomain.example.com' and another for '*.example.com', stunnel will respond with the ' subdomain.example.com' cert.) * one can now use multiple wildcard certs on a single IP:Port combination thanks to SNI. (Without this patch, you can effectively only use one wildcard cert per IP:Port combination with stunnel.) One note: It's been years since I've written any C code, so can't really vouch for the quality of my patch. I'm hoping at least the maintainers of this project see the utility of the patch I'm providing and write something similar in non-stupid C. Thanks, Stephen -- Stephen Balukoff Blue Box Group, LLC (800)613-4305 x807

1 0

Question : prevent close-nofity alerts from stunnel-server
by bhakta79 28 Nov '12

28 Nov '12

Hello, I was trying MITM on a windows application (which talks to a M$ server). Stunnel was running on my windows xp machine. windows-client-app -> stunnel server ---> stunnel client --> M$ Server What I found is that stunnel server sends close notify alert to the windows client app which causes the client to suspend all further communication (busted windows-client of course!). I tried setting the TimeoutClose option to high values but I always saw the server sending close notify alert (is the timeout close only a client-side parameter?) Is there a way to configure server to not send close notify? stullen logs: 2012.11.28 18:32:12 LOG7[3908:5904]: SSL socket closed on SSL_read 2012.11.28 18:32:12 LOG7[3908:5904]: Sent socket write shutdown 2012.11.28 18:32:12 LOG7[3908:4232]: Socket closed on read 2012.11.28 18:32:12 LOG5[3908:5904]: Connection closed: 901 byte(s) sent to SSL, 38020 byte(s) sent to socket 2012.11.28 18:32:12 LOG7[3908:4232]: Sending close_notify alert 2012.11.28 18:32:12 LOG7[3908:4232]: SSL alert (write): warning: close notify 2012.11.28 18:32:12 LOG6[3908:4232]: SSL_shutdown successfully sent close_notify alert 2012.11.28 18:32:12 LOG7[3908:5904]: Remote socket (FD=356) closed <mailto:[email protected]> I finally ended up making this one line code-change to stop server from sending close alert that helped my MITM progress. src/client.c: if(!(SSL_get_shutdown(c->ssl)&SSL_SENT_SHUTDOWN) && !sock_open_rd && !c->sock_ptr) { s_log(LOG_DEBUG, "BHAKTA - HACK -> Skip Sending close_notify alert"); *! if(0 && SSL_version(c->ssl)!=SSL2_VERSION) { /* SSLv3, TLSv1 */* s_log(LOG_DEBUG, "Sending close_notify alert"); shutdown_wants_write=1; } else { /* no alerts in SSLv2, including the close_notify alert */ s_log(LOG_DEBUG, "Closing SSLv2 socket"); if(c->ssl_rfd->is_socket) shutdown(c->ssl_rfd->fd, SHUT_RD); /* notify the kernel */ if(c->ssl_wfd->is_socket) shutdown(c->ssl_wfd->fd, SHUT_WR); /* send TCP FIN */ /* notify the OpenSSL library */ SSL_set_shutdown(c->ssl, SSL_SENT_SHUTDOWN|SSL_RECEIVED_SHUTDOWN); } } Is there a way to prevent server from sending close notify alert by means of stunel.conf parameters? stunnel.conf: debug = 7 output = stunnel.log cert = fakecert.pem key = fakecert.key options = DONT_INSERT_EMPTY_FRAGMENTS socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 [https] sslVersion = TLSv1 accept = 0.0.0.0:443 connect = 127.0.0.1:446 [https-client] client = yes sslVersion = TLSv1 accept = 127.0.0.1:446 connect = 172.24.244.11:443 TIMEOUTclose = 300

1 0

Re: [stunnel-users] WinCE link errors
by Bao, Robert 28 Nov '12

28 Nov '12

Brian, You are right. After changing the order, all wcecompatex.lib related link errors are gone! Thanks a lot. Also thank Pierre for dropping me another suggestion. Mike, When you get chance to update next time, you may consider changing this line (in evc.mak): From: LIBS=/NODEFAULTLIB coredll.lib corelibc.lib winsock.lib wcecompatex.lib libeay32.lib ssleay32.lib To: LIBS=/NODEFAULTLIB winsock.lib wcecompatex.lib libeay32.lib ssleay32.lib coredll.lib corelibc.lib Thank you all. Robert From: Brian Wilkins [mailto:[email protected]] Sent: Wednesday, November 28, 2012 5:15 PM To: Bao, Robert Subject: Re: [stunnel-users] WinCE link errors Maybe try changing the link order...? On Nov 28, 2012 5:10 PM, "Bao, Robert" <rbao(a)tycoint.com> wrote: Dear Mike and WinCE stunnel users out there, I am currently in the process of compiling/linking the latest stunnel (4.54) for our ARM and WinCE 5.0 based device. I noticed that this version requires coredll.lib and corelibc.lib in the final link process (defined in the LIBS variable), which the old ones (e.g., version 4.33) didn't. Anyway, I got a lot of linking errors (see below), and just wondering any of you have seen the same errors and how you get around with these errors. If you have any other suggestions please feel free to let me know too. Note: I could resolve the errors at the bottom, but I have trouble get rid of the errors relating to wcecompatex.lib(redir.obj). Thank you for your time. wcecompatex.lib(redir.obj) : error LNK2005: fopen already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: fclose already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: fread already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: fwrite already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: _getstdfilex already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: _fileno already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: fflush already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: feof already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: ferror already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: clearerr already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: fseek already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: ftell already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: _setmode already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: fgets already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: fprintf already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : warning LNK4006: fopen already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: fclose already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: fread already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: fwrite already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: _getstdfilex already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: _fileno already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: fflush already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: feof already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: ferror already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: clearerr already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: fseek already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: ftell already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: _setmode already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: fgets already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: fprintf already defined in coredll.lib(COREDLL.dll); second definition ignored Creating library ..\bin\ARMV4I\tstunnel.lib and object ..\bin\ARMV4I\tstunnel.exp options.obj : error LNK2001: unresolved external symbol WSAGetLastError network.obj : error LNK2001: unresolved external symbol WSAGetLastError stunnel.obj : error LNK2019: unresolved external symbol WSAGetLastError referenced in function daemon_loop ctx.obj : error LNK2001: unresolved external symbol WSAGetLastError client.obj : error LNK2019: unresolved external symbol WSAGetLastError referenced in function init_remote log.obj : error LNK2001: unresolved external symbol WSAGetLastError client.obj : error LNK2019: unresolved external symbol hwnd referenced in function win_new_chain log.obj : error LNK2019: unresolved external symbol hwnd referenced in function s_strerror options.obj : error LNK2001: unresolved external symbol hwnd log.obj : error LNK2019: unresolved external symbol WSASetLastError referenced in function s_log nogui.obj : error LNK2019: unresolved external symbol main_execute referenced in function main ..\bin\ARMV4I\tstunnel.exe : fatal error LNK1120: 4 unresolved externals NMAKE : fatal error U1077: 'link' : return code '0x460' Robert Bao Software House Tyco International 978-577-4202 Explore our new Tyco Online Learning Center Web-based Training Bundles at: www.swhouse.com/support/tyco_online_learning_center.aspx This e-mail may contain or have attached to it information or technology the export or re-export of which is restricted by U.S. laws and regulations. By viewing this e-mail and any attachments, the recipient agrees to the following: (i) the recipients use of the contents of this e-mail and any attachments shall comply with all applicable laws, rules and regulations, including, without limitation, U.S. international trade laws and regulations, and (ii) the recipient may not transfer or otherwise export or re-export any information or technology contained in this e-mail or any attachment except in full compliance with the export controls administered by the U.S. and other countries and any applicable import and use restrictions. _______________________________________________ stunnel-users mailing list stunnel-users(a)stunnel.org https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users

1 0

WinCE link errors
by Bao, Robert 28 Nov '12

28 Nov '12

Dear Mike and WinCE stunnel users out there, I am currently in the process of compiling/linking the latest stunnel (4.54) for our ARM and WinCE 5.0 based device. I noticed that this version requires coredll.lib and corelibc.lib in the final link process (defined in the LIBS variable), which the old ones (e.g., version 4.33) didn't. Anyway, I got a lot of linking errors (see below), and just wondering any of you have seen the same errors and how you get around with these errors. If you have any other suggestions please feel free to let me know too. Note: I could resolve the errors at the bottom, but I have trouble get rid of the errors relating to wcecompatex.lib(redir.obj). Thank you for your time. wcecompatex.lib(redir.obj) : error LNK2005: fopen already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: fclose already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: fread already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: fwrite already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: _getstdfilex already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: _fileno already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: fflush already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: feof already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: ferror already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: clearerr already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: fseek already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: ftell already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: _setmode already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: fgets already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : error LNK2005: fprintf already defined in coredll.lib(COREDLL.dll) wcecompatex.lib(redir.obj) : warning LNK4006: fopen already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: fclose already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: fread already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: fwrite already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: _getstdfilex already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: _fileno already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: fflush already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: feof already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: ferror already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: clearerr already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: fseek already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: ftell already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: _setmode already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: fgets already defined in coredll.lib(COREDLL.dll); second definition ignored wcecompatex.lib(redir.obj) : warning LNK4006: fprintf already defined in coredll.lib(COREDLL.dll); second definition ignored Creating library ..\bin\ARMV4I\tstunnel.lib and object ..\bin\ARMV4I\tstunnel.exp options.obj : error LNK2001: unresolved external symbol WSAGetLastError network.obj : error LNK2001: unresolved external symbol WSAGetLastError stunnel.obj : error LNK2019: unresolved external symbol WSAGetLastError referenced in function daemon_loop ctx.obj : error LNK2001: unresolved external symbol WSAGetLastError client.obj : error LNK2019: unresolved external symbol WSAGetLastError referenced in function init_remote log.obj : error LNK2001: unresolved external symbol WSAGetLastError client.obj : error LNK2019: unresolved external symbol hwnd referenced in function win_new_chain log.obj : error LNK2019: unresolved external symbol hwnd referenced in function s_strerror options.obj : error LNK2001: unresolved external symbol hwnd log.obj : error LNK2019: unresolved external symbol WSASetLastError referenced in function s_log nogui.obj : error LNK2019: unresolved external symbol main_execute referenced in function main ..\bin\ARMV4I\tstunnel.exe : fatal error LNK1120: 4 unresolved externals NMAKE : fatal error U1077: 'link' : return code '0x460' Robert Bao Software House Tyco International 978-577-4202 Explore our new Tyco Online Learning Center Web-based Training Bundles at: www.swhouse.com/support/tyco_online_learning_center.aspx This e-mail may contain or have attached to it information or technology the export or re-export of which is restricted by U.S. laws and regulations. By viewing this e-mail and any attachments, the recipient agrees to the following: (i) the recipients use of the contents of this e-mail and any attachments shall comply with all applicable laws, rules and regulations, including, without limitation, U.S. international trade laws and regulations, and (ii) the recipient may not transfer or otherwise export or re-export any information or technology contained in this e-mail or any attachment except in full compliance with the export controls administered by the U.S. and other countries and any applicable import and use restrictions.

2 1

equivalent to SSLHonorcipherorder in stunnel?
by Mehdi Bennani 28 Nov '12

28 Nov '12

Hi, I was wondering if there were a flag available in stunnel, that would be the equivalent of the Apache directive 'SSLHonorcipherorder' ? I would like to basically be able to 'force' server preferences, rather then client ones, during cipher negotiation SSL handshake. Thank you, Elextra-

2 1

Max Cookie Size
by Scott McKeown 20 Nov '12

20 Nov '12

Hi All, I was wondering if anyone knows if its possible to pass a 'really' large cookie through STunnel. I've just built the latest version again (output below). However, we have a client that is looking to pass 16Kb (yes I know please don't tell me this is a bad idea a I know this!) via a cookie. Since we are looking to include STunnel in our offerings I was wondering if we could increase or change the maximum allowed size. I have a script that will generate a test cookie of any size that I require to test with but I can only get an 8K cookie to work. Any help would be great. ~Yours, Scott [root@localhost ~]# stunnel -version stunnel 4.54 on x86_64-unknown-linux-gnu platform Compiled/running with OpenSSL 1.0.0-fips 29 Mar 2010 Threading:PTHREAD SSL:+ENGINE+OCSP+FIPS Auth:none Sockets:POLL+IPv6 Global options: debug = daemon.notice pid = /usr/local/var/run/stunnel/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes Service-level options: ciphers = FIPS (with "fips = yes") ciphers = ALL:!SSLv2:!aNULL:!EXP:!LOW:-MEDIUM:RC4:+HIGH (with "fips = no") sessionCacheSize = 1000 sessionCacheTimeout = 300 seconds sslVersion = TLSv1 (with "fips = yes") sslVersion = TLSv1 for client, all for server (with "fips = no") stack = 65536 bytes TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds verify = none [root@localhost ~]# -- With Kind Regards. Scott McKeown Loadbalancer.org http://www.loadbalancer.org

2 2

Problem using stunnel on Windows 7
by Hal Hovland 18 Nov '12

18 Nov '12

I've spent days googling this and read everything relevant in the archives. I'm developing a Windows 7 program that connects to a financial trading exchange that expects all communication to be SSL'd. Everything I read said that stunnel is the answer because of ease of installation and use. After a day of abortive attempts to link to the exchange, I decided to create a much simpler test environment involving two Windows 7 computers next to each other here. One, let's call it Riven-II (192.168.1.9), is set up with a simple Listener program that listens on port 8000. From stunnel's viewpoint this will be a server. The second machine, Lightning (192.168.1.158), has a simple Sender program that sends a text message via port 7999 to Riven-II (192.168.1.9:8000) - this will be the Client. In the absence of stunnel, all messages sent from Lightning/Sender appears on the window of Listener. So far so good. I've downloaded and installed the very latest version (4.54) of stunnel on both machines. On installation I entered the same responses to the certificate generating process. On the Server machine, hard wired to a Broadband Router, I configured stunnel.conf as (removing comments for simplicity) debug = 7 output = stunnel.log socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 cert = stunnel.pem key = stunnel.pem options = NO_SSLv2 taskbar=yes [Listener] connect=8000 accept=8001 On the Client machine, connected to the router via wi-fi, we have in stunnel.conf debug = 7 output = stunnel.log cert = stunnel.pem socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 fips=no options = NO_SSLv2 delay=yes taskbar=yes client=yes [sender] accept = 0.0.0.0:7999 (I've tried just 7999 and 192.168.1.158:7999, here. Makes no difference) connect = 192.168.1.9:8001 I've tried many variations with the same result, but the above is where they have ended up. My understanding of this is that stunnel both ends will be intercepting port 8000 on the Server and port 7999 on the Client and presenting/receiving SSL encoded messages across the wire on port 8001. Starting stunnel in the Server (not as a Windows service, although I did try that as well) the following log appears: 2012.11.16 22:34:08 LOG7[3484:6184]: No limit detected for the number of clients 2012.11.16 22:34:08 LOG5[3484:6184]: stunnel 4.54 on x86-pc-msvc-1500 platform 2012.11.16 22:34:08 LOG5[3484:6184]: Compiled/running with OpenSSL 1.0.1c-fips 10 May 2012 2012.11.16 22:34:08 LOG5[3484:6184]: Threading:WIN32 SSL:+ENGINE+OCSP+FIPS Auth:none Sockets:SELECT+IPv6 2012.11.16 22:34:08 LOG5[3484:6184]: Reading configuration from file stunnel.conf 2012.11.16 22:34:08 LOG5[3484:6184]: FIPS mode is enabled 2012.11.16 22:34:08 LOG7[3484:6184]: Compression not enabled 2012.11.16 22:34:08 LOG7[3484:6184]: Snagged 64 random bytes from C:/.rnd 2012.11.16 22:34:08 LOG7[3484:6184]: Wrote 1024 new random bytes to C:/.rnd 2012.11.16 22:34:08 LOG7[3484:6184]: PRNG seeded successfully 2012.11.16 22:34:08 LOG6[3484:6184]: Initializing service [Listener] 2012.11.16 22:34:08 LOG7[3484:6184]: Certificate: stunnel.pem 2012.11.16 22:34:08 LOG7[3484:6184]: Certificate loaded 2012.11.16 22:34:08 LOG7[3484:6184]: Key file: stunnel.pem 2012.11.16 22:34:08 LOG7[3484:6184]: Private key loaded 2012.11.16 22:34:08 LOG7[3484:6184]: Could not load DH parameters from stunnel.pem 2012.11.16 22:34:08 LOG7[3484:6184]: Using hardcoded DH parameters 2012.11.16 22:34:08 LOG7[3484:6184]: DH initialized with 2048-bit key 2012.11.16 22:34:08 LOG7[3484:6184]: ECDH initialized with curve prime256v1 2012.11.16 22:34:08 LOG7[3484:6184]: SSL options set: 0x01000004 2012.11.16 22:34:08 LOG5[3484:6184]: Configuration successful 2012.11.16 22:34:08 LOG7[3484:6184]: Service [Listener] (FD=272) bound to 0.0.0.0:8001 On the Client, the log shows: 2012.11.16 22:25:53 LOG7[4184:4948]: No limit detected for the number of clients 2012.11.16 22:25:53 LOG5[4184:4948]: stunnel 4.54 on x86-pc-msvc-1500 platform 2012.11.16 22:25:53 LOG5[4184:4948]: Compiled/running with OpenSSL 1.0.1c-fips 10 May 2012 2012.11.16 22:25:53 LOG5[4184:4948]: Threading:WIN32 SSL:+ENGINE+OCSP+FIPS Auth:none Sockets:SELECT+IPv6 2012.11.16 22:25:53 LOG5[4184:4948]: Reading configuration from file stunnel.conf 2012.11.16 22:25:53 LOG5[4184:4948]: FIPS mode is disabled 2012.11.16 22:25:53 LOG7[4184:4948]: Compression not enabled 2012.11.16 22:25:53 LOG7[4184:4948]: Snagged 64 random bytes from C:/.rnd 2012.11.16 22:25:53 LOG7[4184:4948]: Wrote 1024 new random bytes to C:/.rnd 2012.11.16 22:25:53 LOG7[4184:4948]: PRNG seeded successfully 2012.11.16 22:25:53 LOG6[4184:4948]: Initializing service [sender] 2012.11.16 22:25:53 LOG7[4184:4948]: Certificate: stunnel.pem 2012.11.16 22:25:53 LOG7[4184:4948]: Certificate loaded 2012.11.16 22:25:53 LOG7[4184:4948]: Key file: stunnel.pem 2012.11.16 22:25:53 LOG7[4184:4948]: Private key loaded 2012.11.16 22:25:53 LOG7[4184:4948]: SSL options set: 0x01000004 2012.11.16 22:25:53 LOG5[4184:4948]: Configuration successful 2012.11.16 22:25:53 LOG7[4184:4948]: Service [sender] (FD=224) bound to 0.0.0.0:7999 Running the Listener on the Server and Sender on the Client adds nothing to the log, and port sniffers on both machines show traffic between 7999 and 8000 (exactly the same as when stunnel is not running). No sign of the use of port 8001. I'd appreciate any input on this. I'm sure I must be doing something stupid, but I've watched hours of YouTube videos, read many hundreds of web pages, and been through the documentation quite a few times, to no avail. I have a Java based version, running in a JVM in the same Windows machines, that talks perfectly to the exchange using some inbuilt SSL capabilities of an included library, so that should probably eliminate any hardware/router issues? Regards, Hal

4 10

log rotation
by Michael Curran 11 Nov '12

11 Nov '12

Are there any built in stunnel.conf parameters for log rotation? Im looking for windows based -- not logrotate on unix -- thats simple Do I need to use windows third party logrotate tools to make this happen instead?

2 1

High memory usage problem.
by Jeremy Frady 11 Nov '12

11 Nov '12

Thanks for taking the time to read this. We're operating on a low spec system that can not be modified at this point. stunnel was introduced at the last minute, without consideration to resource requirements and now consumes enough ram to cause the kernel to issue OOM exceptions. So in short, we are trying to trade increased CPU usage for less memory usage and have tried setting “sessions” to 3600 to reduce memory pressure, but unfortunately it doesn't last. Our current solution is to cron a restart of stunnel on a regular basis, but would prefer to limit number of threads or number of cache entries or something else altogether similarly gentler. Thanks again for your consideration and assistance in this! If there's any specific information I can give, please let me know. Regards, Jeremy

2 1

How do I re-encrypt ssl traffic with stunel?
by Arsen Zahray 11 Nov '12

11 Nov '12

I'm trying to set up wireshark debugging of ssl traffic by following this article: http://www.webos-internals.org/wiki/Decrypt_SSL_(trusted_man-in-the-middle_t echnique) It lists following stunnel commands to do the job: Listen on local IP and de-SSL traffic to localhost:8080 sudo stunnel -p ps.pem -d 443 -r 8080 Listen on 8080, re-SSL to remote server on 443 sudo stunnel -c -d 8080 -r ps.palmws.com:443 The article seems outdated, and stunnel does not react on these commands anymore. Can anyone provide me with a proper configuration file to do the same?

3 2

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