August 2011 - 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

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

05 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

Error detected on socket (read) file descriptor: Broken pipe (32)
by Alex Magee 08 Nov '11

08 Nov '11

Hello, I'm trying to use stunnel to workaround a wine bug which prevents an old Windows mail client from accessing my mail server through a pop3s 995 port. I'm not an expert on linux, stunnel, sockets or ssl. The process seems to start off well, establishes a connection to the correct remote mail server, and negotiates an ssl connection, but then terminates with: Error detected on socket (read) file descriptor: Broken pipe (32) I've played with various settings in the stunnel.conf file, but with no success. A Google search turned up one other example of this problem back in Nov 2010, but no solution was forthcoming. Does anyone have any suggestions of what might be the problem? The level 7 debug stunnel.log file follows at the end, with TCP addresses masked. The system is SUSE Linux 11.4. Using the latest versions of ssl and stunnel. Thanks, Alex stunnel.log -------------- local socket: FD=0 allocated (non-blocking mode) Service pmail-pop3 accepted FD=0 from 127.0.0.1:48828 Service pmail-pop3 started Option TCP_NODELAY set on local socket Service pmail-pop3 accepted connection from 127.0.0.1:48828 remote socket: FD=1 allocated (non-blocking mode) connect_blocking: connecting xxx.xxx.xxx.xxx:995 connect_blocking: s_poll_wait xxx.xxx.xxx.xxx:995: waiting 10 seconds connect_blocking: connected xxx.xxx.xxx.xxx:995 Service pmail-pop3 connected remote server from 192.168.1.47:46187 Remote FD=1 initialized Option TCP_NODELAY set on remote socket SNI: host name: yyy.yyy.yyy..com SSL state (connect): before/connect initialization SSL state (connect): SSLv3 write client hello A SSL state (connect): SSLv3 read server hello A SSL state (connect): SSLv3 read server certificate A SSL state (connect): SSLv3 read server done A SSL state (connect): SSLv3 write client key exchange A SSL state (connect): SSLv3 write change cipher spec A SSL state (connect): SSLv3 write finished A SSL state (connect): SSLv3 flush data SSL state (connect): SSLv3 read finished A 1 items in the session cache 1 client connects (SSL_connect()) 1 client connects that finished 0 client renegotiations requested 0 server connects (SSL_accept()) 0 server connects that finished 0 server renegotiations requested 0 session cache hits 0 external session cache hits 0 session cache misses 0 session cache timeouts SSL connected: new session negotiated Negotiated ciphers: RC4-SHA SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=SHA1 Socket closed on read Sending SSL write shutdown Error detected on socket (read) file descriptor: Broken pipe (32) Connection reset: 79 bytes sent to SSL, 64 bytes sent to socket Service pmail-pop3 finished (0 left) str_stats: 0 block(s), 0 byte(s)

2 2

SSL3_READ_BYTES:tlsv1 alert internal error
by Andrew Heuneman 07 Sep '11

07 Sep '11

Hello, We recently implemented Stunnel on Centos 5.6 for ssl offloading for our java application. The application has applets to communicate java objects over https to a tomcat server on the server side. We have it setup in front of our Alteon/Radware load balancer. This hardware load balancer is capable of ssl load balancing, but has produced a very specific packet reset that only presents itself in ssl processing. We decided to implement Stunnel in front of this load balancer to fix this problem. Ssl offloading was working great with Stunnel until we ran into Java 7. if I run any version of our applets on java 6 they work. If i run java 7 they do not work. I have tried googling and looking for this error but I have only found some references to SNI... is this correct? Is there anything I can do. Please forgive me if i have omitted any details I will be more than happy to include a packet capture or other details if needed. I compiled stunnel with the following options ./configure --disable-libwrap --bindir=/usr/sbin --sbindir=/usr/sbin --sysconfdir=/etc --with-ssl=/usr/local/ssl also i compiled OpenSSL 1.0.0d with the following ./Configure threads shared linux-generic64 stunnel -version No limit detected for the number of clients signal_pipe: FD=3 allocated (non-blocking mode) signal_pipe: FD=4 allocated (non-blocking mode) stunnel 4.42 on x86_64-unknown-linux-gnu platform Compiled/running with OpenSSL 1.0.0d 8 Feb 2011 Threading:PTHREAD SSL:ENGINE Auth:none Sockets:POLL,IPv6 stunnel 4.42 on x86_64-unknown-linux-gnu platform Compiled/running with OpenSSL 1.0.0d 8 Feb 2011 Threading:PTHREAD SSL:ENGINE Auth:none Sockets:POLL,IPv6 Global option defaults debug = daemon.notice pid = /usr/local/var/run/stunnel/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes Service-level option defaults ciphers = ALL:!SSLv2:!aNULL:!EXP:!LOW:-MEDIUM:RC4:+HIGH curve = prime256v1 session = 300 seconds sslVersion = TLSv1 for client, all for server stack = 65536 bytes TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds verify = none str_stats: 112 block(s), 4046 byte(s) stunnel.conf cert=/etc/stunnel/stunnel.pem debug=7 output=/var/log/stunnel.log socket=l:TCP_NODELAY=1 socket=r:TCP_NODELAY=1 [https] accept=0.0.0.0:443 connect=172.16.18.100:80 session = 300 TIMEOUTbusy = 300 TIMEOUTconnect = 10 TIMEOUTidle = 43200 client = no stunnel.log 2011.08.22 16:58:49 LOG7[438154:47689394220768]: Service https accepted FD=2 from 10.0.11.27:46830 2011.08.22 16:58:49 LOG7[438154:1104877888]: Service https started 2011.08.22 16:58:49 LOG7[438154:1104877888]: Option TCP_NODELAY set on local socket 2011.08.22 16:58:49 LOG5[438154:1104877888]: Service https accepted connection from 10.0.11.27:46830 2011.08.22 16:58:49 LOG7[438154:1104877888]: SSL state (accept): before/accept initialization 2011.08.22 16:58:49 LOG7[438154:1104877888]: SSL state (accept): SSLv3 read client hello A 2011.08.22 16:58:49 LOG7[438154:1104877888]: SSL state (accept): SSLv3 write server hello A 2011.08.22 16:58:49 LOG7[438154:1104877888]: SSL state (accept): SSLv3 write certificate A 2011.08.22 16:58:49 LOG7[438154:1104877888]: SSL state (accept): SSLv3 write key exchange A 2011.08.22 16:58:49 LOG7[438154:1104877888]: SSL state (accept): SSLv3 write certificate request A 2011.08.22 16:58:49 LOG7[438154:1104877888]: SSL state (accept): SSLv3 flush data 2011.08.22 16:58:49 LOG7[438154:1104877888]: SSL alert (read): fatal: internal error 2011.08.22 16:58:49 LOG3[438154:1104877888]: SSL_accept: 14094438: error:14094438:SSL routines:SSL3_READ_BYTES:tlsv1 alert internal error 2011.08.22 16:58:49 LOG5[438154:1104877888]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2011.08.22 16:58:49 LOG7[438154:1104877888]: Service https finished (1 left) 2011.08.22 16:58:49 LOG7[438154:1104877888]: str_stats: 0 block(s), 0 byte(s) 2011.08.22 16:59:01 LOG7[438154:1104947520]: Socket closed on read 2011.08.22 16:59:01 LOG7[438154:1104947520]: Sending SSL write shutdown 2011.08.22 16:59:01 LOG7[438154:1104947520]: SSL alert (write): warning: close notify 2011.08.22 16:59:01 LOG6[438154:1104947520]: SSL_shutdown successfully sent close_notify 2011.08.22 16:59:01 LOG7[438154:1104947520]: SSL alert (read): warning: close notify 2011.08.22 16:59:01 LOG7[438154:1104947520]: SSL closed on SSL_read 2011.08.22 16:59:01 LOG7[438154:1104947520]: Sending socket write shutdown 2011.08.22 16:59:01 LOG5[438154:1104947520]: Connection closed: 49445 bytes sent to SSL, 8175 bytes sent to socket -- Thank You, Andrew Heuneman Senior Systems Administrator Reading Plus®/Taylor Associates Helping students become proficient silent readers. <http://twitter.com/readingplus> <http://www.facebook.com/pages/Reading-Plus/165970877038>

2 1

Windows version not starting when Run
by Dayo Akande 31 Aug '11

31 Aug '11

The main thing that I'm seeing as the error is: "Could not load DH parameters from stunnel.pem" Below is the entire log file, I am so stumped here. I appreciate any help. No limit detected for the number of clients make_sockets: s_socket#1: FD=272 allocated (blocking mode) make_sockets: s_socket#2: FD=276 allocated (blocking mode) make_sockets: s_accept: FD=292 allocated (non-blocking mode) stunnel 4.42 on x86-pc-mingw32-gnu platform Compiled/running with OpenSSL 1.0.0d 8 Feb 2011 Threading:WIN32 SSL:ENGINE Auth:none Sockets:SELECT,IPv6 Reading configuration from file stunnel.conf Snagged 64 random bytes from C:/.rnd Wrote 1024 new random bytes to C:/.rnd PRNG seeded successfully Initializing SSL context for service pop3s Certificate: stunnel.pem Certificate loaded Key file: stunnel.pem Private key loaded Could not load DH parameters from stunnel.pem Using hardcoded DH parameters DH initialized with 2048-bit key ECDH initialized with curve prime256v1 SSL options set: 0x01180004 SSL context initialized Initializing SSL context for service imaps Certificate: stunnel.pem Certificate loaded Key file: stunnel.pem Private key loaded Could not load DH parameters from stunnel.pem Using hardcoded DH parameters DH initialized with 2048-bit key ECDH initialized with curve prime256v1 SSL options set: 0x01180004 SSL context initialized Line 91: "socket = l:TCP_NODELAY=1 ": Specified option name is not valid here str_stats: 152 block(s), 11942 byte(s) Server is down

2 2

Re: [stunnel-users] CRL
by Uldis Biks 31 Aug '11

31 Aug '11

1 0

CRL
by Uldis Biks 31 Aug '11

31 Aug '11

2 2

stunnel : binding in ipv6+ipv4 : problem
by Guylhem Aznar 27 Aug '11

27 Aug '11

Hello I have a problem with stunnel : I just don't know how to specify 2 different port forwarding, one for all ipv4 connections to port 443, the other for all ipv6 connections. Either one seem to work, but I can't have both at the same time. In my /etc/hosts : 127.0.0.1 localhost ::1 localhost6 0.0.0.0 listenall4 :: listenall6 In my stunnel.conf: [sslh] accept = listenall4:443 connect = 127.0.0.1:444 TIMEOUTclose = 0 [ssl6] accept = listenall6:443 connect = 6.guylhem.org:80 TIMEOUTclose = 0 I have read that linux can block ipv6 sockets if the ipv4 socket is created first, but here the order doesn't change anything. I though that stunnel was ipv6 capable, but apparently it doesn't play well with ipv4 on the same port. So I tried to remove one of the listenall : the listenall4 is important, but listenall6 is not. Yet giving a AAAA only host like 6.guylhem.org does not help - even if it goes before the listenall4. So I'm stuck. Has anyone patched stunnel for such a situation? Guylhem

1 0

FW: Mysql doesnt run with stunnel
by Freeh Sophia 26 Aug '11

26 Aug '11

Craig Retief <stunnel <at> rsw.co.za> writes: > > I see that on your server you have specified your config for mysqls like > this: > Hi Craig, That fixed it for me. Thanks! Freeh Sophia Marketing GmbH Emanuelstr. 3, 10317 Berlin Deutschland Telefon: +49 (33) 5310967 Email: freehsophia(a)gmail.com Site: http://flug.airego.de/

1 0