August 2010 - stunnel-users

Stunnel 4 failing to connect to gmail
by Asif Iqbal 11 Dec '20

11 Dec '20

I am faling to connect to gmail. Not sure what that bind error means. iqbala@ghar:~$ sudo stunnel4 2008.12.15 13:53:17 LOG7[3839:3083650736]: Snagged 64 random bytes from /home/iqbala/.rnd 2008.12.15 13:53:17 LOG7[3839:3083650736]: Wrote 1024 new random bytes to /home/iqbala/.rnd 2008.12.15 13:53:17 LOG7[3839:3083650736]: RAND_status claims sufficient entropy for the PRNG 2008.12.15 13:53:17 LOG7[3839:3083650736]: PRNG seeded successfully 2008.12.15 13:53:17 LOG7[3839:3083650736]: Certificate: /etc/stunnel/stunnel.pem 2008.12.15 13:53:17 LOG7[3839:3083650736]: Certificate loaded 2008.12.15 13:53:17 LOG7[3839:3083650736]: Key file: /etc/stunnel/stunnel.pem 2008.12.15 13:53:17 LOG7[3839:3083650736]: Private key loaded 2008.12.15 13:53:17 LOG7[3839:3083650736]: SSL context initialized for service ssmtp 2008.12.15 13:53:17 LOG5[3839:3083650736]: stunnel 4.22 on i486-pc-linux-gnu with OpenSSL 0.9.8g 19 Oct 2007 2008.12.15 13:53:17 LOG5[3839:3083650736]: Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv6 Auth:LIBWRAP 2008.12.15 13:53:17 LOG6[3839:3083650736]: file ulimit = 1024 (can be changed with 'ulimit -n') 2008.12.15 13:53:17 LOG6[3839:3083650736]: poll() used - no FD_SETSIZE limit for file descriptors 2008.12.15 13:53:17 LOG5[3839:3083650736]: 500 clients allowed 2008.12.15 13:53:17 LOG7[3839:3083650736]: FD 10 in non-blocking mode 2008.12.15 13:53:17 LOG7[3839:3083650736]: FD 11 in non-blocking mode 2008.12.15 13:53:17 LOG7[3839:3083650736]: FD 12 in non-blocking mode 2008.12.15 13:53:17 LOG7[3839:3083650736]: SO_REUSEADDR option set on accept socket 2008.12.15 13:53:17 LOG3[3839:3083650736]: Error binding ssmtp to 74.125.93.111:587 2008.12.15 13:53:17 LOG3[3839:3083650736]: bind: Cannot assign requested address (99) Here is how my conf file looks like iqbala@ghar:~$ cat /etc/stunnel/stunnel.conf | egrep -v "^;|^$" cert = /etc/stunnel/stunnel.pem foreground = yes sslVersion = SSLv3 chroot = /var/lib/stunnel4/ setuid = stunnel4 setgid = stunnel4 pid = /stunnel4.pid socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 debug = 7 output = /var/log/stunnel4/stunnel.log client = yes [ssmtp] accept = smtp.gmail.com:587 connect = 25 Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu

5 9

Re: [stunnel-users] Stunnel on the same machine
by subrata＠indiatimes.com 01 Aug '11

01 Aug '11

The configuration files are : pid = /var/stunnel.pid ;chroot = /var/lib/stunnel setuid = nobody setgid = nobody foreground =yes ; Use it for client mode client = yes ; Service-level configuration [pop3s] accept = 995 connect = 110 [imaps] accept = 993 connect = 143 [ssmtp] accept = 465 connect = 25 [mysqls] accept = 3307 connect = 192.168.1.6:3307 On 192.168.1.6 ---------------------- pid = /var/stunnel.pid setuid =nobody setgid = nobody foreground = yes client = no ; Service-level configuration [pop3s] accept = 995 connect = 110 [imaps] accept = 993 connect = 143 [ssmtp] accept = 465 connect = 25 [mysqls] accept =3307 connect =3306 connecting like /usr/local/mysql/bin/mysql -h 127.0.0.1 -u root -p -P 3307 Enter password: On entring password the following lines appear : ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 104 Subrata ----- Original Message ----- From: Brian Hatch <bri(a)stunnel.org> To: subrata(a)indiatimes.com Sent: Sun, 7 Oct 2007 10:02:17 +0530 (IST) Subject: Re: [stunnel-users] Stunnel on the same machine Near 2007-10-05 22:17 +0530, subrata(a)indiatimes.com insisted: > After starting stunnel and connecting the mysql client/usr/local/mysql/bin/mysql -h 127.0.0.1 -u root -p the flow gets stuck at the Enter password prompt any suggestions how to proceed from there. What do your stunnel configuration files look like? Other problem: mysql client may decide to use a local domain socket when connecting to localhost, thwarting your attempts to go via Stunnel. You might want to 'strace mysql ...' and look for the connect() lines. -- Brian Hatch Time flies like an Systems and arrow. Fruit flies Security Engineer like a banana. http://www.ifokr.org/bri/ Every message PGP signed -- My life has changed. What about yours? Log on to the new Indiatimes Mail and Live out of the Inbox!

3 3

Stunnel 4.33 released
by Michal Trojnara 22 Apr '11

22 Apr '11

The ChangeLog entry: Version 4.33, 2010.04.05, urgency: MEDIUM: * New features - Win32 DLLs for OpenSSL 1.0.0. This library requires to c_rehash CApath/CRLpath directories on upgrade. - Win32 DLLs for zlib 1.2.4. - Experimental support for local mode on WIN32 platform. Try "exec = c:\windows\system32\cmd.exe". * Bugfixes - Inetd mode fixed SHA-1 value for stunnel-4.33.tar.gz: 695c7ef834952cb8ddbc790e10b6e32798fc2767 Home page: http://stunnel.mirt.net/ Download: ftp://stunnel.mirt.net/stunnel/ Best regards, Michal Trojnara

4 6

Re: [stunnel-users] Individual user certs for each person who uses Windows PC
by Bucci, David G 07 Sep '10

07 Sep '10

Thx for replying, Scott ... how did you handle multiple users on the PC, though? They all shared that cert? I thought about having a single location and copying to there on user login (from a standard location in a user's home dir, e.g.) ... then firing up stunnel ... but it seems like so much can go wrong, resulting in User B accessing using User A's certificate (because the copy failed, e.g.). And we're leery of exposing User A's cert to User B - especially since stunnel doesn't support encryption of the user's key, right? So the permissions would be a little tricky and maybe fragile. Seems like there should be a straightforward way to do it, dadnabit! ________________________________ From: Scott Gifford <sgifford(a)suspectclass.com> To: Bucci, David G Cc: stunnel-users(a)mirt.net <stunnel-users(a)mirt.net> Sent: Mon Aug 30 17:41:09 2010 Subject: EXTERNAL: Re: [stunnel-users] Individual user certs for each person who uses Windows PC On Mon, Aug 30, 2010 at 3:41 PM, Bucci, David G <david.g.bucci(a)lmco.com<mailto:[email protected]>> wrote: [ ... ] I've tried using envvars in the stunnel.conf (e.g., cert = %USERPROFILE%\usercert.pem), tried adjusting the command line to include "-p %USERPROFILE%\usercert.pem" as an option ... We implemented something similar by simply making a "C:\stunnel" directory on each PC, naming the certificate the same thing on all machines, then hardcoding that path into the stunnel configuration (e.g. "C:\stunnel\usercert.pem"). Not quite as nice as %USERPROFILE%\usercert.pem, but it worked. :-) Hope this is helpful, ----Scott.

5 11

Honor --sysconfdir and --localstatedir in stunnel.conf-sample.in
by Sebastian Kayser 01 Sep '10

01 Sep '10

Hi, I am packaging stunnel for opencsw.org. Would you guys mind merging a patch [1] to make use of --sysconfdir and --localstatedir (instead of @prefix@/{etc,var}) in the sample configuration file? Currently, if --sysconfdir and --localstatedir are passed to ./configure and are not a directory below prefix, the configuration file doesn't reflect this layout. The patch is against 4.33. Fedora seems to carry the same change [2]. Sebastian [1]http://gar.svn.sf.net/svnroot/gar/csw/mgar/pkg/stunnel/trunk/files/0001-M… [2]http://lists.fedoraproject.org/pipermail/scm-commits/2010-March/413078.ht…

3 4

[[email protected]: Bug#594876: stunnel4: Fails to connect, "Input line too long"]
by Rodrigo Gallardo 31 Aug '10

31 Aug '10

----- Forwarded message from Harri Kiiskinen <harri.kiiskinen(a)utu.fi> ----- Date: Mon, 30 Aug 2010 13:26:07 +0300 From: Harri Kiiskinen <harri.kiiskinen(a)utu.fi> To: Debian Bug Tracking System <submit(a)bugs.debian.org> Subject: Bug#594876: stunnel4: Fails to connect, "Input line too long" Package: stunnel4 Version: 3:4.29-1local1 Severity: normal My Univ. recently updated their mail servers, and I could not read my mails anymore with Emacs/mew, that uses stunnel4 for encryption. It turned out the reason was, that the server responded with this string: * OK [CAPABILITY STARTTLS CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS CHILDREN BINARY UNSELECT SORT LANGUAGE IDLE XSENDER X-NETSCAPE XSERVERINFO X-SUN-SORT X-SUN-IMAP X-ANNOTATEMORE X-UNAUTHENTICATE XUM1 AUTH=PLAIN AUTH=PLAIN] Messaging Multiplexor (Sun Java(tm) System Messaging Server 7.3-11.01 (built Sep 1 2009)) It turned out that this was way much longer than what stunnel4 expects. In common.h, one finds #define STRLEN 256 When this is changed to #define STRLEN 512 and the package recompiled, everything works well. Perhaps the length of accepted strings should be increased? Or is this long a response against some standard? All the best, Harri K. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-3-686 (SMP w/1 CPU core) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages stunnel4 depends on: ii adduser 3.112 add and remove users and groups ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libssl0.9.8 0.9.8o-1 SSL shared libraries ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra ii netbase 4.42 Basic TCP/IP networking system ii openssl 0.9.8o-1 Secure Socket Layer (SSL) binary a ii perl-modules 5.10.1-14 Core Perl modules stunnel4 recommends no packages. Versions of packages stunnel4 suggests: pn logcheck-database <none> (no description available) -- Configuration Files: /etc/stunnel/stunnel.conf changed [not included] -- no debconf information ----- End forwarded message ----- -- Rodrigo Gallardo

2 1

Individual user certs for each person who uses Windows PC
by Bucci, David G 30 Aug '10

30 Aug '10

Hi, all - I've searched, but can't find any answer on this. Is it possible to configure stunnel with client certificates on, and in such a way that individual users who logon have their own individual certificate used? I've tried using envvars in the stunnel.conf (e.g., cert = %USERPROFILE%\usercert.pem), tried adjusting the command line to include "-p %USERPROFILE%\usercert.pem" as an option ... the closest I've been able to think of (and it's a pretty blunt sword) is to create individual services, one per user and listening on different ports, then having each user access a different URL (well, different port#) ... I would prefer this all work when running as a Windows service, but if it's necessary to train the users to hit a start menu entry or something (e.g., if there's a way to do it using envvars on command line parameters), then the world probably won't end ... This is on Windows, but I'd also appreciate knowing how to do the same on Linux. Thx! ---- David G. Bucci When Dr. Bruce Banner becomes angry, he changes into the Incredible Hulk; when the Incredible Hulk becomes angry, he changes into Chuck Norris. -- ChuckNorrisFacts.com

2 1

Cross-compiling stunnel woes feedback
by Martin van den Nieuwelaar 30 Aug '10

30 Aug '10

Hi everyone (again). I thought I'd post some feedback regarding cross-compiling stunnel, which I have successfully done for an Arm based embedded system we use. I had to edit the 'configure' script in order to remove three sections of code that just check for the cross compiling option, and if set simply exit (message 'cannot check for file existence when cross compiling'). This behaviour really isn't condusive to successful cross compiling. :-) So as I say I removed these sections of code. Next, I configured with './configure --host=arm-linux', then 'make' and the rest are standard as usual. Perhaps the configure script for future releases could be a little more friendly for those cross compiling? Editing the configure file shouldn't be necessary. -- R A Ward Ltd. | We take the privacy of our customers seriously. Christchurch | All sensitive E-Mail attachments MUST be encrypted. New Zealand

2 2

"stunnel -version"
by Felix E. Klee 30 Aug '10

30 Aug '10

I installed the official stunnel 4.33 binary on Windows XP/32. And, when I execute "stunnel -version", a popup window appears with the following message: --------------------------- stunnel 4.33 on Win32 (not configured) --------------------------- Stunnel server is down due to an error. You need to exit and correct the problem. Click OK to see the error log window. --------------------------- OK --------------------------- Shouldn't that just work? What may be the cause for the problem? Indeed, I didn't configure stunnel yet. But I also realized that when I change something - for example the log level - in "stunnel.conf", then this is ignored by "stunnel -version". After clicking "OK" to close the popup message, I get some more info, though meaningless to me: stunnel 4.33 on x86-pc-mingw32-gnu with OpenSSL 1.0.0 29 Mar 2010 Threading:WIN32 SSL:ENGINE Sockets:SELECT,IPv6 Global options debug = notice RNDbytes = 64 RNDoverwrite = yes service = stunnel taskbar = yes Service-level options cert = stunnel.pem ciphers = ALL:!aNULL:!eNULL:!SSLv2 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 Server is down

2 4

Updated stunnel version in Debian experimental
by Rodrigo Gallardo 28 Aug '10

28 Aug '10

I have just uploaded stunnel 4.33 to Debian experimental. amd64 packages will be available for download as soon as the automated processing is done (6-12 hours). Other architectures will follow as the autobuilders get time in their queues for us. Aside from the updates in stunnel itself, the packaging has been updated somewhat. In particular, the start/stop scripts in /etc/init.d have grown shinny new options to take advantage of configuration file reloading and the log rotation config takes advantage of them to avoid the long standing issue of having to either live with ever-growing logs, or killing long lived connections when rotating. I would be very glad if you would test those new scripts and report any and all bugs. To Debian's BTS, of course, as none of them are at all the fault of our most excellent upstream ;) As much as I'd have liked to upload it to unstable, the distribution is now in freeze in preparation for the upcoming release, and thus uploading a completely new version of stunnel, together with the packaging changes I made would be completely unacceptable. I will upload this version, together with any bug fixes we collect, as soon as the release is over and sid is unfrozen again. Sadly, that means that the next Debian stable will release with 4.29. For that I am sorry, and I promise to make a backport of 4.33 available as soon as possible after the release. -- Rodrigo yes-I-have-been-remise-as-maintainer Gallardo

1 0