- stunnel-users - stunnel.org

Inconsistent performance across stunnel and/or OpenSSL versions
by PPingPongBaker PPingPongBaker 23 Apr '13

23 Apr '13

Hi All, I am experimenting with stunnel inside a VM on Xenserver 6.02. So this may not be a "common" use case, nonetheless, I would like to point out the issue. It is a basic setup as follows with 3 VMs running "ab" for webclient, stunnel+haproxy combo as the https/http bridge and nginx as the webserver. client VM (ab) <-> stunnel + haproxy VM <-> webserver VM (nginx) Specs on the stunnel VM are 2GB RAM, single-core dedicated 2.5 GHz Xeon E5-2640 vCPU, running Debian Squeeze 2.6.32-5-amd64 (64 bit) kernel. All things unchanged such as stunnel/haproxy/nginx config and taking care of common gotchas such as file descriptor limit, TIMEOUTclose, disabling libwrap, etc. stunnel is built with pthreads. Also stunnel is configured to use a 2K RSA self-signed certificate, and the client is being forced to do TLS1. "ab" is invoked with "-c 4" so as to peg the stunnel VM CPU (any value beyond 4 doesn't seem to matter). nginx serves a tiny 32 byte static html file. With stunnel 4.29 and OpenSSL 0.9.8o, I get 300 requests per second as max throughput. With stunnel 4.56 and OpenSSL 1.0.1e, I get only 40 requests per second as max throughput. tcpdump tells me that the Server Hello sent to the client takes a longer time in the latter case. Tinkering with TCP_NODELAY doesn't change anything. Anyone else seeing this maybe even on physical hardware? Has anything changed in OpenSSL across those versions? Suggestions? Thanks.

4 10

Windows Failover Clustering Support
by Cynthia Haselton 22 Apr '13

22 Apr '13

All, A (hopefully) quick question: Is stunnel supported on Windows Failover Clusters...specifically as a clustered service or to encrypt connections to/from a clustered IP? Thanks in advance, CJH

2 4

Customizing encryption
by John 19 Apr '13

19 Apr '13

HI guys, I need to take off SSL and use another encryption, need some hints since i'm new to stunnel. Thanks in advance,John

1 0

limited number of ports
by Terren Suydam 09 Apr '13

09 Apr '13

Hi, There appears to be a limit to the number of services you can define. Services beyond the 64th service appear to get set up without any log warnings or errors, yet don't pass traffic. The code uses select() & FD_SET to accept() an incoming connection & in Windows (using Windows Server 2008) the default is 64 sockets for that so wondering if I can just recompile, setting FD_SETSIZE to something larger. I'll try it either way, just wanted to put it out there to see if anyone else has ever run into this. Thanks, Terren

4 10

Trying to Upgrade stunnel, but compile isn't working?
by Michael D. Setzer II 03 Apr '13

03 Apr '13

I have been using stunnel for a long time, but was just trying to compile the latest version from source, and it compiles, but doesn't work like the older version, so I must have some option wrong. With the current version on my Fedora 14 machine using the latest version it loads the stunnel ports and works, but the newer version does seem to load or give an error message. I've tested the stunnel from Fedora 16 and Fedora 17, and they work fine with the stunnel.conf to load the settings. Current version info from Fedora 14 system. stunnel 4.34 on x86_64-redhat-linux-gnu with OpenSSL 1.0.0e-fips 6 Sep 2011 Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv6 Auth:LIBWRAP Global options debug = daemon.notice pid = /var/run/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes Service-level options cert = /etc/stunnel/stunnel.pem ciphers = ALL:!aNULL:!eNULL:!SSLv2 curve = sect163r2 session = 300 seconds stack = 65536 bytes sslVersion = SSLv3 for client, all for server TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds verify = none The new build does this. stunnel 4.56 on x86_64-unknown-linux-gnu platform Compiled/running with OpenSSL 1.0.0e-fips 6 Sep 2011 Threading:PTHREAD Sockets:POLL,IPv6 SSL:ENGINE,OCSP,FIPS 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 Have also tried it with --disable-fips With the new version I have to provide the /etc/stunnel/stunnel.conf, but it doesn't load any of the options. Sure it is just a simple configure setting I am missing. Thanks. +----------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor Guam Community College Computer Center mailto:mikes@kuentos.guam.net mailto:msetzerii@gmail.com http://www.guam.net/home/mikes Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +----------------------------------------------------------+ http://setiathome.berkeley.edu (Original) Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489) BOINC@HOME CREDITS SETI 14305761.074364 | EINSTEIN 10610832.119852 ROSETTA 6726167.419674 | ABC 15903532.519753

2 2

Log Rotation on Windows
by Brian Wilkins 03 Apr '13

03 Apr '13

I know that log rotation on Windows is on the TO-DO list. Is there a way to rotate the log at startup using some other means or during use? I suppose I could start stunnel with a batch file and do the log rotation before starting. Is there any other way? Brian

1 0

32/64 bit interposition on Solaris
by Norm Jacobs 29 Mar '13

29 Mar '13

I was recently working with stunnel on Solaris and ran across the following code in client.c: putenv("LD_PRELOAD=" LIBDIR "/libstunnel.so"); This appears to have been put in place to interpose a stunnel version of getpeername() on the downstream application. This works great when libstunnel.so has the same bittedness as the downstream application, but Solaris allows users to install and run both 32 and 64 bit applications on the same system. If the stunnel exectuable is a 32 bit application and the downstream application is a 64 bit application, the runtime linker falls over because of the mismatch with the interposed library. To avoid this problem, stunnel should use LD_PRELOAD_32 and LD_PRELOAD_64 on Solaris. I have put together a patch to client.c that sets both LD_PRELOAD_* environment variables to something that seems to make sense on Solaris, but have used a fairly hacky way of enabling it when I build. The client.c changes that I put together are: # On Solaris, fix stunnel so that the linker know where both the 32 and 64 bit # interposer libraries are. If you use LD_PRELOAD with the wrong bittedness # of interposer, the runtime linker hits a fatal error in trying to load # mismatched ELF objects. # diff -r -u stunnel-4.55.orig/src/client.c stunnel-4.55/src/client.c --- stunnel-4.55.orig/src/client.c 2013-02-28 00:17:58.000000000 -0800 +++ stunnel-4.55/src/client.c 2013-03-21 22:55:21.098479331 -0700 @@ -1096,9 +1096,14 @@ /* just don't set these variables if getnameinfo() fails */ putenv(str_printf("REMOTE_HOST=%s", host)); if(c->opt->option.transparent_src) { - putenv("LD_PRELOAD=" LIBDIR "/libstunnel.so"); - /* for Tru64 _RLD_LIST is used instead */ +#ifdef MACH64 + putenv("LD_PRELOAD_32=" LIBDIR "/libstunnel.so"); + putenv("LD_PRELOAD_64=" LIBDIR "/" MACH64 "/libstunnel.so"); +#elif __osf /* for Tru64 _RLD_LIST is used instead */ putenv("_RLD_LIST=" LIBDIR "/libstunnel.so:DEFAULT"); +#else + putenv("LD_PRELOAD=" LIBDIR "/libstunnel.so"); +#endif } } This adds more appropriate environment variables into the calling environment on Solaris. It still needs some work to integrate better with the build. Anyway, I thought that I would raise the issue and at least offer a direction to work from. I am happy to work with someone on a better resolution to this. -Norm

1 0

use of CRYPTO_NUM_LOCKS
by Norm Jacobs 29 Mar '13

29 Mar '13

A while ago, the Solaris security group noticed that stunnel uses CRYPTO_NUM_LOCKS to size a lock table in the code at compile time. They noted that there is function CRYPTO_num_locks() that can do the same thing at runtime and have requested that the function be used so that FIPS/non-FIPS support can be switched on by users simply using interposition. As a result of this, I put together this patch that switches to code to use the function instead of macro. -Norm # stunnel should use CRYPTO_num_locks() function instead of CRYPTO_NUM_LOCKS # macro. The function interogates libcrypto at run-time for sizing and the # macro at compile time. If you interpose a a version at runtime to switch # between FIPS/non-FIPS support, the lock table may not be sized correctly. # diff -r -u stunnel-4.55.orig/src/sthreads.c stunnel-4.55/src/sthreads.c --- stunnel-4.55.orig/src/sthreads.c 2012-08-09 14:44:18.000000000 -0700 +++ stunnel-4.55/src/sthreads.c 2013-03-21 23:29:34.912001586 -0700 @@ -212,7 +212,7 @@ #ifdef USE_PTHREAD static pthread_mutex_t stunnel_cs[CRIT_SECTIONS]; -static pthread_mutex_t lock_cs[CRYPTO_NUM_LOCKS]; +static pthread_mutex_t *lock_cs; void enter_critical_section(SECTION_CODE i) { pthread_mutex_lock(stunnel_cs+i); @@ -275,13 +275,15 @@ int sthreads_init(void) { int i; + int num_locks = CRYPTO_num_locks(); /* initialize stunnel critical sections */ for(i=0; i<CRIT_SECTIONS; i++) pthread_mutex_init(stunnel_cs+i, NULL); /* initialize OpenSSL locking callback */ - for(i=0; i<CRYPTO_NUM_LOCKS; i++) + lock_cs = calloc(num_locks, sizeof (*lock_cs)); + for(i=0; i<num_locks; i++) pthread_mutex_init(lock_cs+i, NULL); CRYPTO_set_id_callback(stunnel_thread_id); CRYPTO_set_locking_callback(locking_callback);

1 0

SSL VPN configuration confusion
by TJ 28 Mar '13

28 Mar '13

I'm using stunnel v4.56 on Linux (Ubuntu) and trying to configure a routed tunnel in conjunction with pppd. I could do with some help to figure it out - my biggest problem is not knowing what a good connection configuration or log looks like. I've read lots of (old) patchy articles on how it is done but the instructions are either hopelessly out of date, or plain wrong. During extensive trial and error I found what appeared to be bugs in the Ubuntu distro-packaged v4.42 but as I don't yet know what a successful connection log looks like they may have been red herrings. The main issue I was trying to build out of was (on the server): SSL accepted: new session negotiated Negotiated ciphers: ECDHE-RSA-RC4-SHA SSLv3 Kx=ECDH Au=RSA Enc=RC4(128) Mac=SHA1 TTY=/dev/pts/4 allocated Local mode child started (PID=17247) Remote FD=1 initialized TCP_NODELAY: Socket operation on non-socket (88) Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket linger (remote): Socket operation on non-socket (88) Service vpn finished (0 left) At this point there would be no pppX interfaces. I created an up-to-date Debian/Ubuntu package for v4.56 which has been more successful. Both ends of the link have the same x86 (i386) package installed. On the server again: stunnel: LOG6[23986:3073268544]: SSL accepted: new session negotiated stunnel: LOG6[23986:3073268544]: Negotiated TLSv1/SSLv3 ciphersuite: ECDHE-RSA-RC4-SHA (128-bit encryption) stunnel: LOG6[23986:3073268544]: Compression: null, expansion: null stunnel: LOG7[23986:3073268544]: TTY=/dev/pts/5 allocated stunnel: LOG6[23986:3073268544]: Local mode child started (PID=23989) stunnel: LOG7[23986:3073268544]: Remote socket (FD=14) initialized stunnel: LOG3[23986:3073268544]: TCP_NODELAY: Socket operation on non-socket (88) stunnel: LOG4[23986:3073268544]: Failed to set remote socket options pppd[23989]: pppd options in effect: pppd[23989]: debug^I^I# (from /etc/ppp/peers/pella-vpn) pppd[23989]: updetach^I^I# (from /etc/ppp/peers/pella-vpn) pppd[23989]: linkname pella^I^I# (from /etc/ppp/peers/pella-vpn) pppd[23989]: ktune^I^I# (from /etc/ppp/peers/pella-vpn) pppd[23989]: unit 3^I^I# (from /etc/ppp/peers/pella-vpn) pppd[23989]: dump^I^I# (from /etc/ppp/peers/pella-vpn) pppd[23989]: nomp^I^I# (from /etc/ppp/peers/pella-vpn) pppd[23989]: noauth^I^I# (from /etc/ppp/peers/pella-vpn) pppd[23989]: ^I^I# (from /etc/ppp/options) pppd[23989]: notty^I^I# (from /etc/ppp/peers/pella-vpn) pppd[23989]: crtscts^I^I# (from /etc/ppp/options) pppd[23989]: local^I^I# (from /etc/ppp/peers/pella-vpn) pppd[23989]: noaccomp^I^I# (from /etc/ppp/peers/pella-vpn) pppd[23989]: asyncmap 0^I^I# (from /etc/ppp/options) pppd[23989]: nopcomp^I^I# (from /etc/ppp/peers/pella-vpn) pppd[23989]: silent^I^I# (from /etc/ppp/peers/pella-vpn) pppd[23989]: lcp-echo-failure 4^I^I# (from /etc/ppp/options) pppd[23989]: lcp-echo-interval 30^I^I# (from /etc/ppp/options) pppd[23989]: hide-password^I^I# (from /etc/ppp/options) pppd[23989]: novj^I^I# (from /etc/ppp/peers/pella-vpn) pppd[23989]: noipdefault^I^I# (from /etc/ppp/peers/pella-vpn) pppd[23989]: noccp^I^I# (from /etc/ppp/peers/pella-vpn) pppd[23989]: noipx^I^I# (from /etc/ppp/options) pppd[23989]: pppd 2.4.5 started by root, uid 0 pppd[23989]: using channel 19 udevd[2122]: device 0xb7b0a6e8 has devpath '/devices/virtual/net/ppp3' udevd[2122]: created empty file '/run/udev/data/n27' for '/devices/virtual/net/ppp3' pppd[23989]: Using interface ppp3 pppd[23989]: Connect: ppp3 <--> /dev/pts/6 Both ends of the link have ppp interfaces but neither have IP addresses. The server configuration is: ----- /etc/stunnel/pella-vpn.conf ----- CAfile = /etc/stunnel/vpn.pem cert = /etc/stunnel/vpn.pem key = /etc/stunnel/vpn.pem output = /var/log/stunnel-vpn.log #verify = 2 debug = 7 client = no foreground = no [vpn] accept = 109.74.x.y:9876 exec = /usr/sbin/pppd execargs = pppd call pella-vpn 10.254.241.1:10.254.241.2 pty = yes ---------- ----- /etc/ppp/peers/pella-vpn ----- unit 3 notty ktune local noipdefault noccp noauth novj nomp nopcomp noaccomp silent updetach linkname pella debug dump ---------- # ifconfig ppp3 ppp3 Link encap:Point-to-Point Protocol POINTOPOINT NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) The client configuration is: ---- /etc/network/interfaces ----- # SSL VPN to Pella iface ppp3 inet ppp unit 3 provider pella-vpn pre-up /sbin/ifconfig ppp0 up ---------- ----- /etc/ppp/peers/pella-vpn ----- # ensure we use ppp3 (ppp0-2 are already in use) unit 3 ktune local noipdefault noccp noauth novj nomp nopcomp noaccomp silent updetach logfd 2 linkname pella pty "/usr/bin/stunnel4 /etc/stunnel/pella.conf.vpn" user "tj" # debugging debug dump ---------- ----- /etc/stunnel/pella.conf.vpn ----- pid = /var/run/stunnel4/pella.pid debug = debug output = /var/log/stunnel-pella.log foreground = no client=yes connect = 109.74.x.y:9876 CAfile = /etc/stunnel/vpn.pem # verify the peer's certificate verify = 2 ---------- # ifup ppp3 pppd options in effect: debug # (from /etc/ppp/peers/pella-vpn) updetach # (from command line) logfd 2 # (from /etc/ppp/peers/pella-vpn) linkname pella # (from /etc/ppp/peers/pella-vpn) ktune # (from /etc/ppp/peers/pella-vpn) unit 3 # (from command line) dump # (from /etc/ppp/peers/pella-vpn) nomp # (from /etc/ppp/peers/pella-vpn) noauth # (from /etc/ppp/peers/pella-vpn) user tj # (from /etc/ppp/peers/pella-vpn) # (from /etc/ppp/options) pty /usr/bin/stunnel4 /etc/stunnel/pella.conf.vpn # (from /etc/ppp/peers/pella-vpn) crtscts # (from /etc/ppp/options) local # (from /etc/ppp/peers/pella-vpn) noaccomp # (from /etc/ppp/peers/pella-vpn) asyncmap 0 # (from /etc/ppp/options) nopcomp # (from /etc/ppp/peers/pella-vpn) silent # (from /etc/ppp/peers/pella-vpn) lcp-echo-failure 4 # (from /etc/ppp/options) lcp-echo-interval 30 # (from /etc/ppp/options) hide-password # (from /etc/ppp/options) novj # (from /etc/ppp/peers/pella-vpn) noipdefault # (from /etc/ppp/peers/pella-vpn) noccp # (from /etc/ppp/peers/pella-vpn) noipx # (from /etc/ppp/options) using channel 43 Using interface ppp3 Connect: ppp3 <--> /dev/pts/5 # ifconfig ppp3 ppp3 Link encap:Point-to-Point Protocol POINTOPOINT NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) # netstat -natp | grep stun tcp 0 0 82.71.a.b:34437 109.74.x.y:9876 ESTABLISHED 24105/stunnel4

1 2

Fw: High memory usage problem.
by mkanet＠yahoo.com 27 Mar '13

27 Mar '13

Jeremy, I know there's an android build of stunnel. Im not trying to be funny, but are you running stunnel on your mobile phone? :) The latest android mobile phones include quadcore CPU's with 2GB's of RAM It would be interesting to see how much of a load a mobile phone can handle with a USB to RJ45 Ethernet interface. Edit: I tried sending this earlier, but it doesn't look like it went through. My apologies in case this is a duplicate. ------------------------ 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

3 7

environment/user variable
by Sebastian Rose-Indorf 26 Mar '13

26 Mar '13

Hello, Stunnel is a very helpful tool. But I miss the support of a environment/user variable to reference the configuration file or the folder of the configuration file: such as %GNUPGHOME% in GnuPG or %OPENSSL_CONF% in OpenSSL. Sebastian

1 0

the range of stunnel functionality
by John A. Wallace 26 Mar '13

26 Mar '13

Where can I find more information about the use and functionality of "tstunnel.exe"? Maybe I am going quite blind, but I looked around unsuccessfully. Thanks. John A. Wallace The pen is mightier than the sword, but only if you get in the first stroke.

3 3

stunnel 4.56 released
by Michal Trojnara 23 Mar '13

23 Mar '13

Dear Users, I have released version 4.56 of stunnel. The ChangeLog entry: Version 4.56, 2013.03.22, urgency: HIGH: * New features - Win32 installer automatically configures firewall exceptions. - Win32 installer configures administrative shortcuts to invoke UAC. - Improved Win32 GUI shutdown time. * Bugfixes - Fixed a regression bug introduced in version 4.55 causing random crashes on several platforms, including Windows 7. - Fixed startup crashes on some Win32 systems. - Fixed incorrect "stunnel -exit" process synchronisation. - Fixed FIPS detection with new versions of the OpenSSL library. - Failure to open the log file at startup is no longer ignored. Home page: https://www.stunnel.org/ Download: https://www.stunnel.org/downloads.html SHA-256 hash for stunnel-4.56.tar.gz: 9cae2cfbe26d87443398ce50d7d5db54e5ea363889d5d2ec8d2778a01c871293 Best regards, Mike

2 2

4.56 FIPS startup issue
by Ian Donaldson 23 Mar '13

23 Mar '13

Hi, I've been using stunnel for years and tried to upgrade to 4.56 today and it fails to start with this error: Clients allowed=125 stunnel 4.56 on i386-pc-solaris2.9 platform Compiled/running with OpenSSL 1.0.1e 11 Feb 2013 Threading:PTHREAD Sockets:POLL,IPv6 SSL:ENGINE,OCSP,FIPS Reading configuration from file /opt/local/etc/stunnel.conf FIPS_mode_set: F06D065: error:0F06D065:common libcrypto routines:FIPS_mode_set:fips mode not supported Line 36: "[pop3s]": Failed to initialize SSL str_stats: 5 block(s), 118 data byte(s), 210 control byte(s) I note some mention of FIPS in today's release. 4.55 started ok though with the same version of openssl (and crashed a few hours later), so we're back to 4.54 again. Ian D

1 1

stunnel craches in windows 7 x64
by Mosy Mosy 15 Mar '13

15 Mar '13

I have been facing with a strange bug in stunnel 4.55 (and also in tstunnel) in Windows 7 x64 and also in Windows Server 2003 R2 x86. I redirect TCP connections from a win7 client to a win2k3 server. Stunnel works fine when accepting connections and transferring data. But suddenly crashes when the client program (in the client side) closes the connection (maybe the several connections simultaneously). It happens on the server side too. Because of this problem I have to load a little program to relaunch stunnel whenever it is crashed. What I mean by 'crash' is that the windows shows the "stunnel stops working" and giving the choices to restart,stop, or debug the program. If you need more details I will be pleased to help you in this case. Thank you :) PS: I just have downloaded "stunnel-4.56b1" and I'm using it right now. I see no sign of crashing and instability until this moment :) it seems the bug is eliminated :)

1 0

4.55 is unstable
by Death Master 14 Mar '13

14 Mar '13

Windows build of 4.55, 2013.03.03 crashes every 20-60sec under load. OS:Win7 x64 (with all updates) This bug affects both stunnel and tstunnel. Please fix it soon ;)

5 6

stunnel: SSL routinesdecryption failed or bad record mac
by Kishore Paul 13 Mar '13

13 Mar '13

Hello Everyone, I updated to the latest version of stunnel and openssl and am still getting a lot of decryption fails. stunnel: SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac and a few times it just segfaults: [937987.314573] stunnel: segfault at 7f6164025000 ip 00007f616d8b5adc sp 00007f616e6a9af0 error 4 in libcrypto.so.1.0.0[7f616d84a000+19f000] stunnel 4.54 on x86_64-unknown-linux-gnu platform Compiled with OpenSSL 1.0.1e 11 Feb 2013 Running with OpenSSL 1.0.1 14 Mar 2012 Is there any way to avoid these errors? I limited my cipher set to just RC4-SHA after seeing that there is an issue even in openssl 1.01e-1 for e_aes_cbc_hmac_sha1.c http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678353 Appreciate your help. Thanks, Kishore

1 0

Need help to configure STUNNEL using proxy socks v5 to send file to a server
by laurent.uk＠bnpparibas.com 11 Mar '13

11 Mar '13

Hi everyone, I need to connect to proxy socks V5 in order to send file in my server. I configure my stunnel like this : sslVersion = SSLv3 client=yes cert = /opt/freeware/etc/stunnel/ca_nopass.pem pid = /var/adm/stunnel_test.pid socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 debug = 7 output = /logs/stunnel/stunnel.log ; Don't forget to c_rehash CApath ; CApath is located inside chroot jail CApath = /opt/freeware/etc/stunnel/CA_files/ protocol = connect protocolAuthentication = basic protocolHost = ***:8080 [pesit] accept = 12099 connect = ***:433 But it doesn't works! The log from my stunnel client : 2013.03.11 18:57:30 LOG5[26673178:260]: Service pesit accepted connection from ***:48549 2013.03.11 18:57:30 LOG7[26673178:260]: remote socket: FD=1 allocated (non-blocking mode) 2013.03.11 18:57:30 LOG6[26673178:260]: connect_blocking: connecting ::1:10443 2013.03.11 18:57:30 LOG3[26673178:260]: connect_blocking: connect ::1:10443: Connection refused (79) 2013.03.11 18:57:30 LOG7[26673178:260]: remote socket: FD=1 allocated (non-blocking mode) 2013.03.11 18:57:30 LOG6[26673178:260]: connect_blocking: connecting ****:10443 2013.03.11 18:57:30 LOG5[26673178:260]: connect_blocking: connected ****:10443 2013.03.11 18:57:30 LOG5[26673178:260]: Service pesit connected remote server from ****:48551 2013.03.11 18:57:30 LOG7[26673178:260]: Remote FD=1 initialized 2013.03.11 18:57:30 LOG7[26673178:260]: Option TCP_NODELAY set on remote socket 2013.03.11 18:57:30 LOG6[26673178:260]: Client-mode connect protocol negotiations started 2013.03.11 18:57:30 LOG7[26673178:260]: -> CONNECT ****:1080 HTTP/1.1 2013.03.11 18:57:30 LOG7[26673178:260]: -> Host: ****:1080 2013.03.11 18:57:30 LOG7[26673178:260]: -> 2013.03.11 18:57:30 LOG3[26673178:260]: fdgetline: readsocket: Connection reset by peer (73) 2013.03.11 18:57:30 LOG5[26673178:260]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2013.03.11 18:57:30 LOG7[26673178:260]: Service pesit finished (0 left) 2013.03.11 18:57:30 LOG7[26673178:260]: str_stats: 0 block(s), 0 data byte(s), 0 control byte(s) 2013.03.11 18:57:32 LOG7[26673178:1]: local socket: FD=0 allocated (non-blocking mode) In my stunnel server, i have the following message : "SSL_accept: 1407609B: error:1407609B:SSL routines:SSL23_GET_CLIENT_HELLO:https proxy request" 2013.03.11 18:57:30 LOG7[27525210:1]: Service pesitip accepted FD=0 from ****:48551 2013.03.11 18:57:30 LOG7[27525210:265]: Service pesitip started 2013.03.11 18:57:30 LOG7[27525210:265]: Option TCP_NODELAY set on local socket 2013.03.11 18:57:30 LOG5[27525210:265]: Service pesitip accepted connection from 159.50.49.69:48551 2013.03.11 18:57:30 LOG3[27525210:265]: SSL_accept: 1407609B: error:1407609B:SSL routines:SSL23_GET_CLIENT_HELLO:https proxy request 2013.03.11 18:57:30 LOG5[27525210:265]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2013.03.11 18:57:30 LOG7[27525210:265]: Service pesitip finished (0 left) 2013.03.11 18:57:30 LOG7[27525210:265]: str_stats: 0 block(s), 0 data byte(s), 0 control byte(s) 2013.03.11 18:57:32 LOG7[27525210:1]: local socket: FD=0 allocated (non-blocking mode) Can you help me to configure my stunnel please? Thanks. Regards, Laurent UK This message and any attachments (the "message") is intended solely for the intended addressees and is confidential. If you receive this message in error,or are not the intended recipient(s), please delete it and any copies from your systems and immediately notify the sender. Any unauthorized view, use that does not comply with its purpose, dissemination or disclosure, either whole or partial, is prohibited. Since the internet cannot guarantee the integrity of this message which may not be reliable, BNP PARIBAS (and its subsidiaries) shall not be liable for the message if modified, changed or falsified. Do not print this message unless it is necessary,consider the environment. ---------------------------------------------------------------------------------------------------------------------------------- Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur ou s'il ne vous est pas destine, merci de le detruire ainsi que toute copie de votre systeme et d'en avertir immediatement l'expediteur. Toute lecture non autorisee, toute utilisation de ce message qui n'est pas conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite. L'Internet ne permettant pas d'assurer l'integrite de ce message electronique susceptible d'alteration, BNP Paribas (et ses filiales) decline(nt) toute responsabilite au titre de ce message dans l'hypothese ou il aurait ete modifie, deforme ou falsifie. N'imprimez ce message que si necessaire, pensez a l'environnement.

1 0

Mutual Authentication
by Sameer Rahmani 11 Mar '13

11 Mar '13

Hi guys, I want to have secure tunnel to my server and also i want only specified clients can connect via the tunnel to the server. I was reading about mutual authentication but i can't run stunnel using verify=2 or 3 or 4. I confused. Can you please explain for me what should i do to use 2way ssl connection? how does stunnel use this?

2 1

It doesn't work.
by Raemsh Pungavanam 11 Mar '13

11 Mar '13

Hi , i have following issue with latest version of stunnel and openssl. version ====== stunnel - 4.55 openssl - 1.0.1e stunnel.conf ========== # Sample stunnel configuration file # Copyright by Michal Trojnara 2002 # Comment it out on Win32 #cert = /etc/tr69/stunnel.pem key = /etc/tr69/stunnel.pem # chroot = /usr/local/var/run/stunnel/ # PID is created inside chroot jail pid = /var/run/ssl.pid setuid = root setgid = root # Protocol version (all, SSLv2, SSLv3, TLSv1) sslVersion = TLSv1.2 # Workaround for Eudora bug #options = DONT_INSERT_EMPTY_FRAGMENTS # Authentication stuff verify = 1 # don't forget about c_rehash CApath # it is located inside chroot jail: #CApath = /certs # or simply use CAfile instead: #CAfile = /usr/local/etc/stunnel/certs.pem #CAfile = /etc/tr69/ca.crt # CRL path or file (inside chroot jail): #CRLpath = /crls # or simply use CAfile instead: #CRLfile = /usr/local/etc/stunnel/crls.pem # Some debugging stuff debug = 7 output = /var/log/ssl.log foreground = yes # Use it for client mode client = yes # Service-level configuration [https] CAfile = /flash/Cert.pem accept = 127.0.0.1:8001 connect = acs.qacafe.com:80 #accept = 8080 cat /var/log/ssl.log ============== 2013.03.11 18:29:04 LOG5[5849:0]: stunnel 4.55 on mips-openwrt-linux-uclibc platform 2013.03.11 18:29:04 LOG5[5849:0]: Compiled/running with OpenSSL 1.0.1e 11 Feb 2013 2013.03.11 18:29:04 LOG5[5849:0]: Threading:FORK SSL:+ENGINE+OCSP Auth:none Sockets:POLL+IPv6 2013.03.11 18:29:04 LOG5[5849:0]: Reading configuration from file /etc/tr69/stunnel.conf 2013.03.11 18:29:04 LOG7[5849:0]: Compression not enabled 2013.03.11 18:29:04 LOG7[5849:0]: PRNG seeded successfully 2013.03.11 18:29:04 LOG6[5849:0]: Initializing service [https] 2013.03.11 18:29:04 LOG4[5849:0]: Insecure file permissions on /etc/tr69/stunnel.pem 2013.03.11 18:29:04 LOG7[5849:0]: Loaded verify certificates from /flash/Cert.pem 2013.03.11 18:29:04 LOG7[5849:0]: Loaded /flash/Cert.pem revocation lookup file 2013.03.11 18:29:04 LOG7[5849:0]: SSL options set: 0x00000004 2013.03.11 18:29:04 LOG5[5849:0]: Configuration successful 2013.03.11 18:29:04 LOG7[5849:0]: Service [https] (FD=17) bound to 127.0.0.1:8001 2013.03.11 18:29:04 LOG7[5849:0]: Created pid file /var/run/ssl.pid 2013.03.11 18:29:21 LOG7[5849:0]: Service [https] accepted (FD=4) from 127.0.0.1:36039 2013.03.11 18:29:21 LOG7[5920:0]: Service [https] started 2013.03.11 18:29:21 LOG5[5920:0]: Service [https] accepted connection from 127.0.0.1:36039 2013.03.11 18:29:22 LOG6[5920:0]: connect_blocking: connecting 6.0.0.1:80 2013.03.11 18:29:22 LOG7[5920:0]: connect_blocking: s_poll_wait 6.0.0.1:80: waiting 10 seconds 2013.03.11 18:29:22 LOG5[5920:0]: connect_blocking: connected 6.0.0.1:80 2013.03.11 18:29:22 LOG5[5920:0]: Service [https] connected remote server from 61.200.100.100:35694 2013.03.11 18:29:22 LOG7[5920:0]: Remote socket (FD=17) initialized 2013.03.11 18:29:22 LOG7[5920:0]: SNI: sending servername: acs.qacafe.com 2013.03.11 18:29:22 LOG7[5920:0]: SSL state (connect): before/connect initialization 2013.03.11 18:29:22 LOG7[5920:0]: SSL state (connect): SSLv3 write client hello A 2013.03.11 18:30:15 LOG7[5849:0]: Service [https] accepted (FD=4) from 127.0.0.1:36042 2013.03.11 18:30:15 LOG7[5973:0]: Service [https] started 2013.03.11 18:30:15 LOG5[5973:0]: Service [https] accepted connection from 127.0.0.1:36042 2013.03.11 18:30:15 LOG6[5973:0]: connect_blocking: connecting 6.0.0.1:80 2013.03.11 18:30:15 LOG7[5973:0]: connect_blocking: s_poll_wait 6.0.0.1:80: waiting 10 seconds 2013.03.11 18:30:15 LOG5[5973:0]: connect_blocking: connected 6.0.0.1:80 2013.03.11 18:30:15 LOG5[5973:0]: Service [https] connected remote server from 61.200.100.100:35697 2013.03.11 18:30:15 LOG7[5973:0]: Remote socket (FD=17) initialized 2013.03.11 18:30:15 LOG7[5973:0]: SNI: sending servername: acs.qacafe.com 2013.03.11 18:30:15 LOG7[5973:0]: SSL state (connect): before/connect initialization 2013.03.11 18:30:15 LOG7[5973:0]: SSL state (connect): SSLv3 write client hello A 2013.03.11 18:31:40 LOG7[5849:0]: Service [https] accepted (FD=4) from 127.0.0.1:49029 2013.03.11 18:31:40 LOG7[6023:0]: Service [https] started 2013.03.11 18:31:40 LOG5[6023:0]: Service [https] accepted connection from 127.0.0.1:49029 2013.03.11 18:31:40 LOG6[6023:0]: connect_blocking: connecting 6.0.0.1:80 2013.03.11 18:31:40 LOG7[6023:0]: connect_blocking: s_poll_wait 6.0.0.1:80: waiting 10 seconds 2013.03.11 18:31:40 LOG5[6023:0]: connect_blocking: connected 6.0.0.1:80 2013.03.11 18:31:40 LOG5[6023:0]: Service [https] connected remote server from 61.200.100.100:40051 2013.03.11 18:31:40 LOG7[6023:0]: Remote socket (FD=17) initialized 2013.03.11 18:31:40 LOG7[6023:0]: SNI: sending servername: acs.qacafe.com 2013.03.11 18:31:40 LOG7[6023:0]: SSL state (connect): before/connect initialization 2013.03.11 18:31:40 LOG7[6023:0]: SSL state (connect): SSLv3 write client hello A 2013.03.11 18:33:45 LOG7[5849:0]: Service [https] accepted (FD=4) from 127.0.0.1:49032 2013.03.11 18:33:45 LOG7[6074:0]: Service [https] started 2013.03.11 18:33:45 LOG5[6074:0]: Service [https] accepted connection from 127.0.0.1:49032 2013.03.11 18:33:45 LOG6[6074:0]: connect_blocking: connecting 6.0.0.1:80 2013.03.11 18:33:45 LOG7[6074:0]: connect_blocking: s_poll_wait 6.0.0.1:80: waiting 10 seconds 2013.03.11 18:33:45 LOG5[6074:0]: connect_blocking: connected 6.0.0.1:80 2013.03.11 18:33:45 LOG5[6074:0]: Service [https] connected remote server from 61.200.100.100:40054 2013.03.11 18:33:45 LOG7[6074:0]: Remote socket (FD=17) initialized 2013.03.11 18:33:45 LOG7[6074:0]: SNI: sending servername: acs.qacafe.com 2013.03.11 18:33:45 LOG7[6074:0]: SSL state (connect): before/connect initialization 2013.03.11 18:33:45 LOG7[6074:0]: SSL state (connect): SSLv3 write client hello A 2013.03.11 18:34:22 LOG6[5920:0]: init_ssl: s_poll_wait: TIMEOUTbusy exceeded: sending reset 2013.03.11 18:34:22 LOG5[5920:0]: Connection reset: 0 byte(s) sent to SSL, 0 byte(s) sent to socket 2013.03.11 18:34:22 LOG7[5920:0]: Remote socket (FD=17) closed 2013.03.11 18:34:22 LOG7[5920:0]: Local socket (FD=4) closed 2013.03.11 18:34:22 LOG7[5920:0]: Service [https] finished 2013.03.11 18:34:22 LOG7[5920:0]: str_stats: 19 block(s), 877 data byte(s), 798 control byte(s) 2013.03.11 18:34:22 LOG7[5849:0]: Dispatching signals from the signal pipe 2013.03.11 18:34:22 LOG7[5849:0]: Processing SIGCHLD 2013.03.11 18:34:22 LOG7[5849:0]: Process 5920 finished with code 0 2013.03.11 18:34:22 LOG7[5849:0]: Signal pipe is empty 2013.03.11 18:35:15 LOG6[5973:0]: init_ssl: s_poll_wait: TIMEOUTbusy exceeded: sending reset 2013.03.11 18:35:15 LOG5[5973:0]: Connection reset: 0 byte(s) sent to SSL, 0 byte(s) sent to socket 2013.03.11 18:35:15 LOG7[5973:0]: Remote socket (FD=17) closed 2013.03.11 18:35:15 LOG7[5973:0]: Local socket (FD=4) closed 2013.03.11 18:35:15 LOG7[5973:0]: Service [https] finished 2013.03.11 18:35:15 LOG7[5973:0]: str_stats: 19 block(s), 877 data byte(s), 798 control byte(s) 2013.03.11 18:35:15 LOG7[5849:0]: Dispatching signals from the signal pipe 2013.03.11 18:35:15 LOG7[5849:0]: Processing SIGCHLD 2013.03.11 18:35:15 LOG7[5849:0]: Process 5973 finished with code 0 2013.03.11 18:35:15 LOG7[5849:0]: Signal pipe is empty 2013.03.11 18:36:40 LOG6[6023:0]: init_ssl: s_poll_wait: TIMEOUTbusy exceeded: sending reset 2013.03.11 18:36:40 LOG5[6023:0]: Connection reset: 0 byte(s) sent to SSL, 0 byte(s) sent to socket 2013.03.11 18:36:40 LOG7[6023:0]: Remote socket (FD=17) closed 2013.03.11 18:36:40 LOG7[6023:0]: Local socket (FD=4) closed 2013.03.11 18:36:40 LOG7[6023:0]: Service [https] finished 2013.03.11 18:36:40 LOG7[6023:0]: str_stats: 19 block(s), 877 data byte(s), 798 control byte(s) 2013.03.11 18:36:40 LOG7[5849:0]: Dispatching signals from the signal pipe 2013.03.11 18:36:40 LOG7[5849:0]: Processing SIGCHLD 2013.03.11 18:36:40 LOG7[5849:0]: Process 6023 finished with code 0 2013.03.11 18:36:40 LOG7[5849:0]: Signal pipe is empty 2013.03.11 18:38:45 LOG6[6074:0]: init_ssl: s_poll_wait: TIMEOUTbusy exceeded: sending reset 2013.03.11 18:38:45 LOG5[6074:0]: Connection reset: 0 byte(s) sent to SSL, 0 byte(s) sent to socket 2013.03.11 18:38:45 LOG7[6074:0]: Remote socket (FD=17) closed 2013.03.11 18:38:45 LOG7[6074:0]: Local socket (FD=4) closed 2013.03.11 18:38:45 LOG7[6074:0]: Service [https] finished 2013.03.11 18:38:45 LOG7[6074:0]: str_stats: 19 block(s), 877 data byte(s), 798 control byte(s) 2013.03.11 18:38:45 LOG7[5849:0]: Dispatching signals from the signal pipe 2013.03.11 18:38:45 LOG7[5849:0]: Processing SIGCHLD 2013.03.11 18:38:45 LOG7[5849:0]: Process 6074 finished with code 0 2013.03.11 18:38:45 LOG7[5849:0]: Signal pipe is empty Normally under which circumstances this can happen. please help me totally clue less ... Rgds, Ramesh P

1 0

Stunnel SMP enabled?
by Michael Curran 06 Mar '13

06 Mar '13

I am running an Ubuntu system with Stunnel for 443 connections to an application on the back end. Essentially acting as a load balancer. When I look at the processor stats per processor (this is a 6-cpu system) I see cpu0 with almost 4% usage , compared to the other 5 processors hiting maybe .5% usage across the board. Is stunnel SMP enabled and passes processing amongst all 6 Procs? Or does it bind to one Proc and as long as its active it does all its work on just one PROC. We are having a lot of dropped connections when the overall system CPU hits about 23-25% .. which seems to me that it could be pushing just one CPU hard and the other 5 become basically idle. I am setting up to capture some SAR data to help confirm this effort, but it would if I knew that stunnel was setup for SMP processing.

1 0

Re: [stunnel-users] Stunnel as an "HTTPS to HTTPS" proxy
by Javier 05 Mar '13

05 Mar '13

On Tue, 05 Mar 2013 09:04:41 +0200 "jmwb(a)webmail.co.za" <jmwb(a)webmail.co.za> wrote: > Thank you for your response Javier. > > I now understand how to phrase what I am looking for. What I am looking for is > effectively an SSL Man-in-The-Middle (but please be assured that I am not > looking to build malware). However, I am still not certain from your response > that Stunnel can do this. Can the client-side handle SSL or does it only > support clear-text on the client side? > > jmwb Hi, in the example I gave to you is like this. Hope this can help you to understand how stunnel works in such scenario. 1. Web browser without SSL support. 2. It sends clear text to the IP:port where stunnel client is listening. 3. Stunnel in the client machine send ciphered text to the machine with Stunnel acting as server. 4. Stunnel in the server machine sends clear text to the web server. 5. The web server hasn't SSL support. 6. The communication is reversed to reply to the client side. With a diagram. Browser <> clear text <> stunnel<> ciphered <> stunnel <> clear text <> web server Of course, it is possible to make a MiTM attack between browser and stunnel and stunnel and web server at both sides, but not in between. To accomplish such attack you'll first need to access one of the machines and find such scenario. If both sides support SSL you don't need stunnel (unless one of the sides doesn't support SSL) and, therefore, all communications are ciphered P2P. No clear text. Except keyboard/mouse loggers in the client side. As said, is a secure tunnel, an SSL proxy. As you wish. Regards.

1 0

Re: [stunnel-users] Disable SNI in stunnel win32 version
by Lilienberg, Daniel () 05 Mar '13

05 Mar '13

I want to use my Apache as a secure proxy (where Stunnel adds the SSL layer). With SNI enabled, I must send all hosts I want to connect to which is impossible ? This is for internet proxy usage, so all sites on Internet must be available through the proxy. It worked fine before SNI. From: Brian Wilkins [mailto:bwilkins@gmail.com] Sent: den 5 mars 2013 14:14 To: Lilienberg, Daniel () Subject: Re: [stunnel-users] Disable SNI in stunnel win32 version Does this help? http://langui.sh/2009/11/03/ssl-vhosting-on-the-same-ip-aka-sni/ On Tue, Mar 5, 2013 at 8:10 AM, Lilienberg, Daniel () <daniel.lilienberg(a)volvocars.com<mailto:daniel.lilienberg@volvocars.com>> wrote: Hi, In my local vmware setup im using Apache with mod_ssl on the server side and Stunnel on client side to make a secure proxy. Im using Chrome as webbrowser to connect locally to the apache which bounces me to internet. In my setup everything worked with the older Stunnel 4.3x, but when you upgraded to a newer Openssl it enabled SNI and now its broken. Can I disable SNI in any way or so I need to recompile stunnel with an older OpenSSL package ? Im running on Win32. _______________________________________________ stunnel-users mailing list stunnel-users(a)stunnel.org<mailto:stunnel-users@stunnel.org> https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users

1 0

Disable SNI in stunnel win32 version
by Lilienberg, Daniel () 05 Mar '13

05 Mar '13

Hi, In my local vmware setup im using Apache with mod_ssl on the server side and Stunnel on client side to make a secure proxy. Im using Chrome as webbrowser to connect locally to the apache which bounces me to internet. In my setup everything worked with the older Stunnel 4.3x, but when you upgraded to a newer Openssl it enabled SNI and now its broken. Can I disable SNI in any way or so I need to recompile stunnel with an older OpenSSL package ? Im running on Win32.

1 0

Stunnel as an "HTTPS to HTTPS" proxy
by jmwb＠webmail.co.za 04 Mar '13

04 Mar '13

Hi, Please could you tell me if Stunnel supports HTTPS on the client-side i.e. a true SSL proxy with client-side SSL and server-side SSL (or if anyone has developed a version that does)? I have tried searching for this without luck because it is difficult to narrow down the search criteria e.g. Stunnel is already cited as an SSL proxy. jmwb ____________________________________________________________ South Africas premier free email service - www.webmail.co.za For super low premiums, click here. http://www.dialdirect.co.za/landing/oct/1/?vdn=15752

2 1