stunnel-users

stunnel-users@stunnel.org

5 participants
3293 discussions

syslog-ng over stunnel does not work for me
by Christoph Pleger 08 Jun '06

08 Jun '06

Hello, I set up a server and a client machine to test the combination of stunnel and syslog-ng. I followed the instructions in the example at http://www.stunnel.org/examples/syslog-ng.html, but the log messages are not sent correcly. The log on the server says: ****: syslog started ****: syslog connected from ###.###.###.###:51646 ****: SSL state (accept): before/accept initialization ****: SSL_accept: 140B544E: error: 140B544E: SSL routines:SSL_GET_NEW_SESSION:ssl session id callback failed ****: syslog finished (-1 left) The log on the client says: ****: syslog started ****: syslog connected from 127.0.0.1:3524 ****: FD 8 in non-blocking mode ****: syslog connecting ###.###.###.###:514 ****: connect_wait: waiting 10 seconds ****: connect_wait: connected ****: Remote FD=8 initialized ****: SSL state (connect): before/accept initialization ****: SSL state (connect): SSLv3 write client hello A ****: SSL_connect: Peer suddenly disconnected ****: syslog finished (0 left) Please help. Regards Christoph

1 1

Connection Reset by Peer
by Srilalitha Muralidhara(HCL Capital Market Services) 08 Jun '06

08 Jun '06

Hi, My stunnel server is unable to send data correctly to my application running the same machine. This happens when the client is run from windows platform. When client is run from UNIX everything works fine. The Stunnel Server log file says: 2006.06.05 11:54:54 LOG7[23141:8]: rssvr connecting 127.0.0.1:28091 2006.06.05 11:54:54 LOG7[23141:8]: Remote FD=1 initialized 2006.06.05 11:54:54 LOG7[23141:8]: TCP_NODELAY option set on remote socket 2006.06.05 11:54:54 LOG3[23141:8]: SSL_read: Connection reset by peer (131) 2006.06.05 11:54:54 LOG5[23141:8]: Connection reset: 0 bytes sent to SSL, 13 bytes sent to socket 2006.06.05 11:54:54 LOG5[23141:8]: linger (local): Invalid argument (22) 2006.06.05 11:54:54 LOG7[23141:8]: rssvr finished (0 left) ------------------------------------------------------------------------ -------------------------------------------------------------------- Does anybody know the cause of the problem? And hopefully the solution? Thanks Sri Disclaimer: *********** The contents of this E-mail (including the contents of the enclosure(s) or attachment(s) if any) are privileged and confidential material of HCL Capital Market Services and should not be disclosed to, used by or copied in any manner by anyone other than the intended addressee(s). In case you are not the desired addressee, you should delete this message and/or re-direct it to the sender. The views expressed in this E-mail message (including the enclosure(s) or attachment(s) if any) are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of HCL Capital Market Services. This e-mail message including attachment/(s), if any, is believed to be free of any virus. However, it is the responsibility of the recipient to ensure that it is virus free and HCL Capital Market Services is not responsible for any loss or damage arising in any way from its use.

1 0

decryption failed or bad record mac
by Trent Townsend 07 Jun '06

07 Jun '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've emailed about this once already, but am just giving a *little* more info. It seems similar problems with SSL proliferate the web. The problem is below (message from the client and server posted). I thought it may be a bug reported with SSL and zlib (which a fix isn't due out until the next version of OpenSSL). However, I can successfully start up a openssl s_server and talk to it with a s_client, so I think that eliminates OpenSSL. Has anyone seen this before (I'm sure this is the case) and figured it out? Client: SSL_connect: 140943FC: error:140943FC:SSL routines:SSL3_READ_BYTES:sslv3 alert bad record mac Server: SSL_accept: 1408F455: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac I'm using stunnel 4.11 (tried 4.15 also) and Openssl 0.9.8a. Thanks. -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.0.6 (Build 6060) iQA/AwUBRIcbw40HAxBKv2yIEQI5XQCg2ylvhIBlZ57euv9/wu8fM5vI40cAoKKk L2bMgFZDc23T6ED6CGJJn8oy =+PA6 -----END PGP SIGNATURE-----

1 0

RE: [stunnel-users] stunnel error
by Nadav, Erez 07 Jun '06

07 Jun '06

Hi, It seems that the problem occur when the client write large buffers (30-40Kbytes) on each write. Any idea how to solve it Thanks Erez ________________________________ From: stunnel-users-bounces(a)mirt.net [mailto:stunnel-users-bounces@mirt.net] On Behalf Of Nadav, Erez Sent: Wednesday, June 07, 2006 6:00 PM To: stunnel-users(a)mirt.net Subject: [stunnel-users] stunnel error Hi, I use stunnel 4.14 and face this error when performing buffer writes from client to remote side SSL_write: 140D5042: error:140D5042:SSL routines:SSL3_CTRL:called a function you should not call Does anybody know how can I overcome this ??? Thanks Erez ________________________________________________________________________ __________________ This electronic message contains information from Verint Systems, which may be privileged and confidential. The information is intended to be for the use of the individual(s)or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by replying to this email (1). __________________________________________________________________________________________ This electronic message contains information from Verint Systems, which may be privileged and confidential. The information is intended to be for the use of the individual(s)or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by replying to this email (1).

1 0

stunnel error
by Nadav, Erez 07 Jun '06

07 Jun '06

Hi, I use stunnel 4.14 and face this error when performing buffer writes from client to remote side SSL_write: 140D5042: error:140D5042:SSL routines:SSL3_CTRL:called a function you should not call Does anybody know how can I overcome this ??? Thanks Erez __________________________________________________________________________________________ This electronic message contains information from Verint Systems, which may be privileged and confidential. The information is intended to be for the use of the individual(s)or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by replying to this email (1).

1 0

Processing during CRL expiry and refresh
by Nagasundaram, Sekhar 06 Jun '06

06 Jun '06

All: I have 2 questions: 1. Is there a way to have Stunnel continue processing and accepting connections after the CRL expiry? Currently it gives a "revoking all certificates" error and stops accepting connections. 2. Is there a configurable parameter through which we can have the CRL list refresh itself such that 1 above does not happen? Much Thanks in advance.. Sekhar

1 0

unsecure configuration
by Robert Bator 01 Jun '06

01 Jun '06

Hi , I am trying to set up stunnel to accept unsecure calls on port 1001 from inside and secure calls on port 1000 from internet. All calls are forwarded to machin B The configuration like this: secure --> 1000 machine A unsecure --> 1002 machine B unsecure --> 1001 machine A unsecure --> 1002 machine B Is this setup possible i stunnel? PS. I use "stone repeater" and this rules are easy to setup. Best Regards, Robert Bator

1 0

stunnel and bad rsa signature
by Trent Townsend 30 May '06

30 May '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On a test environment, I successfully had stunnel securing MySQL traffic between 2 systems using a verify level of 3. However, with the production system and what I would call an identical setup (albeit with new certificates), I get the following errors (see log below.) The version I'm running of stunnel is 4.11. I saw the "bad rsa signature" message in the server's output, so I regenerated the private key file to be sure I'd used the right one. Everything seems to be in order, but it will not work. Any ideas? Client: 2006.05.30 09:20:21 LOG5[21951:1]: stunnel 4.11 on i686-pc-linux-gnu UCONTEXT+POLL+IPv4+LIBWRAP with OpenSSL 0.9.7a Feb 19 2003 2006.05.30 09:20:21 LOG5[21951:1]: 499 clients allowed 2006.05.30 09:20:25 LOG5[21951:2]: stunnel_mysql connected from 127.0.0.1:32853 2006.05.30 09:20:25 LOG3[21951:2]: SSL_connect: 14094410: error: 14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure 2006.05.30 09:20:25 LOG5[21951:2]: stack_info: size=65536, current=15296 (23%), maximum=15296 (23%) Server: 2006.05.30 09:19:42 LOG7[19964:3086334176]: RAND_status claims sufficient entropy for the PRNG 2006.05.30 09:19:42 LOG6[19964:3086334176]: PRNG seeded successfully 2006.05.30 09:19:42 LOG7[19964:3086334176]: Certificate: /usr/KRB5/ openssl/ssl/private/server.key 2006.05.30 09:19:42 LOG7[19964:3086334176]: Key file: /usr/KRB5/ openssl/ssl/private/server.key 2006.05.30 09:19:42 LOG7[19964:3086334176]: Verify directory set to / usr/KRB5/openssl/ssl/certs 2006.05.30 09:19:42 LOG5[19964:3086334176]: Peer certificate location /usr/KRB5/openssl/ssl/certs 2006.05.30 09:19:42 LOG7[19964:3086334176]: SSL context initialized for service stunnel_mysqld 2006.05.30 09:19:42 LOG5[19964:3086334176]: stunnel 4.15 on i686-pc- linux-gnu with OpenSSL 0.9.7a Feb 19 2003 2006.05.30 09:19:42 LOG5[19964:3086334176]: Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv4 Auth:LIBWRAP 2006.05.30 09:19:42 LOG6[19964:3086334176]: file ulimit = 1022 (can be changed with 'ulimit -n') 2006.05.30 09:19:42 LOG6[19964:3086334176]: poll() used - no FD_SETSIZE limit for file descriptors 2006.05.30 09:19:42 LOG5[19964:3086334176]: 499 clients allowed 2006.05.30 09:19:42 LOG7[19964:3086334176]: FD 4 in non-blocking mode 2006.05.30 09:19:42 LOG7[19964:3086334176]: FD 5 in non-blocking mode 2006.05.30 09:19:42 LOG7[19964:3086334176]: FD 6 in non-blocking mode 2006.05.30 09:19:42 LOG7[19964:3086334176]: SO_REUSEADDR option set on accept socket 2006.05.30 09:19:42 LOG7[19964:3086334176]: stunnel_mysqld bound to 0.0.0.0:606 2006.05.30 09:19:42 LOG7[19964:3086334176]: Created pid file /usr/ local/var/stunnel/stunnel.pid 2006.05.30 09:20:40 LOG7[19964:3086334176]: stunnel_mysqld accepted FD=7 from xxx.xxx.xxx.xxx:32854 2006.05.30 09:20:40 LOG7[19964:3086330800]: stunnel_mysqld started 2006.05.30 09:20:40 LOG7[19964:3086330800]: FD 7 in non-blocking mode 2006.05.30 09:20:40 LOG7[19964:3086330800]: FD 8 in non-blocking mode 2006.05.30 09:20:40 LOG7[19964:3086330800]: FD 9 in non-blocking mode 2006.05.30 09:20:40 LOG7[19964:3086330800]: Connection from xxx.xxx.xxx.xxx:32854 permitted by libwrap 2006.05.30 09:20:40 LOG5[19964:3086330800]: stunnel_mysqld connected from xxx.xxx.xxx.xxx:32854 2006.05.30 09:20:40 LOG7[19964:3086334176]: Cleaning up the signal pipe 2006.05.30 09:20:40 LOG6[19964:3086334176]: Child process 19967 finished with code 0 2006.05.30 09:20:40 LOG5[19964:3086330800]: VERIFY OK: depth=2, ... (Root CA) 2006.05.30 09:20:40 LOG5[19964:3086330800]: VERIFY OK: depth=1, ... (CA) 2006.05.30 09:20:40 LOG5[19964:3086330800]: VERIFY OK: depth=0, ... (client) 2006.05.30 09:20:40 LOG3[19964:3086330800]: error stack: 1408807A : error:1408807A:SSL routines:SSL3_GET_CERT_VERIFY:bad rsa signature 2006.05.30 09:20:40 LOG3[19964:3086330800]: SSL_accept: 4077068: error:04077068:rsa routines:RSA_verify:bad signature 2006.05.30 09:20:40 LOG5[19964:3086330800]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2006.05.30 09:20:40 LOG7[19964:3086330800]: stunnel_mysqld finished (0 left) Thanks. -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.0.6 (Build 6060) iQA/AwUBRHx+bI0HAxBKv2yIEQIJ1wCcCVJ+9ZqXdxWGTBAS8y7ldUv+J4UAn1al ZYIA5gmw38iwsYuE7tG9esAk =ljGb -----END PGP SIGNATURE-----

1 0

Problem getting stunnel to chroot on Suse 10
by Paul Stepowski 29 May '06

29 May '06

Hi list, I'm using stunnel package that comes standard with Suse 10.0 stunnel 4.10 on i686-suse-linux-gnu UCONTEXT+POLL+IPv4+LIBWRAP with OpenSSL 0.9.7g 11 Apr 2005 I can tunnel ports over ssl using stunnel but the chroot directive doesn't seem to be working. E.g. my pid file is being created under / rather than /var/lib/stunnel-syslogng. The other paths in the config file are taken by stunnel as relative to / rather than the chroot directory. What am I missing? Here's my stunnel config. I'm not passing any other flags when running stunnel. ---snip--- client = no #debug = 7 #foreground = yes chroot = /var/lib/stunnel-syslogng setuid = stunnel setgid = nogroup pid = /stunnel.pid #output = stunnel.log socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 #compression = rle #options = DONT_INSERT_EMPTY_FRAGMENTS #verify = 2 #CApath = /certs #CAfile = /certs/stunnel.pem #CRLpath = /crls #CRLfile = /etc/stunnel/crls.pem cert = /var/lib/stunnel-syslogng/certs/stunnel.pem ---snip--- Thanks, Paul

1 0

Re: [stunnel-users] stunnel-4.15 segfaulting and looping under FreeBSD-CURRENT
by Michael Weiser 26 May '06

26 May '06

On Wed, May 17, 2006 at 06:01:37PM +0200, Michael Weiser wrote: > > I'm now retrying with a freshly compiled openssl-0.9.8b to see if that has > > anything to do with anything. > The problem persists with openssl-0.9.8b: > # gdb src/stunnel --core stunnel.core --batch -ex "thread apply all bt > full" -ex "quit" > Core was generated by `stunnel'. > Program terminated with signal 11, Segmentation fault. > #0 0x280d07b5 in SSL_get_peer_certificate () from > ../bin/openssl-0.9.8b/lib/libssl.so.0.9.8 > [New LWP 100077] The problem is triggered by a change to src/client.c in stunnel-4.15. client() now loops over calls to run_client() instead of doing it just once. The first, successful (!) call to run_client() seems to leave the ssl context in an undefined state which makes the following calls to run_client() segfault in the forked child which in turn produces the core file. My guess is, that it's not actually supposed to loop if the call to run_client() is successful. Reverting client.c to roughly 4.14 fixes the problem for me. A patch is attached. Any insights and a more permanent fix would be highly appreciated. BTW: I configured stunnel with --with-threads=pthread. By default, ucontext is detected, which is broken in stunnel-4.14 as well. After finishing, 4.14 hangs in s_poll_wait waiting for -1 seconds on 0 fds (!?). I can provide debugging log and gdb output if needed. -- bye, Michael

1 0

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