stunnel-users

3 participants
3308 discussions

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

DNS Spoofing
by Happy Manocha 25 May '06

25 May '06

Hello All, >From Website I came to know Stunnel can help in DNS spoofing. Can someone redirect to know how this can be achieved. Stunnel can help: Protect interception of data Prevent manipulation of data And, if compiled with libwrap support: Defend against IP source routing, (one host sending packets as if they came from somewhere else) DNS spoofing (an attacker forging name server records) Regds Happy Manocha

1 0

stunnel + socks v5
by Carlos E. Mansilla G. 25 May '06

25 May '06

I need to know please, if can I accept connections from sock5 clients in stunnel4.. thnx. Carlos Mansilla

1 0

stunnel + socks v5
by Carlos E. Mansilla G. 25 May '06

25 May '06

I need to know please, if can I accept connections from sock5 clients in stunnel4.. thnx. Carlos Mansilla

1 0

libwrap support
by Happy Manocha 24 May '06

24 May '06

Hello All, Can someone throw some light on libwrap support feature of stunnel? What it is and how it can be used? Thanks in advance. Regds Happy Manocha

1 0

Using a signed *.domain.com with ssl - Getting "unable to get local issuer certificate"
by Pritesh Mehta 24 May '06

24 May '06

Hello all, I have had a good hunt around and am having trouble finding a solution. I am using stunnel to provide encrypted pop3 access to our mail server, and we have recently purchased a signed *.XXX.com certificate from godaddy. This has been great since I can use the same cert on all our servers, and this has worked cleanly with the webservices. However, I am having some issues with the stunnel and pop3 service. I am not entirely certain whether it is caused by the *.XXX.com certificate (although I think it unlikely) but was hoping someone more knowledgeable could enlighten me? I currently have stunnel configured thusly: stunnel -f \ -A /etc/stunnel/certs/sf_issuing.pem \ -p /etc/stunnel/certs/wildcard.XXX.com.stunnel.pem \ -r 127.0.0.1:110 Unfortunately my users are getting warnings, and using the openssl client I get: $ openssl s_client -connect mail.XXX.com:995 CONNECTED(00000003) depth=1 /C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./OU=http://www.starfieldtech.com/repository/CN=Starfield Secure Certification Authority/emailAddress=practices(a)starfieldtech.com verify error:num=20:unable to get local issuer certificate verify return:0 --- Certificate chain 0 s:/O=*.XXX.com/OU=Domain Control Validated/CN=*.XXX.com i:/C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./OU=http://www.starfieldtech.com/repository/CN=Starfield Secure Certification Authority/emailAddress=practices(a)starfieldtech.com 1 s:/C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./OU=http://www.starfieldtech.com/repository/CN=Starfield Secure Certification Authority/emailAddress=practices(a)starfieldtech.com i:/L=ValiCert Validation Network/O=ValiCert, Inc./OU=ValiCert Class 2 Policy Validation Authority/CN=http://www.valicert.com//[email protected] --- Server certificate -----BEGIN CERTIFICATE----- [snip] -----END CERTIFICATE----- subject=/O=*.XXX.com/OU=Domain Control Validated/CN=*.XXX.com issuer=/C=US/ST=Arizona/L=Scottsdale/O=Starfield Technologies, Inc./OU=http://www.starfieldtech.com/repository/CN=Starfield Secure Certification Authority/emailAddress=practices(a)starfieldtech.com --- No client certificate CA names sent --- SSL handshake has read 2381 bytes and written 340 bytes --- New, TLSv1/SSLv3, Cipher is AES256-SHA Server public key is 1024 bit Compression: NONE Expansion: NONE SSL-Session: Protocol : TLSv1 Cipher : AES256-SHA Session-ID: 4E550C07BDA9661C4B532A28110E5616549CB9FA72D37E5C979E3C6579F8FB99 Session-ID-ctx: Master-Key: 2E588101AA098463FA40C0353009F5842FA19B1C3D48D9A0000EB2E241EFB70BB10D52FE9BC444344D49653B9FEB25F4 Key-Arg : None Start Time: 1148463445 Timeout : 300 (sec) Verify return code: 20 (unable to get local issuer certificate) --- I am positive this must have been covered before somewhere, but I haven't been able to find anything conclusive. Apologies if I'm covering well trodden ground :) TIA, -- Pritesh Mehta <pmehta(a)gnr.com> Global Name Registry _____________________________________________________ Information contained herein is Global Name Registry Proprietary Information and/or Registry Sensitive Information and is made available to you because of your interest in or affiliation with our company. This information is submitted in confidence and its disclosure to you is not intended to constitute public disclosure or authorization for disclosure to other parties. Should you have received this email and are not an intended recipient, please delete this email in its entirety. Global Name Registry is registered with the Office of the UK Information Commissioner.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

stunnel-users