- stunnel-users - stunnel.org

:o( Stunnel KO on Windows Server 2003 VM
by BOXI31 TEST 22 Feb '12

22 Feb '12

Hi all ! I'm new with Stunnel. It'a nice tool that works perfectly on Windows 7 64-bit host but won't start on Windows Server 2003 guest VM (VMWare Player 3.1.x). When I try to start it, I have a message like "can't initialize...". I'll give you the exact message tomorrow, I don't have now the VM on hand. On Windows 7, when I started Stunnel for the 1st time, I was asked to create a certificate with a kind of wizard but on the Windows Server 2003 VM, it stops before this step. Is it a known problem on VM ? What could I check ? I managed to make the software I'm testing (SMTP sending function) on the VM "talk" to Stunnel on my host by I'd really like to install it on the VM to be independant from host. Thanks by advance, Regards, Steve.

2 1

Stunnel Not supporting DSA key
by Anand Krishnan 16 Feb '12

16 Feb '12

Hi All, I have query regarding Stunnel (version 4) working. We have a windows client application which communicates with a web service via SSL encryption with DSA algorithm. The windows client machine is using a pfx file for authentication with server. Now we need to convert this windows machine with a linux machine and hence we converted the pfx into pem file. But when i tried to start the Stunnel using this pem file it threws up below error. 2012.02.13 18:23:23 LOG3[23972:47049761923264]: error stack: 140B3009 : error:140B3009:SSL routines:SSL_CTX_use_RSAPrivateKey_file:PEM lib 2012.02.13 18:23:23 LOG3[23972:47049761923264]: SSL_CTX_use_RSAPrivateKey_file: 607907F: error:0607907F:digital envelope routines:EVP_PKEY_get1_RSA:expecting an rsa key It seems the .pem file I mapped in the stunnel.conf is expecting RSA algorithm but when I opened it I can see it as DSA coded. Can some body help me on this. I am attaching the pfx and pem file along with this. Regards, Anand K DISCLAIMER: "The information in this e-mail and any attachment is intended only for the person to whom it is addressed and may contain confidential and/or privileged material. If you have received this e-mail in error, kindly contact the sender and destroy all copies of the original communication. IBS makes no warranty, express or implied, nor guarantees the accuracy, adequacy or completeness of the information contained in this email or any attachment and is not liable for any errors, defects, omissions, viruses or for resultant loss or damage, if any, direct or indirect." DISCLAIMER: "The information in this e-mail and any attachment is intended only for the person to whom it is addressed and may contain confidential and/or privileged material. If you have received this e-mail in error, kindly contact the sender and destroy all copies of the original communication. IBS makes no warranty, express or implied, nor guarantees the accuracy, adequacy or completeness of the information contained in this email or any attachment and is not liable for any errors, defects, omissions, viruses or for resultant loss or damage, if any, direct or indirect."

2 1

Key files across NFS
by James Devine 15 Feb '12

15 Feb '12

I have an stunnel config saved on an NFS mount so it can be shared with other servers, it only seems to work if the key file is stored locally, as soon as I move the key onto the NFS mount I get the error: /disks/disk1/stunnel/certs/wildcard.key: Value too large for defined data type (75) Any idea why that might be and what I might do to fix it?

1 1

server does not send its cert?
by Keresztfalvi Laszlo 14 Feb '12

14 Feb '12

Hello, after a day of trying.. - 2 box of *Win7 Pro x64* - fresh install of *stunnel 4.52* - keys generated with C:\Program Files (x86)\stunnel>* **.\openssl.exe req -new -x509 -days 365 -nodes -config stunnel.cnf -out stunnel.pem -keyout stunnel.pem* - *certs.pem* on both box contains certificate part of stunnel.pem from both machine server stunnel.conf (192.168.0.52): debug = 7 cert = stunnel.pem verify = 2 CAfile = certs.pem options = NO_SSLv2 [unison] accept = 10001 connect = 127.0.0.1:10000 client stunnel.conf (192.168.0.216): client = yes debug = 7 cert = stunnel.pem verify = 2 CAfile = certs.pem options = NO_SSLv2 [unison] client = yes accept = 127.0.0.1:10000 connect = 192.168.0.52:10001 Test #1: *OK* C:\Program Files (x86)\stunnel>* .\openssl verify -CAfile certs.pem stunnel.pem* *stunnel.pem: OK* C:\Program Files (x86)\stunnel>* .\openssl verify -CAfile certs.pem certs.pem* *certs.pem: OK* Test #2: *OK* C:\Program Files (x86)\stunnel> *.\openssl s_server -accept 10001 -cert stunnel.pem -verify 2 -CAfile certs.pem -no_ssl2* vs C:\Program Files (x86)\stunnel> *.\openssl s_client -connect 192.168.0.52:10001 -cert stunnel.pem -verify 2 -CAfile certs.pem -no_ssl2* Test #3: *OK - "certificate accepted" * C:\Program Files (x86)\stunnel> *.\openssl s_server -accept 10001 -cert stunnel.pem -verify 2 -CAfile certs.pem -no_ssl2* vs *stunnel client** * Test #4: *OK - "certificate accepted" * *stunnel server* vs C:\Program Files (x86)\stunnel> *.\openssl s_client -connect 192.168.0.52:10001 -cert stunnel.pem -verify 2 -CAfile certs.pem -no_ssl2* Test #5: *FAILED* *stunnel server* Service unison accepted connection from 192.168.0.216:23134 2012.02.14 09:02:39 LOG3[134028:132792]: SSL_accept: 140943F2: error:140943F2:SSL routines:*SSL3_READ_BYTES:sslv3 alert unexpected message* 2012.02.14 09:02:39 LOG5[134028:132792]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket* * vs *stunnel client * 2012.02.14 09:02:33 LOG5[2500:5876]: Service unison connected remote server from 192.168.0.216:23134 2012.02.14 09:02:33 LOG7[2500:5876]: Remote FD=372 initialized 2012.02.14 09:02:33 LOG3[2500:5876]: SSL_connect: 140870E8: error:140870E8:SSL routines:*SSL3_GET_CERTIFICATE_**REQUEST:tls client cert req with anon cipher* 2012.02.14 09:02:33 LOG5[2500:5876]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket After a *stunnel.conf **reload* on both box (yes, only a reload) then the following details and differences appear: *stunnel server* vs *openssl s_client : OK - "certificate accepted" * 2012.02.14 09:42:02 LOG5[134236:132440]: Service unison accepted connection from 192.168.0.216:23698 2012.02.14 09:42:02 LOG7[134236:132440]: SSL state (accept): before/accept initialization 2012.02.14 09:42:02 LOG7[134236:132440]: SSL state (accept): SSLv3 read client hello B 2012.02.14 09:42:02 LOG7[134236:132440]: SSL state (accept): *SSLv3 write server hello A* 2012.02.14 09:42:02 LOG7[134236:132440]: SSL state (accept): *SSLv3 write certificate A* 2012.02.14 09:42:02 LOG7[134236:132440]: SSL state (accept): *SSLv3 write key exchange A* 2012.02.14 09:42:02 LOG7[134236:132440]: SSL state (accept): SSLv3 write certificate request A 2012.02.14 09:42:02 LOG7[134236:132440]: SSL state (accept): SSLv3 flush data 2012.02.14 09:42:02 LOG7[134236:132440]: Starting certificate verification: depth=0, /C=HU/ST=Mazovia Province/L=Budapest/O=-/OU=client/CN=x-pc 2012.02.14 09:42:02 LOG5[134236:132440]: Certificate accepted: depth=0, /C=HU/ST=Mazovia Province/L=Budapest/O=-/OU=client/CN=x-pc 2012.02.14 09:42:02 LOG7[134236:132440]: SSL state (accept): SSLv3 read client certificate A 2012.02.14 09:42:02 LOG7[134236:132440]: SSL state (accept): SSLv3 read client key exchange A 2012.02.14 09:42:02 LOG7[134236:132440]: SSL state (accept): SSLv3 read certificate verify A 2012.02.14 09:42:02 LOG7[134236:132440]: SSL state (accept): SSLv3 read finished A 2012.02.14 09:42:02 LOG7[134236:132440]: SSL state (accept): SSLv3 write session ticket A 2012.02.14 09:42:02 LOG7[134236:132440]: SSL state (accept): SSLv3 write change cipher spec A 2012.02.14 09:42:02 LOG7[134236:132440]: SSL state (accept): SSLv3 write finished A 2012.02.14 09:42:02 LOG7[134236:132440]: SSL state (accept): SSLv3 flush data *stunnel server* vs *stunnel client : FAILED * *server:* 2012.02.14 09:45:24 LOG5[134236:134552]: Service unison accepted connection from 192.168.0.216:23752 2012.02.14 09:45:24 LOG7[134236:134552]: SSL state (accept): before/accept initialization 2012.02.14 09:45:24 LOG7[134236:134552]: SSL state (accept): SSLv3 read client hello B 2012.02.14 09:45:24 LOG7[134236:134552]: SSL state (accept): *SSLv3 write server hello A* 2012.02.14 09:45:24 LOG7[134236:134552]: SSL state (accept): *SSLv3 write key exchange A* 2012.02.14 09:45:24 LOG7[134236:134552]: SSL state (accept): SSLv3 write certificate request A 2012.02.14 09:45:24 LOG7[134236:134552]: SSL state (accept): SSLv3 flush data 2012.02.14 09:45:24 LOG7[134236:134552]: SSL alert (read): fatal: unexpected_message 2012.02.14 09:45:24 LOG3[134236:134552]: SSL_accept: 140943F2: error:140943F2:SSL routines:*SSL3_READ_BYTES:sslv3 alert unexpected message* 2012.02.14 09:45:24 LOG5[134236:134552]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2012.02.14 09:45:24 LOG7[134236:134552]: Service unison finished (0 left) *client:* 2012.02.14 09:45:18 LOG5[1100:7176]: Service unison connected remote server from 192.168.0.216:23752 2012.02.14 09:45:18 LOG7[1100:7176]: Remote FD=452 initialized 2012.02.14 09:45:18 LOG7[1100:7176]: SSL state (connect): before/connect initialization 2012.02.14 09:45:18 LOG7[1100:7176]: SSL state (connect): SSLv3 write client hello A 2012.02.14 09:45:18 LOG7[1100:7176]: SSL state (connect): *SSLv3 read server hello A* 2012.02.14 09:45:18 LOG7[1100:7176]: SSL state (connect): *SSLv3 read server key exchange A* 2012.02.14 09:45:18 LOG7[1100:7176]: SSL alert (write): *fatal: unexpected_message* 2012.02.14 09:45:18 LOG3[1100:7176]: SSL_connect: 140870E8: error:140870E8:SSL routines:*SSL3_GET_CERTIFICATE_**REQUEST:tls client cert req with anon cipher* 2012.02.14 09:45:18 LOG5[1100:7176]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket Please, give me some clues. Thank you, Laszlo **

3 5

AUTO: Jean Daros is out of the office (returning 02/13/2012)
by Jean Daros 11 Feb '12

11 Feb '12

I am out of the office until 02/13/2012. If you need immediate assistance, please contact the helpdesk at ext. 1540. Thank you. Note: This is an automated response to your message "stunnel-users Digest, Vol 91, Issue 6" sent on 2/11/2012 6:00:01 AM. This is the only notification you will receive while this person is away.

1 0

(no subject)
by Jean Daros 07 Feb '12

07 Feb '12

We are using version 4.33 with RedRock Software - Tutortrac Stunnel will crash. The stunnel service terminated unexpectedly. Faulting application stunnel.exe, veraion 0.0.0.0, faulting module libeay32.dll, version 1.0.0.0 fault address 0x000731ee. Any ideas? -Jean Berkeley College

2 1

Improving SSL security and protecting against the BEAST attack
by Shannon Carver 06 Feb '12

06 Feb '12

Hi all, Long time lurker, but first time poster on the Stunnel mailing list. I'm currently entering into a business partnership with a prominent media group, and as such they've got some strict guidelines by which their partners should abide by when it comes to Security/Encryption, both for brand protection, and making sure that both sides are sufficiently covered (at least from a general scan point of view). Basically the big thing that is coming up in my testing now (predominantly using the Qualysis tool at www.ssllabs.com) is that I'm vulnerable to the BEAST attack, CBC-Mode vulnerabilities and a potential issue of DoS attack due to server accepting Client Side Re-negotiation. I've spent days now trawling the web looking for a solution, but haven't really found anything of use yet, short of disabling CBC Ciphers completely (e.g 'cipher = RC4-SHA:RC4-MD5:!SSLv2:!ADH:!EDH:!EXP:!aNULL:!eNULL:!NULL' or similar), but I fear this me be too restrictive when it comes to client support. I guess my question is, are there other stunnel users who've been in the same situation, and is there a recommended cipher/options list when using Stunnel for HTTPS? Thanks in advance Shannon

1 0

Re: [stunnel-users] No SSL handshake between stunnel in client mode and SSL server
by Michal Trojnara 06 Feb '12

06 Feb '12

On Wednesday, 1 of February 2012, Jose Alf. wrote: > Looks like your client connects for a very short time, sends just 1 byte, > the disconnects. > > Mike can correct me if I am wrong. [cut] > 2012.01.31 12:57:12 LOG6[6748:6808]: SSL connected: new session negotiated [cut] > 2012.01.31 12:57:22 LOG5[6748:6808]: Connection closed: 200 bytes sent to SSL, 1 bytes sent to socket 2012.01.31 12:57:22 As requested: The log says "SSL connected" (as opposed to "SSL accepted"), so this service was configured in client mode, so SSL=server side and socket=client side. 200 bytes sent to SSL were received from socket (i.e. client), and 1 byte sent to socket were received from SSL (i.e. server). Otherwise you are correct. Mike

2 1

No SSL handshake between stunnel in client mode and SSL server
by Denis Berezhnoy 01 Feb '12

01 Feb '12

Hi guys, I have a quick question. I am trying to use stunnel in client mode to encrypt traffic going to my server. Basically, I have a server which listens for SSL connection. And I have a client which can not do SSL but it needs to communicate with server over SSL. I setup stunnel in client mode to accept unecrypted traffic from client and redirect it to server over SSL. I checked TCP traffic with WireShark between stunnel and my server and I can see that there is no SSL handshake, stunnel makes TCP connection with server and sends some TCP packets but I expect to see SSL handshake. My stunnel conf file is here: [Router] client=yes accept = 192.168.1.121:55555 connect = 192.168.160.168:55443 Can you please comment on this? Best regards, Denis

2 5

Possible use-after-free in stunnel 4.52
by David Shaw 01 Feb '12

01 Feb '12

Hello, I am using stunnel 4.52 in client mode with exec and connect. The client program that stunnel execs periodically exits, and is properly re-started by stunnel, as I have "retry = yes" set. However, after a retry, I occasionally get a segfault inside one of the OpenSSL libraries. It does not happen right away, but once it happens, every retry causes the same segfault. I did some debugging and it seems that what is happening during a retry is that the SSL connection is brought down in client_run(), then is freed via SSL_free(c->ssl). However, it seems that c->ssl is used after this free, for example in connect_local(), which calls SSL_get_peer_certificate(c->ssl). When exec, connect, and retry are all set, client_main() will call connect_local() after client_run() exits. This patch seems to resolve the issue: --- client.c.orig 2012-01-11 10:43:33.000000000 -0500 +++ client.c 2012-01-31 18:02:19.155213010 -0500 @@ -162,6 +162,7 @@ if(c->ssl) { /* SSL initialized */ SSL_set_shutdown(c->ssl, SSL_SENT_SHUTDOWN|SSL_RECEIVED_SHUTDOWN); SSL_free(c->ssl); + c->ssl=NULL; ERR_remove_state(0); } For completeness, here's my stunnel.conf: client = yes sslVersion = SSLv3 pid = /var/run/stunnel.pid socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 foreground=yes [experiment] connect = x.x.x.x:443 exec = testprog retry = yes David

2 2