stunnel-users May 2011

stunnel-users@stunnel.org

16 participants
26 discussions

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

stunnel and hosts.allow
by Yousef Alhashemi 06 Jul '16

06 Jul '16

Hi, This may be a little bit off-topic, but does anyone here use stunnel with pan? My connections to stunnel (in pan) are always refused by libwrap. I was looking for the right rule to add to /etc/hosts.allow but nothing seems to work aside from "ALL : ALL" (which is obviously not good) and "nntps: KNOWN". Is the latter reasonable? The hosts_access(5) manpage is confusing to say the least. It mentions that daemon (the first token on any line) is the name of the daemon running the process, which would be "stunnel" in my case, but using "stunnel : LOCAL" or even "stunnel : ALL" doesn't work. The rule that seems to work, as mentioned, is "nntps : KNOWN" ("nntps" being the group name in stunnel.conf). What's even more confusing to me is that "nntps : LOCAL" does not work either. Nor does "nntps : localhost 127.0.0.1", "nntps : localhost", "nntps : 127.0.0.1", or "nntps : 192.168.1.". Pan is running on the same machine as stunnel so all connections must be coming from localhost. Why do these rules not trigger? Either way, I'd like to know the "least permissive" hosts.allow rule that would allow me to connect to my news provider from pan, and/or whether "nntps : KNOWN" is a safe option. Thanks, Yousef

3 6

patch for using stunnel as client with pkcs11-engine and opensc smartcard
by Märt Laak 29 Jan '12

29 Jan '12

Dear stunnel managers, I would like to inform you that there exist some incompatibility with stunnel and openssl pkcs11-engine with external PIN entry device (like RSA smartcard using opensc) in Linux. We use this config to load openssl engine stunnel.conf: --- engine=dynamic engineCtrl=SO_PATH:/usr/lib/engines/engine_pkcs11.so engineCtrl=ID:pkcs11 engineCtrl=LIST_ADD:1 engineCtrl=LOAD engineCtrl=MODULE_PATH:/usr/lib/opensc-pkcs11.so engineCtrl=INIT --- Problem is, with this setup stunnel does not allow user to enter PIN for the secret key. Instead it tries to get secret key without PIN, 3 times (and then therefore usually blocks card PIN) and retires: ---- Initializing engine 1 Engine 1 initialized PRNG seeded successfully Certificate: mart.pem Certificate loaded Key file: id_01 error queue: 26096080 : error:26096080:engine routines:ENGINE_load_private_key:failed loading private key error queue: 800050A0 : error:800050A0:PKCS11 library:PKCS11_login:PIN incorrect Wrong PIN: retrying error queue: 26096080 : error:26096080:engine routines:ENGINE_load_private_key:failed loading private key error queue: 800050A0 : error:800050A0:PKCS11 library:PKCS11_login:PIN incorrect Wrong PIN: retrying error queue: 26096080 : error:26096080:engine routines:ENGINE_load_private_key:failed loading private key ENGINE_load_private_key: 800050A0: error:800050A0:PKCS11 library:PKCS11_login:PIN incorrect ---- I discovered workaround that is valid form version 4.26 till current 4.34, as follows, NULL-ing the ui_data.method property in ctx.c: --- diff -cr stunnel-4.34/src/ctx.c stunnel-4.34-patched/src/ctx.c *** stunnel-4.34/src/ctx.c 2010-09-14 18:08:43.000000000 +0300 --- stunnel-4.34-patched/src/ctx.c 2010-09-28 21:56:36.219081931 +0300 *************** *** 304,309 **** --- 304,310 ---- UI_method_set_reader(ui_method, pin_cb); #else /* USE_WIN32 */ ui_method=UI_OpenSSL(); + ui_data.section = NULL; #endif /* USE_WIN32 */ if(section->engine) for(i=1; i<=3; i++) { --- After that patch private key loads correctly: --- Initializing engine 1 Engine 1 initialized PRNG seeded successfully Certificate: mart.pem Certificate loaded Key file: id_01 private key loaded --- It would be nice if: * somebody investigates more precisely why the OpenSSL PIN entry is not showing with unpached stunnel * include my or better patch for this situation Thank you very much for excellent piece of software! With best regards, Märt Laak

2 2

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

15 Jun '11

Hi everyone, I'm happily using stunnel for almost 8 years now :) I recently began to use verify=3 and i'm quite disappointed that a succesful access does not appear in the logs unless they are set to quite verbose. To be precise, i think it makes sense, for paranoid setups to keep track of successful accesses to. I'd suggest logging remote end's DN for log level =3 or 4. As there were some improvements lately in verify=3, i hope you could integrate this too. Thanks

2 1

Slow connection to remote stunnel
by Thorsten Kampe 31 May '11

31 May '11

Hi, I'm using stunnel 4.36 on Linux to secure Samba SWAT. When I connect directly to the remot stunnel port with my browser on Windows 7 (https://swat-server:stunnel-port), I get a long delay after entering my credentials (about 60 seconds or so). This seems to be known issue (for instance see "You will be prompted for the Linux root user username and password. There will be a delay of about 60 to 75 seconds with each login."[1].) I did a Wireshark trace and it seems that the server simply does not respond during that time. But when I connect to the local stunnel client (http://localhost:stunnel-port), the SWAT page displays immediately. Is that "normal". How can I get the same speed without a stunnel client? Thorsten [1] <http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_: _Ch10_:_Windows,_Linux,_and_Samba#Test_The_Secure_SWAT_Login>

2 1

stunnel cannot exec SWAT
by Thorsten Kampe 28 May '11

28 May '11

Hi, I'm successfully securing Samba SWAT on Linux with stunnel 4.36. The connection goes like this: browser -> http://localhost:901 (stunnel) -> remote:50901 (xinetd) -> stunnel -> remote:901 (xinetd) -> SWAT. Now I want to remove the xinetd swat file and have stunnel directly call swat: browser -> http://localhost:901 (stunnel) -> remote:50901 (xinetd) -> stunnel -> SWAT I do this by commenting out "connect" and setting exec and execargs (as documented in stunnel's man page): #connect = 901 exec = /usr/sbin/swat execargs = swat Now I get a "Connection closed by remote server" in my browser. The log shows this: [xinetd] START: swat-ssl pid=1026 from=192.168.0.253 [stunnel] Reading configuration from file /etc/stunnel/swat.xconf [stunnel] Could not load DH parameters from /etc/stunnel/stunnel.pem [stunnel] Configuration successful [stunnel] No limit detected for the number of clients [stunnel] stunnel 4.36 on i686-pc-linux-gnu with OpenSSL 1.0.0d 8 Feb 2011 [stunnel] Threading:PTHREAD SSL:ENGINE Auth:LIBWRAP Sockets:POLL, IPv6 [stunnel] Service stunnel accepted connection from 192.168.0.253:60418 [stunnel] SSL accepted: new session negotiated [stunnel] Negotiated ciphers: ECDHE-RSA-AES256-SHA SSLv3 Kx=ECDH Au=RSA Enc=AES(256) Mac=SHA1 [stunnel] connect: Operation now in progress (115) [stunnel] Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket [stunnel] pid=1026 duration=0(sec) [xinetd] EXIT: swat-ssl status=0 pid=1026 duration=0(sec) The successful connection (when xinetd calls swat) looks like this: [xinetd] START: swat-ssl pid=5076 from=192.168.0.253 [everything as above] [stunnel] connect_blocking: connecting 127.0.0.1:901 [xinetd] START: swat pid=5085 from=127.0.0.1 [stunnel] connect_blocking: connected 127.0.0.1:901 [stunnel] Service stunnel connected remote server from 127.0.0.1:47098 [stunnel] SSL_shutdown successfully sent close_notify [stunnel] Connection closed: 288 bytes sent to SSL, 512 bytes sent to socket [xinetd] EXIT: swat status=0 pid=5085 duration=0(sec) [xinetd] EXIT: swat-ssl status=0 pid=5076 duration=0(sec) The only difference I can see is the "connect" in the problem case versus the "connect_blocking" in the success case. Who can shed some light? Thorsten

1 0

stunnel doing client cert authentication?
by Johann Smith 24 May '11

24 May '11

Hi, I have stunnel running as an https server. Can stunnel handle/validate client certificates in this mode? How are authentication details forwarded to the http backend, by additional headers? Thank you! Johann

2 1

During make of stunnel-4.36 on OSX: "str.c:83: error: thread-local storage not supported for this target"
by SciFi 24 May '11

24 May '11

Hello, During make, I suddenly got this, from the stunnel-4.36 tarball: > str.c:83: error: thread-local storage not supported for this target while it was compiling src/str.c . I'm running MacOSX 10.6.7 with Xcode-3.2.6. I always compile for i386 32-bit mode. (The kernel must be in 32-bit mode for this model iMac, even though most tasks will run in 64-bit mode.) The stunnel-4.34 was built and is (still) running fine here. (I must've skipped -4.35 for some reason.) The src/str.c does seem to be a new module in 4.36, however. I configure stunnel this way: $ ./configure \ --enable-dependency-tracking \ --enable-static \ --enable-shared \ --with-ssl=/usr/local/ssl (same configure with 4.34 & 4.36) The configure step found most things, including libwrap etc. They're using the same compiler and other flags etc.: $ $CC --version i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3) […] (I never use a pkg-mgr such as Macports or Fink; besides, they are both now back-level with stunnel.) I'm skeptical in upgrading Xcode to their 4.x series, with Apple's insistence we use the LLVM family there. ;) I'm just a hobbyist, using stunnel to connect Pan to NNTP servers thru their SSL services (including sending this message via Gmane). I am happy with 4.34 in this regard. If it's not too much trouble, though, could someone help further with this problem in 4.36, please? Thank you.

2 4

stunnel4 with exec as service for securing pop3
by Jörg-Volker Peetz 23 May '11

23 May '11

I would like to run the stunnel4 daemon in order to provide a pop3s service by using a pop server (solid-pop3d). The following configuration file doesn't work (the pop3 server doesn't start, I think) and I would like to ask for any hints. --stunnel.conf>>> cert = /etc/stunnel/stunnel4.pem sslVersion = SSLv3 [pop3s] accept = 995 exec = /usr/sbin/solid-pop3d execargs = solid-pop3d <<<stunnel.conf-- I would expect stunnel4 to start up solid-pop3d every time someone connects to port 995 and communicate to solid-pop3d, just like inetd would do, if configured to serve solid-pop3d. By the way, I have opened the service "pop3s" in /etc/hosts.allow. Thanks in advance for any help. -- Best regards, Jörg-Volker.

4 8

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

stunnel-users May 2011