stunnel-users

stunnel-users@stunnel.org

5 participants
3293 discussions

Help using Stunnel-4.XX
by Harmon, Paul 30 Nov '07

30 Nov '07

Hi Folks, Well I know a little more now than before. The version of Stunnel I'm using is Stunnel 4.05 running under Fedora 7.0. I am trying to setup a test scenario at the moment where I am running a stream socket between a client and a server, both mine since this is a test scenario. I need thisese programs to connect over a secure socket and the exchange of data is a custom application. I've read through Barry O'donovan's article and that seems to give me the information on how to configure and use Stunnel on the server side. It is not clear to me yet, what I need to do to the client side. Is there anyone out there who has done this type of thing and could give me some help? Thanks in advance, Paul Harmon

2 1

Problem with stunnel 4.20 on Fedora 7
by Andrew M Dunn 30 Nov '07

30 Nov '07

[Oh wise list folks... I haven't seen any responses to this. Does anybody have any experience either with using stunnel on Fedora 7, or with the particular error? I cannot find any other hints or reasons as to why the resolution is failing... Andy] ----original message------ I can't get stunnel to run on a freshly-installed Fedora 7 system. It fails with "Error resolving '0.0.0.0': servname is not supported for ai_socktype" but the usual other causes of that error (ie. ports not defined in /etc/services, bad settings in /etc/nsswitch.conf) are not the culprit this time. COMMAND LINE: /usr/sbin/stunnel /home/amdunn/security/stunnel.conf COMMAND OUTPUT: 2007.08.29 11:44:12 LOG3[13614:3086243520]: Error resolving '0.0.0.0': servname is not supported for ai_socktype (EAI_SERVICE) file /home/amdunn/security/stunnel.conf line 10: Failed to resolve accepting address STUNNEL.CONF FILE: ; ; stunnel file for testing 443 access to local http server ; cert=/home/amdunn/security/xxxxxxx key=/home/amdunn/security/yyyyyyy foreground=yes ; ; [sweb] accept=443 ; https port connect=80 ; standard httpd listening port TIMEOUTclose=0 ; must set this or IE waits 60sec on page end client=no STUNNEL -VERSION OUTPUT: stunnel 4.20 on i686-redhat-linux-gnu with OpenSSL 0.9.8b 04 May 2006 Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv6 Auth:LIBWRAP Global options debug = 5 pid = /var/run/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes Service-level options cert = /etc/stunnel/stunnel.pem ciphers = ALL:!ADH:+RC4:@STRENGTH key = /etc/stunnel/stunnel.pem session = 300 seconds sslVersion = SSLv3 for client, all for server TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds verify = none

2 1

zlib compression not working
by webmaster＠escoltesiguies.cat 29 Nov '07

29 Nov '07

I have configured both windows client and linux server (samba) with zlib compression: compression = zlib But I have transferred a txt file of 100Mb in 40 minutes and the same file compressed with gzip (22Mb) in 14 minutes. So I thing compression is not working. Client log tells: Compression enabled using zlib method and server log: Compression enabled using zlib method How can I verify comression is working? maybe compression is working but it is poor?

1 0

About stunnel 4.21 daemon mode
by wei hu 28 Nov '07

28 Nov '07

Dear I had successfully installed stunnel 4.21 on my server, but after I edited the file stunnel.conf and startup the stunnel, I can't find the stunnel via the "ps -ef" command.Then I have found such error message in the log file: 2007.11.27 07:42:28 LOG5[28550:3085354688]: stunnel 4.21 on i686-pc-linux-gnu wi th OpenSSL 0.9.7f 22 Mar 2005 2007.11.27 07:42:28 LOG5[28550:3085354688]: Threading:PTHREAD SSL:ENGINE Sockets :POLL,IPv6 Auth:LIBWRAP 2007.11.27 07:42:28 LOG6[28550:3085354688]: file ulimit = 1024 (can be changed w ith 'ulimit -n') 2007.11.27 07:42:28 LOG6[28550:3085354688]: poll() used - no FD_SETSIZE limit fo r file descriptors 2007.11.27 07:42:28 LOG5[28550:3085354688]: 500 clients allowed 2007.11.27 07:42:28 LOG7[28550:3085354688]: FD 9 in non-blocking mode 2007.11.27 07:42:28 LOG7[28550:3085354688]: FD 10 in non-blocking mode 2007.11.27 07:42:28 LOG7[28550:3085354688]: FD 11 in non-blocking mode 2007.11.27 07:42:28 LOG7[28550:3085354688]: SO_REUSEADDR option set on accept so cket 2007.11.27 07:42:28 LOG7[28550:3085354688]: sproxy bound to 0.0.0.0:83 2007.11.27 07:42:28 LOG3[28556:3085354688]: Failed to get GID for group nobody Do somebody knows how to get GID for group nobody? My nobody group is sured to work correctly with Squid. The config file about group: ; Some security enhancements for UNIX systems - comment them out on Win32 chroot = /usr/local/var/lib/stunnel/ setuid = nobody setgid = nobody ; PID is created inside chroot jail pid = /stunnel.pid The command "stunnel -version" response: [root@vps stunnel]# /usr/local/bin/stunnel -version stunnel 4.21 on i686-pc-linux-gnu with OpenSSL 0.9.7f 22 Mar 2005 Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv6 Auth:LIBWRAP Global options debug = 5 pid = /usr/local/var/run/stunnel/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes Service-level options cert = /usr/local/etc/stunnel/stunnel.pem ciphers = ALL:!ADH:+RC4:@STRENGTH key = /usr/local/etc/stunnel/stunnel.pem session = 300 seconds sslVersion = SSLv3 for client, all for server TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds verify = none The command "/usr/local/bin/stunnel" response: [root@vps stunnel]# /usr/local/bin/stunnel 2007.11.27 07:27:27 LOG7[13697:3085354688]: Snagged 64 random bytes from /root/.rnd 2007.11.27 07:27:27 LOG7[13697:3085354688]: Wrote 1024 new random bytes to /root/.rnd 2007.11.27 07:27:27 LOG7[13697:3085354688]: RAND_status claims sufficient entropy for the PRNG 2007.11.27 07:27:27 LOG7[13697:3085354688]: PRNG seeded successfully 2007.11.27 07:27:27 LOG7[13697:3085354688]: Certificate: /usr/local/etc/stunnel/stunnel.pem 2007.11.27 07:27:27 LOG7[13697:3085354688]: Certificate loaded 2007.11.27 07:27:27 LOG7[13697:3085354688]: Key file: /usr/local/etc/stunnel/stunnel.pem 2007.11.27 07:27:27 LOG7[13697:3085354688]: Private key loaded 2007.11.27 07:27:27 LOG7[13697:3085354688]: SSL context initialized for service sproxy Best Regards, HuWei

2 2

Re: [stunnel-users] More questions on RDP and port forwarding
by richard.woodman＠cox.net 28 Nov '07

28 Nov '07

Carter, Thanks. With the exception of the client's loopback address in the hosts file, I have a very similar configuration. I have created an inbound rule (Custom service with an inbound rule declaration but no outbound rule) that looks just like my inbound RDP rules - I even reviewed the configuration file and the stunnel rule had the same commands as the RDP rule. However, RDP works through the firewall but stunnel does not. My Windows firewall has an exception for stunnel with a scope of "Internet" and the stunnel server works from within the corporate network. Meaning, I think, that the Windows firewall is not denying the connection (at least from within the same subnet). I am not a Windows AD guy, but is there a way to prevent network connections without using the Windows firewall? I mean, can a GPO be created that prevents connections from IP addresses not on the same subnet but that does not use the OS's firewall? If so, this could be the issue because from what I can see, neither the Watchguard nor the Windows firewalls are blocking the connection; yet I still cannot connect. Richard Carter Browne wrote: I use stunnel to protect RDP for a couple of sites using a mix of Watchguard Edge and V series firewalls. For computer ABC that I want to connect to, I create an entry in the hosts file: 127.0.0.n ABCs (where n is greater than 1) On the client side I have an entry: [ABC-RDP] accept = ADCs:12345 connect = ABC:54321 client = yes On the server sid I have an entry: [RDP-IN] accept = 54321 connect = 3389 client = no Port 54321 is enabled in both the Watchguard and the Windows firewalls. Using the 127.n.n.n ports are not processed by the firewalls. You can use 127.0.0.1 for everything, but I needed to connect to more that one host and wanted a standard setup. I have had a number of users confused by this setup whereby the program references a local port to connect to a remote computer. For stunnel, it is the connect string that determines the destination, so any local port works fine for the accept string. Carter

2 1

Problems accessing samba
by webmaster＠escoltesiguies.cat 27 Nov '07

27 Nov '07

I have a winXP machine which should connect to a linux samba. Everything installed following http://wiki.netbsd.se/index.php/How_to_secure_samba_with_stunnel but it don't connect. I have both loglevels set to 7, and as serverlog don't change I thing the error is at clientside. stunnel.conf is: client=yes debug = 7 [smb] accept=222.222.222.222:139 connect=85.48.253.144:8888 And the client log is: 2007.11.27 12:46:58 LOG7[3716:720]: RAND_status claims sufficient entropy for the PRNG 2007.11.27 12:46:58 LOG7[3716:720]: PRNG seeded successfully 2007.11.27 12:46:58 LOG7[3716:720]: Certificate: stunnel.pem 2007.11.27 12:46:58 LOG7[3716:720]: Certificate loaded 2007.11.27 12:46:58 LOG7[3716:720]: Key file: stunnel.pem 2007.11.27 12:46:58 LOG7[3716:720]: Private key loaded 2007.11.27 12:46:58 LOG7[3716:720]: SSL context initialized for service smb 2007.11.27 12:46:58 LOG5[3716:720]: stunnel 4.21 on x86-pc-mingw32-gnu with OpenSSL 0.9.8g 19 Oct 2007 2007.11.27 12:46:58 LOG5[3716:720]: Threading:WIN32 SSL:ENGINE Sockets:SELECT,IPv6 2007.11.27 12:46:58 LOG5[3716:3292]: No limit detected for the number of clients 2007.11.27 12:46:59 LOG7[3716:3292]: FD 216 in non-blocking mode 2007.11.27 12:46:59 LOG7[3716:3292]: SO_REUSEADDR option set on accept socket 2007.11.27 12:46:59 LOG7[3716:3292]: smb bound to 222.222.222.222:139 2007.11.27 12:47:15 LOG7[3716:3292]: smb accepted FD=248 from 88.31.107.217:1625 2007.11.27 12:47:15 LOG7[3716:3292]: Creating a new thread 2007.11.27 12:47:15 LOG7[3716:3292]: New thread created 2007.11.27 12:47:15 LOG7[3716:4028]: smb started 2007.11.27 12:47:15 LOG7[3716:4028]: FD 248 in non-blocking mode 2007.11.27 12:47:15 LOG7[3716:4028]: TCP_NODELAY option set on local socket 2007.11.27 12:47:15 LOG5[3716:4028]: smb accepted connection from 88.31.107.217:1625 2007.11.27 12:47:15 LOG7[3716:4028]: FD 272 in non-blocking mode 2007.11.27 12:47:15 LOG7[3716:4028]: smb connecting 85.48.253.144:8888 2007.11.27 12:47:15 LOG7[3716:4028]: connect_wait: waiting 10 seconds 2007.11.27 12:47:25 LOG7[3716:3292]: smb accepted FD=308 from 88.31.107.217:1628 2007.11.27 12:47:25 LOG7[3716:3292]: Creating a new thread 2007.11.27 12:47:25 LOG7[3716:3292]: New thread created 2007.11.27 12:47:25 LOG7[3716:3012]: smb started 2007.11.27 12:47:25 LOG7[3716:3012]: FD 308 in non-blocking mode 2007.11.27 12:47:25 LOG7[3716:3012]: TCP_NODELAY option set on local socket 2007.11.27 12:47:25 LOG5[3716:3012]: smb accepted connection from 88.31.107.217:1628 2007.11.27 12:47:25 LOG7[3716:3012]: FD 340 in non-blocking mode 2007.11.27 12:47:25 LOG7[3716:3012]: smb connecting 85.48.253.144:8888 2007.11.27 12:47:25 LOG7[3716:3012]: connect_wait: waiting 10 seconds 2007.11.27 12:47:25 LOG6[3716:4028]: connect_wait: s_poll_wait timeout 2007.11.27 12:47:25 LOG5[3716:4028]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2007.11.27 12:47:25 LOG7[3716:4028]: smb finished (1 left) 2007.11.27 12:47:35 LOG6[3716:3012]: connect_wait: s_poll_wait timeout 2007.11.27 12:47:35 LOG5[3716:3012]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2007.11.27 12:47:35 LOG7[3716:3012]: smb finished (0 left) Where is the problem? Thanks

1 1

VeriSign Intermediate CA Certificate issue.
by Unai Rodriguez 27 Nov '07

27 Nov '07

Dear All, I am trying to set an https layer using stunnel. I am having problems with the intermediary certificate since it appears broken to the user. You may find a screenshot here: http://u-journal.org/stunnel/Root_Cert_Err.jpg My stunnel version is: 3.26 running on Debian 3.1 I run stunnel as standalone with this parameters: stunnel -d 10.123.16.103:443 -D 7 -R /etc/ssl/certs/stunnel.rnd \ -p /etc/ssl/certs/stunnel.pem -o /var/log/stunnel/stunnel.log \ -r 10.123.16.103:80 -N https You may find the output of my stunnel -V here: http://pastebin.ca/793495 uname -a: Linux lb2-dp-vm 2.6.8-3-686 #1 Tue Dec 5 21:26:38 UTC 2006 i686 GNU/Linux openssl version: OpenSSL 0.9.7e 25 Oct 2004 So, if I create my /etc/ssl/certs/stunnel.pem file like this: -----BEGIN RSA PRIVATE KEY----- rsa_priv_key -----END RSA PRIVATE KEY----- -----BEGIN CERTIFICATE----- secured.behringer.com_certificate -----END CERTIFICATE----- -- OR -- -----BEGIN RSA PRIVATE KEY----- rsa_priv_key -----END RSA PRIVATE KEY----- -----BEGIN CERTIFICATE----- secured.behringer.com_certificate -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- VeriSign Intermediate CA Certificate (https://www.verisign.com.sg/support/ssl/install/intermediate/secure.shtml) -----END CERTIFICATE----- I get the mentioned error. If I create the /etc/ssl/certs/stunnel.pem like this: -----BEGIN RSA PRIVATE KEY----- rsa_priv_key -----END RSA PRIVATE KEY----- -----BEGIN CERTIFICATE----- VeriSign Intermediate CA Certificate (https://www.verisign.com.sg/support/ssl/install/intermediate/secure.shtml) -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- secured.behringer.com_certificate -----END CERTIFICATE----- I get the error: "[...] X509_check_private_key:key values mismatch" You may see the log here: http://pastebin.ca/793500 Any clues on what am I doing wrong? Thank you so much! unai

1 1

Re: [stunnel-users] More questions on RDP and port forwarding
by richard.woodman＠cox.net 26 Nov '07

26 Nov '07

OK, I took my configs, my certs, etc. and put them on two boxes in the lab - then I ensured I could use stunnel to connect using VNC. I then put a NAT box (Linksys BEFSR81) between the two and configured the Linksys to provide port forwarding. I then reconnected and everything worked first time. Therefore, I can only assume that either port-forwarding is misconfigured on my Watchguard SOHO 6tc -or- that the Windows firewall is causing problems (neither lab box has a firewall running). I'll keep you posted on what I find. Thanks. Richard My original post: I did read through the archives but I cannot determine how to get Stunnel working through the firewall. Here is what I wish to do: 1. Tunnel Windows Remote Desktop through stunnel. 2. I wish to connect from home to work; I have access to the firewall at work. Here's what I've done: 1. Installed stunnel on Windows XP at home and at work. I have self-signed certificates and am using verify = 3 (on both computers). Cacert.pem has the CA cert, the work cert, and the home cert in a single file. The server-cert.pem has the work computer's key and cert while the client-1-cert.pem (home computer) has it's own key and cert. 2. Stunnel at home has client = yes, stunnel at work has this commented out. Stunnel at work will become a "server" where multiple clients connect via stunnel and that single computer makes multiple RDP connections. Client (home) computer has [rdp1] accept = 4391 connect = <work outside interface IP>:44391 Server (work) computer has [rdp2] accept = 44391 connect = <work computer name>:3392 If I try this at work from within the corporate network (change the client connect string to the stunnel server's IP or hostname), then everything works fine. However, once I try from outside the work network, nothing works. Firewall is a Watchguard SOHO 6tc and I have a inbound rule permitting 44391 and directing it to X.X.X.52 (the stunnel server). I also have other rules allowing RDP (on port 3392 for instance) directly to the computer I wish to control and those rules work. Essentially, RDP directly through the firewall works but stunnel through the firewall does not. I assume there is no traffic destined for .52 on 44391 because the log file on the server (with debug = 7) only shows the startup sequence and port binding (netstat -a shows I am listening on 44391). I also tried this at home on my Juniper 5XT and was unsuccessful. Please help. Richard

1 0

Re: [stunnel-users] More questions on RDP and port forwarding
by richard.woodman＠cox.net 26 Nov '07

26 Nov '07

Craig, Thanks. Are you advising that I put "client = yes" in the service declaration rather than the main configuration? I already have "client = yes" on the client side (in the main configuration) and that line commented out of the server's configuration (I assume the default is client = no). When I review the log on the client computer, I can see where it times out waiting on a response from the work firewall's outside IP address. I do not see any connection attempts on the server side and both stunnel instances (client and server) have debug = 7 and logging to stunnel.log. Richard > -----Original Message----- > From: stunnel-users-bounces(a)mirt.net [mailto:stunnel-users- > bounces(a)mirt.net] On Behalf Of Richard Woodman > Sent: 26 November 2007 07:44 AM > To: stunnel-users(a)mirt.net > Subject: [stunnel-users] More questions on RDP and port forwarding > > I did read through the archives but I cannot determine how to get > Stunnel > working through the firewall. Here is what I wish to do: > > 1. Tunnel Windows Remote Desktop through stunnel. > 2. I wish to connect from home to work; I have access to the firewall > at > work. > > Here's what I've done: > > 1. Installed stunnel on Windows XP at home and at work. I have self- > signed > certificates and am using verify = 3 (on both computers). Cacert.pem > has > the CA cert, the work cert, and the home cert in a single file. The > server-cert.pem has the work computer's key and cert while the > client-1-cert.pem (home computer) has it's own key and cert. > 2. Stunnel at home has client = yes, stunnel at work has this > commented > out. Stunnel at work will become a "server" where multiple clients > connect > via stunnel and that single computer makes multiple RDP connections. > > Client (home) computer has > Try changing the client config to the following: [rdp1] client = yes accept = 4391 connect = <work outside interface IP>:44391 > > Server (work) computer has > > [rdp2] > accept = 44391 > connect = <work computer name>:3392 > > If I try this at work from within the corporate network (change the > client > connect string to the stunnel server's IP or hostname), then everything > works fine. However, once I try from outside the work network, nothing > works. Firewall is a Watchguard SOHO 6tc and I have a inbound rule > permitting 44391 and directing it to X.X.X.52 (the stunnel server). I > also > have other rules allowing RDP (on port 3392 for instance) directly to > the > computer I wish to control and those rules work. Essentially, RDP > directly > through the firewall works but stunnel through the firewall does not. > I > assume there is no traffic destined for .52 on 44391 because the log > file on > the server (with debug = 7) only shows the startup sequence and port > binding > (netstat -a shows I am listening on 44391). I also tried this at home > on my > Juniper 5XT and was unsuccessful. Please help. > > Richard > > > _______________________________________________ > stunnel-users mailing list > stunnel-users(a)mirt.net > http://stunnel.mirt.net/mailman/listinfo/stunnel-users Cheers, Craig

1 0

More questions on RDP and port forwarding
by Richard Woodman 26 Nov '07

26 Nov '07

I did read through the archives but I cannot determine how to get Stunnel working through the firewall. Here is what I wish to do: 1. Tunnel Windows Remote Desktop through stunnel. 2. I wish to connect from home to work; I have access to the firewall at work. Here's what I've done: 1. Installed stunnel on Windows XP at home and at work. I have self-signed certificates and am using verify = 3 (on both computers). Cacert.pem has the CA cert, the work cert, and the home cert in a single file. The server-cert.pem has the work computer's key and cert while the client-1-cert.pem (home computer) has it's own key and cert. 2. Stunnel at home has client = yes, stunnel at work has this commented out. Stunnel at work will become a "server" where multiple clients connect via stunnel and that single computer makes multiple RDP connections. Client (home) computer has [rdp1] accept = 4391 connect = <work outside interface IP>:44391 Server (work) computer has [rdp2] accept = 44391 connect = <work computer name>:3392 If I try this at work from within the corporate network (change the client connect string to the stunnel server's IP or hostname), then everything works fine. However, once I try from outside the work network, nothing works. Firewall is a Watchguard SOHO 6tc and I have a inbound rule permitting 44391 and directing it to X.X.X.52 (the stunnel server). I also have other rules allowing RDP (on port 3392 for instance) directly to the computer I wish to control and those rules work. Essentially, RDP directly through the firewall works but stunnel through the firewall does not. I assume there is no traffic destined for .52 on 44391 because the log file on the server (with debug = 7) only shows the startup sequence and port binding (netstat -a shows I am listening on 44391). I also tried this at home on my Juniper 5XT and was unsuccessful. Please help. Richard

3 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

stunnel-users