- stunnel-users - stunnel.org

Win2k, stunnel & Magic Mail Monitor questions
by Dana Rasmussen 04 Oct '05

04 Oct '05

Hello, I am running Windows 2000. I have recently learned of the stunnel tool. I am using it with Magic Mail Monitor, (MMM). MMM is a POP3 new mail notifier program. MMM allows me to configure a POP3 server by user name, host, password and POP3 port. MMM allows me to have multiple POP3 servers configured. Unfortunately, MMM does not use SSL. I have been able to get MMM to work with stunnel with the following stunnel.conf file: client = yes [MyPOP3SSL] accept=995 connect=mypop3server.com:995 The associated MMM configuration is: user: myuser host: 127.0.0.1 password:mypassword port:995 I would like to be able to add a second POP3 server to MMM, i.e. Gmail. If I add the following to the bottom of the existing stunnel.conf file Gmail POP3SSL access fails. If I add the following to the top of the existing stunnel.conf file the MyPOP3SSL fails but Gmail works. [GmailPOP3SSL] accept=995 connect=pop.gmail.com:995 The additional MMM configuration is: user:mygmail host: 127.0.0.1 password:mygmailpassword port:995 Is there a way to map the MMM configurations to the matching entries in the stunnel.conf file? Thank you, Dana

2 1

Peer suddenly disconnected
by Mark Tabash 03 Oct '05

03 Oct '05

Hello, I'm having problems using stunnel. I would be glad to provide further information upon request. The funny thing is that it was working before I shipped the client pc to the remote location. Nothing has changed since. Here's what I get in the logs: CLIENT: ssmtp accepted FD=8 from 127.0.0.1:32844 FD 8 in non-blocking mode ssmtp started ssmtp connected from 127.0.0.1:32844 FD 9 in non-blocking mode ssmtp connecting 62.21.201.224:465 remote connect #1: EINPROGRESS: retrying waitforsocket: FD=9, DIR=write waitforsocket: ok Remote FD=9 initialized SSL state (connect): before/connect initialization SSL state (connect): SSLv3 write client hello A waitforsocket: FD=9, DIR=read waitforsocket: ok SSL state (connect): SSLv3 read server hello A SSL state (connect): SSLv3 read server certificate A SSL state (connect): SSLv3 read server certificate request A SSL state (connect): SSLv3 read server done A SSL state (connect): SSLv3 write client certificate A SSL state (connect): SSLv3 write client key exchange A SSL state (connect): SSLv3 write certificate verify A SSL state (connect): SSLv3 write change cipher spec A SSL state (connect): SSLv3 write finished A SSL state (connect): SSLv3 flush data waitforsocket: FD=9, DIR=read waitforsocket: ok SSL_connect: Peer suddenly disconnected ssmtp finished (0 left) SERVER: ssmtp accepted FD=8 from 77.34.26.143:32845 FD 8 in non-blocking mode ssmtp started ssmtp connected from 77.34.26.143:32845 SSL state (accept): before/accept initialization SSL state (accept): SSLv3 read client hello A SSL state (accept): SSLv3 write server hello A SSL state (accept): SSLv3 write certificate A SSL state (accept): SSLv3 write certificate request A SSL state (accept): SSLv3 flush data SSL_accept: Peer suddenly disconnected ssmtp finished (0 left) ============================================ CLIENT INFO: stunnel 4.05 on i386-pc-linux-gnu PTHREAD+LIBWRAP with OpenSSL 0.9.7e 25 Oct 2004 Global options cert = /etc/stunnel/stunnel.pem ciphers = ALL:!ADH:+RC4:@STRENGTH debug = 5 key = /etc/stunnel/stunnel.pem pid = /var/run/stunnel4/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes session = 300 seconds verify = none Service-level options TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTidle = 43200 seconds ------------------ SERVER INFO: stunnel 4.09 on x86_64-pc-linux-gnu PTHREAD+POLL+IPv6+LIBWRAP with OpenSSL 0.9.7e 25 Oct 2004 Global options cert = /etc/stunnel/stunnel.pem ciphers = ALL:!ADH:+RC4:@STRENGTH debug = 5 key = /etc/stunnel/stunnel.pem pid = /var/lib/run/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes session = 300 seconds verify = none Service-level options TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds

2 2

Stunnel 4.12 released
by Michal Trojnara 30 Sep '05

30 Sep '05

Here is the ChangeLog entry: Version 4.12, 2005.09.29, urgency: MEDIUM: * New features - Win32 installer added. - New Win32 commandline options: -start and -stop. - Log level and thread number are reported to syslog. - DLLs for OpenSSL 0.9.8. - stunnel.spec updated by neeo <neeo(a)irc.pl>. * Bugfixes - Use of broken poll() is disabled on Mac OS X. - Yet another transfer() infinite loop condition fixed. - Workaround for a serious M$ bug (KB177346). - IPv6 DLLs allocation problem resulting in GPF on W2K fixed. - zlib added to shared libraries (OpenSSL may need it). - size_t printf() fixed in stack_info(). * Release notes - This is a bugfix release. Upgrade is recommended. Homepage: http://stunnel.mirt.net/ Download: ftp://stunnel.mirt.net/stunnel/ sha1sum: 3a0f1b9955f64dcab376b4145663f1eadc5dfba5 stunnel-4.12.tar.gz Best regards, Mike

2 2

Stunnel Win32 binary
by Michal Trojnara 30 Sep '05

30 Sep '05

Dear Users, Some people were asking me for a standalone stunnel.exe file. It's located in stunnel-4.12/src directory of stunnel-4.12.tar.gz archive. Winzip can handle .tar.gz format, so you'll be able to unpack it. http://www.winzip.com/wzdifs.htm BTW: I recommend to try the installer, anyway. It's designed to make the upgrade much easier. You can simply enter the path where your current stunnel.exe and stunnel.conf are located during the install. stunnel.conf and stunnel.pem files won't be replaced and your Windows will remember the path so you won't have to enter it on next upgrade. Also the latest OpenSSL DLLs are installed in stunnel directory each time. Notes: 1. Uninstall removes stunnel.conf, so don't uninstall if you're only going to upgrade stunnel. 2. Remember to stop stunnel before you uninstall/upgrade it. Best regards, Mike

2 2

No encryption?
by Revelancefound＠aol.com 27 Sep '05

27 Sep '05

Dear patient users, It seems that stunnel does not encrypt outward traffic from my pc. I was able to get stunnel to work in the first place by having different proxies for each protocol. However, to test if my 8196 bit + x509 certificate keys actually encrypted my traffic I decided to do a test. I had sniffed my own computer using Cain and Able while logging in to my home router. To my disappointment, the sniffer picked up my username and password in plain text through HTTP protocol several times. Either that or Able can crack 256bit level encryption (256 x 32 = 8196) rather quickly. My stunnel.conf file: ; Sample stunnel configuration file by Michal Trojnara 2002-2005 ; Some options used here may not be adequate for your particular configuration ; Certificate/key is needed in server mode and optional in client mode cert = C:\Program Files\stunnel\stunnel.pem key = C:\Program Files\stunnel\stunnel.pem ; Some performance tunings socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 ; Workaround for Eudora bug options = DONT_INSERT_EMPTY_FRAGMENTS ; Authentication stuff ;verify = 2 ; Don't forget to c_rehash CApath; CApath is located inside chroot jail: ;CApath = certs ; It's often easier to use CAfile: ;CAfile = certs.pem ; Don't forget to c_rehash CRLpath; CRLpath is located inside chroot jail: ;CRLpath = crls ; Alternatively you can use CRLfile: ;CRLfile = crls.pem ; Some debugging stuff useful for troubleshooting ;debug = 7 ;dutput = C:\Program Files\stunnel\stunnel.log ; Use it for client mode client = yes ; Service-level configuration client = yes verify = 0 ;[pop3s] ;accept = 995 ;connect = 110 ;[imaps] ;accept = 993 ;connect = 143 [ssmtp] accept = 127.0.0.1:465 connect = httpsupportingproxy4:3124 TIMEOUTclose = 0 [http] accept = 127.0.0.1:444 connect = httpsupportingproxy3:6588 TIMEOUTclose = 0 [https] accept = 127.0.0.1:443 connect = httpsupportingproxy2:6588 TIMEOUTclose = 0 [ftps] accept = 127.0.0.1:21 connect = httpsupportingproxy1:6588 TIMEOUTclose = 0 ; vim:ft=dosini And my bat file used to generate keys: openssl req -new -x509 -days 365 -nodes -config C:\OpenSSL\bin\openssl.cnf -out stunnel.pem -keyout stunnel.pem ;requirements: ;OpensSSL.exe in C:\windows directory ;Installation of Win32OpenSSL-v0.9.8.mis to C:\ ;Edit C:\OpenSSL\bin\openssl.cnf strings ;[ req ] ;default_bits = 8196 ;default_keyfile = stunnel.pem ;distinguished_name = req_distinguished_name ;attributes = req_attributes ;x509_extensions = v3_ca # The extentions to add to the self signed cert Cain Log: ================================================================== = Cain's MAC Scanner/Promiscuous-mode Detector = ================================================================== IP Address: (Router) MAC Address: (RouterMAC) OUI Fingerprint: Cisco-Linksys, LLC Hostname: ARP Test (Broadcast 31-bit): * ARP Test (Broadcast 16-bit): * ARP Test (Broadcast 8-bit): * ARP Test (Group bit): * ARP Test (Multicast group 0): * ARP Test (Multicast group 1): * ARP Test (Multicast group 3): * Am I doing something wrong here?

3 2

question about usage of configfile
by Revelancefound＠aol.com 26 Sep '05

26 Sep '05

To put it blatantly, I am trying to make stunnel 4.12 create a 2 way encrypted channel from my home computer as a client to an SSL supporting proxy (HTTP). Also, I am using localhost (127.0.0.1) as a connect address for proxy settings in such programs as Internet Explorer or a download manager. A sample of my stunnel.conf is bellow: client = yes verify = 0 [https] accept = 127.0.0.1:8080 connect = ssl.supporting.httpproxy.with.openport:80 TIMEOUTclose = 0 ; vim:ft=dosini My computer currently has the following installed: stunnel-4.12 Opensslv0.9.8 (Win32OpenSSL-v0.9.8.exe) ActivePerl-5.8.7.813-MSWin32-x86-148120.msi Windows XP Home Edition (SP2) Whenever I try to connect to 127.0.0.1:8080 the stunnel log reports 2005.09.23 20:57:33 LOG5[6012:5668]: stunnel 4.12 on x86-pc-mingw32-gnu WIN32+IPv6 with OpenSSL 0.9.8 05 Jul 2005 2005.09.23 20:57:33 LOG5[6012:4600]: No limit detected for the number of clients 2005.09.23 20:57:38 LOG5[6012:1560]: https connected from 127.0.0.1:3226 2005.09.23 20:59:10 LOG5[6012:5396]: https connected from 127.0.0.1:3232 2005.09.23 21:04:10 LOG5[6012:4576]: https connected from 127.0.0.1:3249 2005.09.23 21:09:10 LOG5[6012:4652]: https connected from 127.0.0.1:3268 2005.09.23 21:14:10 LOG5[6012:5396]: https connected from 127.0.0.1:3283 2005.09.23 21:19:12 LOG5[6012:1556]: https connected from 127.0.0.1:3296 2005.09.23 21:24:13 LOG5[6012:4072]: https connected from 127.0.0.1:3309 2005.09.23 21:29:23 LOG3[6012:3408]: Failed to initialize remote connection 2005.09.23 21:29:23 LOG5[6012:6140]: https connected from 127.0.0.1:3332 And so on into infinity Am I trying to do the impossible, or are all those 8196 bit RSA keys (certified through x508) that I generated going to waste?

2 1

stunnel for dovecot
by dhaval thakar 26 Sep '05

26 Sep '05

dear friends, i m preparing for RHCE Exam, as dovecot can not be configured in host.deny (TCP wrappers), we can create tunnel using stunnel & can use for the security perpose. kindly help me blocking pop3 access using host.deny file (using dovecot for the pop3) thanks in advance

2 1

minor annoyance
by Alaric Dailey 26 Sep '05

26 Sep '05

I have been using stunnel for a while with great success, only one minor issue, I am using stunnel for my http server and it ALWAYS logs traffic as coming from the stunnel IP rather than the IP address it is really coming from, is there a way around this?

3 5

RE: [stunnel-users] newbie stunnel question
by Revelancefound＠aol.com 25 Sep '05

25 Sep '05

no data is being transfered, thats the problem 2005.09.24 09:41:19 LOG5[1672:3268]: stunnel 4.11 on x86-pc-mingw32-gnu WIN32+IPv6 with OpenSSL 0.9.7f 22 Mar 2005 2005.09.24 09:41:20 LOG5[1672:2716]: No limit detected for the number of clients 2005.09.24 09:41:33 LOG5[1672:3576]: http connected from 127.0.0.1:1876 2005.09.24 09:42:18 LOG5[1672:1176]: http connected from 127.0.0.1:1881 2005.09.24 09:42:35 LOG5[1672:1408]: http connected from 127.0.0.1:1884 2005.09.24 09:42:44 LOG5[1672:1028]: http connected from 127.0.0.1:1887 And so on until Failed to initialize remote connection My config file: client = yes cert=c:\stunnel\stunnel.pem [http] accept = 127.0.0.1:80 connect = httpsupportingsslserver:80 [https] accept = 127.0.0.1:443 connect = httpsupportingsslserver:80 [ftp] accept = 127.0.0.1:22 connect = httpsupportingsslserver:80 Am I missing something here?

2 1

newbie stunnel question
by Revelancefound＠aol.com 24 Sep '05

24 Sep '05

Hello, im new to stunnel 4.11 and I am currently having trouble creating ssl conncetions. My operating sysytem in Windows XP Home (SP2), I am running Stunnel not as a service and I do not have CERT nor chroot. I am trying to create a SSL tunnel from my pc (stunnel in client mode) to a SSL supporting proxy that does not spill my ip. Because I am using windows I have to edit the stunnel.conf file, its contense is displayed here: client = yes cert=c:\stunnel\stunnel.pem [http] accept = 127.0.0.1:3900 connect = 200.114.206.192:8080 [https] accept = 127.0.0.1:3900 connect = 200.114.206.192:8080 [ftp] accept = 127.0.0.1:3900 connect = 200.114.206.192:8080 After these values are estabolished an netstat -an shows Proto Local Address Foreign Address State TCP 127.0.0.1:3900 0.0.0.0:0 LISTENING Can someone please help me? Attachment:

3 3

stunnel >= 4.0.7 crashes on IPv6 enabled Windows 2000
by Peter Bieringer 24 Sep '05

24 Sep '05

Hi, 4.0.6 claim about "The procedure entry point freeaddrinfo could not be located in the dynamic link library WS2_32.DLL" 4.0.7 and above crashes "...has generated errors". Windows 2000 is IPv6 enabled by <http://msdn.microsoft.com/downloads/sdks/platform/tpipv6.asp> with information from: <http://msdn.microsoft.com/downloads/sdks/platform/tpipv6/faq.asp> Is it planned to fix this issue? BTW: IPv6 enabled 4.0.11 works fine on Linux ! Peter -- Dr. Peter Bieringer http://www.bieringer.de/pb/ GPG/PGP Key 0x958F422D mailto: pb at bieringer dot de Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/

2 3

Re: stunnel-users Digest, Vol 14, Issue 7
by mxrtmxd72＠att.net 22 Sep '05

22 Sep '05

Thanks Michael. -------------- Original message ---------------------- From: stunnel-users-request(a)mirt.net > Send stunnel-users mailing list submissions to > stunnel-users(a)mirt.net > > To subscribe or unsubscribe via the World Wide Web, visit > http://stunnel.mirt.net/mailman/listinfo/stunnel-users > or, via email, send a message with subject or body 'help' to > stunnel-users-request(a)mirt.net > > You can reach the person managing the list at > stunnel-users-owner(a)mirt.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of stunnel-users digest..." > > > Today's Topics: > > 1. Help Installing Stunnel After Reformat Drive (mxrtmxd72(a)att.net) > 2. Re: Help Installing Stunnel After Reformat Drive (Michal Trojnara) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 21 Sep 2005 20:21:03 +0000 > From: mxrtmxd72(a)att.net > Subject: [stunnel-users] Help Installing Stunnel After Reformat Drive > To: stunnel-users(a)mirt.net (stunnel-users) > Message-ID: > > <092120052021.21511.4331C0AE000BE230000054072160376316CDC90B98039B9D9803(a)att.net > > > > > I have been using Stunnel with Agent versioin 3. My system recently crashed and > I had to re-format the hard drive, reinstall Windows XP, and reinstall my apps. > I have followed the directions at wurd.com/cl_ssl_stunnel.php#Windows. > Fortunately, I had backups of the required files. > > I placed libeay32.dll, libssl32.dll, stunnel-4.10.exe, and stunnel.conf in > C:\Stunnel. > > I placed a shortcut on the desktop which points to C:\Batch\runagent.bat. > > C:\Batch\runagent.bat consists of the following line: > c:\batch\runagent.cmd > > c:\batch\runagent.cmd consists of the following lines: > net start stunnel > "C:\Program Files\Agent\agent.exe" > net stop stunnel > > There is also a desktop shortcut which points to C:\Stunnel\stunnel-4.10.exe. > > When I place a pause command following the net start stunnel line in > runagent.cmd a message appears: The service name is invalid. > > The WURD document seems to imply that it is not necessary to run stunnel-410.exe > -install unless you want Stunnel to run all the time. Am I missing something? > I don't remember exactly how I made this work when I first installed it before > my system crashed. > > Any assistance would be gratefully appreciated. Thanks. > > Mort Middleman > > > > > > > Print. > Move to folder: > > > > ------------------------------ > > Message: 2 > Date: Thu, 22 Sep 2005 10:05:51 +0200 > From: "Michal Trojnara" <Michal.Trojnara(a)mobi-com.net> > Subject: Re: [stunnel-users] Help Installing Stunnel After Reformat > Drive > To: "stunnel-users" <stunnel-users(a)mirt.net> > Message-ID: <001401c5bf4c$823b6f00$df66a8c0@DT1518000186> > Content-Type: text/plain; format=flowed; charset="iso-8859-2"; > reply-type=original > > Mort Middleman <mxrtmxd72(a)att.net> wrote: > > net start stunnel > [cut] > > The WURD document seems to imply that it is not necessary to run > > stunnel-410.exe > > -install unless you want Stunnel to run all the time. Am I missing > > something? > > Yes. You need to install a service in order to start it. 8-) > You can change Startup Type in your Control Panel/Services so stunnel > service is not started automatically. > > BTW: Stunnel 4.12 is going to be released with a Windows installer, so users > won't have to maually copy the dlls. 8-) > You could try a prerelease here: > ftp://ftp.mirt.net/stunnel/stunnel-4.12rc1-installer.exe > > Best regards, > Mike > > > > ------------------------------ > > _______________________________________________ > stunnel-users mailing list > stunnel-users(a)mirt.net > http://stunnel.mirt.net/mailman/listinfo/stunnel-users > > > End of stunnel-users Digest, Vol 14, Issue 7 > ********************************************

1 0

Help Installing Stunnel After Reformat Drive
by mxrtmxd72＠att.net 22 Sep '05

22 Sep '05

I have been using Stunnel with Agent versioin 3. My system recently crashed and I had to re-format the hard drive, reinstall Windows XP, and reinstall my apps. I have followed the directions at wurd.com/cl_ssl_stunnel.php#Windows. Fortunately, I had backups of the required files. I placed libeay32.dll, libssl32.dll, stunnel-4.10.exe, and stunnel.conf in C:\Stunnel. I placed a shortcut on the desktop which points to C:\Batch\runagent.bat. C:\Batch\runagent.bat consists of the following line: c:\batch\runagent.cmd c:\batch\runagent.cmd consists of the following lines: net start stunnel "C:\Program Files\Agent\agent.exe" net stop stunnel There is also a desktop shortcut which points to C:\Stunnel\stunnel-4.10.exe. When I place a pause command following the net start stunnel line in runagent.cmd a message appears: The service name is invalid. The WURD document seems to imply that it is not necessary to run stunnel-410.exe -install unless you want Stunnel to run all the time. Am I missing something? I don't remember exactly how I made this work when I first installed it before my system crashed. Any assistance would be gratefully appreciated. Thanks. Mort Middleman Print. Move to folder:

2 1

RE: [stunnel-users] Access to a daemon that has SSL abilities
by Amiram Oren 15 Sep '05

15 Sep '05

10x for the quick reply Alaric! Just want to see if I fully understand your note.. You set the stunnel daemon (/application) on a certain client machine. (let's say you have an IMAP client on it) Then, you configure your Argosoft server, which is set on another machine, to listen to SSL communication (i.e. IMAPS). Is this correct? Cheers, Oren. -----Original Message----- From: Alaric Dailey [mailto:alaricd@pengdows.com] Sent: Wednesday, September 14, 2005 7:44 PM To: Amiram Oren; stunnel-users(a)mirt.net Subject: Re: [stunnel-users] Access to a daemon that has SSL abilities Amiram Oren wrote: > Hi. > > Can I use stunnel only on a client side, in case on the other side, > the server already supports SSL? > > Will this work for SPOP3 and SMTP\S? > > 10X! > > Oren Amiram > >ilman/listinfo/stunnel-users > > I use it on my Argosoft email server to support IMAP, pop3 and HTTP with SSL onWindows 2003 yet :) - ______________________________________________________________________ This email message has been scanned by PineApp Mail-Secure and has been found clean.

2 1

Failed to initialize remote connection
by stunnel-users＠tinfoil.cotse.net 15 Sep '05

15 Sep '05

Hello I am running the Win32 binaries, v4.11, and up to now, they were working fine, as had all the 4.x versions before. But now my http connection will not work; it says "Failed to initialize remote connection". 2005.09.14 22:50:04 LOG3[2500:1492]: Failed to initialize remote connection 2005.09.14 22:50:06 LOG3[2500:1608]: Failed to initialize remote connection Please can anyone advice me what is wrong and how to put this right? Thanks.

1 0

Re: stunnel-4.11 stable?
by Serge Marigold 14 Sep '05

14 Sep '05

FYI, I'm trying to make a case so that my employer will feel some degree of comfort if we deploy it. Is there any other commercial entity that uses this version (4.11) of stunnel. Thanks

1 0

stunnel-4.11 patch for multiple certificates
by Nick Tolomiczenko 14 Sep '05

14 Sep '05

Hi stunnel users, I placed a patch to stunnel-4.11 that will enable it to handle multiple certificates. It is currently awaiting moderator approval. For those who can't wait, please contact myself, Nick Tolomiczenko, or Shem Ali below. Here's the description of what it does: This patch addresses the need for service-level ssl contexts. In particular, the following options which were only available as global options may now be used at the service level: cert, key, CApath, CAfile, ciphers, CRLpath, CRLfile, options, client and verify. If any of these options are used in a service section, stunnel will override its global setting -- if it exists -- and initialize a separate ssl context for the service. On the other hand, for those services that do not specify any of these options, stunnel will fall back on what was specified in the global section of the configuration file and intialize a "common" ssl context for those services. Note: If all services each specified at least one the the above ssl options, then the no "common" ssl context will be initialized since each service will have its own. In this case, it's still a good idea to put common default ssl options in the global section as each service will inherit these settings even if the service initializes its own ssl context. Brought to you by: Nick Tolomiczenko: nick(a)renderquest.com or nick(a)neikos.com Shem Ali: shem(a)renderquest.com

1 0

stunnel-4.11 patch for multiple certificates
by Nick Tolomiczenko 14 Sep '05

14 Sep '05

This patch addresses the need for service-level ssl contexts. In particular, the following options which were only available as global options may now be used at the service level: cert, key, CApath, CAfile, ciphers, CRLpath, CRLfile, options, client and verify. If any of these options are used in a service section, stunnel will override its global setting -- if it exists -- and initialize a separate ssl context for the service. On the other hand, for those services that do not specify any of these options, stunnel will fall back on what was specified in the global section of the configuration file and intialize a "common" ssl context for those services. Note: If all services each specified at least one the the above ssl options, then the no "common" ssl context will be initialized since each service will have its own. In this case, it's still a good idea to put common default ssl options in the global section as each service will inherit these settings even if the service initializes its own ssl context. Brought to you by: Nick Tolomiczenko: nick(a)renderquest.com or nick(a)neikos.com Shem Ali: shem(a)renderquest.com

1 0

Access to a daemon that has SSL abilities
by Amiram Oren 14 Sep '05

14 Sep '05

Hi. Can I use stunnel only on a client side, in case on the other side, the server already supports SSL? Will this work for SPOP3 and SMTP\S? 10X! Oren Amiram

2 1

stunnel-4.11 stable?
by Serge Marigold 13 Sep '05

13 Sep '05

Hi, Is anyone using stunnel-4.11 in a heavily trafficed production environment?

1 0

4.10 stable?
by conover＠rahul.net 09 Sep '05

09 Sep '05

Stunnel 4.10 has gzip compression, right? Is it stable? Thanks, John -- John Conover, conover(a)rahul.net, http://www.johncon.com/

1 0

[BUG] Stunnel 4.10 + xinetd : Connection reset by peer
by Eric Piel 02 Sep '05

02 Sep '05

Hello, I've upgraded to stunnel 4.10 yesterday and since this time I can't managed to get stunnel working with xinetd. I try to access a CVS server with ssl encryption. If stunnel is started as stand-alone, it works as before, but when it's started by xinetd all I get is: cvs [update aborted]: reading from server: Connection reset by peer I've attached the connection logs with 4.09 and 4.10 as well as my configuration file (which used to work for more than a year). My xinetd is version 2.3.13 (and I haven't changed it for several months). Please, let me know if I'm overlooking at something or if I can try anything to debug more in depth... Thanks in advance, Eric PS: actually the CVS is accesible from outside, so you might want to try yourself! # Sample stunnel configuration file # Copyright by Michal Trojnara 2002 setuid = root setgid = root # Authentication stuff verify = 2 CAfile = /etc/ssl/stunnel/lifl-cvs.pem # Use it for client mode client = yes #debug = 7 #output = /home/eric/busy/stunnel.log connect = cvs.lifl.fr:2405

4 5

Re: Flyspray task #7 - CRLfile is never refreshed
by Kartik Subbarao 27 Aug '05

27 Aug '05

I wanted to follow up on this. Flyspray did not let me add a comment since the bug is closed, so I'm posting to the mailing list. 1. I tried using CRLpath (and setting up the symbolic link properly to the hashed value), but that had the same behavior as CRLfile. It only reads the actual CRL once. If I update the file on disk, it never re-reads the file. So I don't see how this is a workaround. Am I missing something? 2. As I mentioned in my initial report, it is a significant disruption for existing stunnel processes to be killed. If it were possible just to kill the main daemon without also killing the child processes (i.e. like sshd), that could be a workaround. But currently, killing the main stunnel process also kills all child stunnel processes. I guess I don't understand what else one could do in this situation, apart from having the application properly reread the CRL on a regular basis. (OCSP is not yet available). When you say that "that's how openssl works", are you saying that the API does not allow you to reread/reload the CRL file? That seems rather odd. It seems like there should be some kind of way to refresh the OpenSSL data structures that store the CRL. Any thoughts/suggestions would be appreciated. Thanks, -Kartik Michal.Trojnara(a)mirt.net wrote: > Notice from stunnel > > Michal Trojnara (mtrojnar) has closed the following task. You are > receiving this because you are on the notification list. > > Task #7: CRLfile is never refreshed > The reason for closing is: Not a bug > That's how OpenSSL work. There are two workarounds: > 1. Use CRLpath instead of CRLfile (I recommend it). > 2. Restart stunnel after the CRL file modification. > > You can get more information about this task at the following URL: > http://stunnel.mirt.net/flyspray/index.php?do=details&id=7 > >

1 0

[stunnel patch] updated transparent proxy on linux 2.6 using cttproxy patch
by MAtteo HCE Valsasna 26 Aug '05

26 Aug '05

hello folks, here comes an improved version of the transparent proxy patch, basically solving the previous TODO issues. please try it if you are interested in transparent stunnel. any feedback il welcome. the code is heavly based on the examples distributed along with the cttproxy patch, many thanks to Balzs Scheidler for its great work and to Lennert Buytenhek for the skaidrus example program. this code is (re)distributed under the GPL version 2 MAtteo ---README--- cttproxy patch to stunnel MAtteo HCE Valsasna (matteo dot valsasna at uninsubria dot it) based on example code in cttproxy patch ports stunnel transparent proxy to cttproxy kernel patch allow stunnel server to connect to the application server faking the stunnel client's IP source address. the server sees connections coming from the stunnel client's IP address instead of that of the stunnel server, and thus can apply admission control, bandwidth control, logging policies as if the client connected directly. should work 2.4 and 2.6 kernels and 2.0.x cttproxy patch tested with kernel 2.6.12.5 and cttproxy-2.6.12-2.0.2 patch setup: * application server(s): here run the application(s) you want to access trough stunnel must route all traffic, or at least all traffic for transproxyed connections, trough the stunnel server * stunnel server: must not be the same host as the application server grab recent kernel source patch your kernel source with the appropriate cttproxy patch (from http://www.balabit.com/products/oss/tproxy/) configure kernel with: CONFIG_IP_NF_TPROXY=m CONFIG_IP_NF_MATCH_TPROXY=m CONFIG_IP_NF_TARGET_TPROXY=m make and install kernel reboot and choose patched kernel load tproxy kernel modules # modprobe iptable_tproxy # modprobe ipt_tproxy enable ip forwarding (this must act as a router) # echo 1 > /proc/sys/net/ipv4/ip_forward grab stunnel source and extract it $ tar xzf stunnel-4.11.tar.gz patch it $ patch -p0 < cttproxy.patch configure selecting tproxy support $ ./configure --enable-tproxy make and install $ make # make install run stunnel in server mode with transparent = yes remote = <application server>:<port> in conf file * stunnel client run plain stunnel, client = yes remote = stunnel server * application client may or may not be the same host as the stunnel client connect to stunnel client to talk securely to application server ---PATCH---diff -crb /tmp/stunnel-4.11/configure stunnel-4.11/configure *** /tmp/stunnel-4.11/configure 2005-07-09 23:00:44.000000000 +0200 --- stunnel-4.11/configure 2005-08-25 16:59:57.000000000 +0200 *************** *** 463,469 **** # include <unistd.h> #endif" ! ac_subst_vars='SHELL PATH_SEPARATOR PACKAGE_NAME PACKAGE_TARNAME PACKAGE_VERSION PACKAGE_STRING PACKAGE_BUGREPORT exec_prefix prefix program_transform_name bindir sbindir libexecdir datadir sysconfdir sharedstatedir localstatedir libdir includedir oldincludedir infodir mandir build_alias host_alias target_alias DEFS ECHO_C ECHO_N ECHO_T LIBS INSTALL_PROGRAM INSTALL_SCRIPT INSTALL_DATA CYGPATH_W PACKAGE VERSION ACLOCAL AUTOCONF AUTOMAKE AUTOHEADER MAKEINFO install_sh STRIP ac_ct_STRIP INSTALL_STRIP_PROGRAM mkdir_p AWK SET_MAKE am__leading_dot AMTAR am__tar am__untar build build_cpu build_vendor build_os host host_cpu host_vendor host_os CC CFLAGS LDFLAGS CPPFLAGS ac_ct_CC EXEEXT OBJEXT DEPDIR am__include am__quote AMDEP_TRUE AMDEP_FALSE AMDEPBACKSLASH CCDEPMODE am__fastdepCC_TRUE am__fastdepCC_FALSE EGREP LN_S ECHO AR ac_ct_AR RANLIB ac_ct_RANLIB CPP CXX CXXFLAGS ac_ct_CXX CXXDEPMODE am__fastdepCXX_TRUE am__fastdepCXX_FALSE CXXCPP F77 FFLAGS ac_ct_F77 LIBTOOL ssldir RANDOM_FILE USE_DH USE_IPv6 LIBOBJS LTLIBOBJS' ac_subst_files='' # Initialize some variables set by options. --- 463,469 ---- # include <unistd.h> #endif" ! ac_subst_vars='SHELL PATH_SEPARATOR PACKAGE_NAME PACKAGE_TARNAME PACKAGE_VERSION PACKAGE_STRING PACKAGE_BUGREPORT exec_prefix prefix program_transform_name bindir sbindir libexecdir datadir sysconfdir sharedstatedir localstatedir libdir includedir oldincludedir infodir mandir build_alias host_alias target_alias DEFS ECHO_C ECHO_N ECHO_T LIBS INSTALL_PROGRAM INSTALL_SCRIPT INSTALL_DATA CYGPATH_W PACKAGE VERSION ACLOCAL AUTOCONF AUTOMAKE AUTOHEADER MAKEINFO install_sh STRIP ac_ct_STRIP INSTALL_STRIP_PROGRAM mkdir_p AWK SET_MAKE am__leading_dot AMTAR am__tar am__untar build build_cpu build_vendor build_os host host_cpu host_vendor host_os CC CFLAGS LDFLAGS CPPFLAGS ac_ct_CC EXEEXT OBJEXT DEPDIR am__include am__quote AMDEP_TRUE AMDEP_FALSE AMDEPBACKSLASH CCDEPMODE am__fastdepCC_TRUE am__fastdepCC_FALSE CPP LN_S RANLIB ac_ct_RANLIB EGREP ECHO AR ac_ct_AR CXX CXXFLAGS ac_ct_CXX CXXDEPMODE am__fastdepCXX_TRUE am__fastdepCXX_FALSE CXXCPP F77 FFLAGS ac_ct_F77 LIBTOOL ssldir RANDOM_FILE USE_DH USE_IPv6 USE_TPROXY LIBOBJS LTLIBOBJS' ac_subst_files='' # Initialize some variables set by options. *************** *** 1037,1042 **** --- 1037,1043 ---- --disable-rsa Disable RSA support --enable-dh Enable DH support --enable-ipv6 Enable IPv6 support + --enable-tproxy Enable linux 2.6 tproxy patch support --disable-libwrap Disable TCP wrappers library support Optional Packages: *************** *** 23166,23171 **** --- 23344,23367 ---- fi; + # use linux 2.[46] tproxy patch + echo "$as_me:$LINENO: checking whether to enable transparent proxyng using linux 2.46 tproxy patch" >&5 + echo $ECHO_N "checking whether to enable transparent proxyng using linux 2.46 tproxy patch... $ECHO_C" >&6 + # Check whether --enable-tproxy or --disable-tproxy was given. + if test "${enable_tproxy+set}" = set; then + enableval="$enable_tproxy" + echo "$as_me:$LINENO: result: yes" >&5 + echo "${ECHO_T}yes" >&6; cat >>confdefs.h <<\_ACEOF + #define USE_TPROXY 1 + _ACEOF + + else + echo "$as_me:$LINENO: result: no" >&5 + echo "${ECHO_T}no" >&6 + + fi; + + # Disable use of libwrap (TCP wrappers) # it should be the last check! echo "$as_me:$LINENO: checking whether to disable TCP wrappers library support" >&5 *************** *** 23987,23992 **** --- 24184,24190 ---- s,@RANDOM_FILE@,$RANDOM_FILE,;t t s,@USE_DH@,$USE_DH,;t t s,@USE_IPv6@,$USE_IPv6,;t t + s,@USE_TPROXY@,$USE_TPROXY,;t t s,@LIBOBJS@,$LIBOBJS,;t t s,@LTLIBOBJS@,$LTLIBOBJS,;t t CEOF diff -crb /tmp/stunnel-4.11/configure.ac stunnel-4.11/configure.ac *** /tmp/stunnel-4.11/configure.ac 2005-07-09 22:58:05.000000000 +0200 --- stunnel-4.11/configure.ac 2005-08-25 16:56:33.000000000 +0200 *************** *** 14,21 **** --- 14,24 ---- if test "$GCC" = "yes" then CFLAGS="$CFLAGS -Wall -Wshadow -Wcast-align -Wpointer-arith" fi + AC_PROG_CPP AC_PROG_INSTALL + AC_PROG_LN_S AC_PROG_MAKE_SET + AC_PROG_RANLIB # Checks for typedefs, structures, and compiler characteristics # AC_C_CONST *************** *** 254,259 **** --- 257,271 ---- ) AC_SUBST(USE_IPv6) + # use linux 2.[46] tproxy patch + AC_MSG_CHECKING([whether to enable transparent proxyng using linux 2.[46] tproxy patch]) + AC_ARG_ENABLE(tproxy, + [ --enable-tproxy Enable linux 2.6 tproxy patch support], + [AC_MSG_RESULT([yes]); AC_DEFINE(USE_TPROXY)], + [AC_MSG_RESULT([no])] + ) + AC_SUBST(USE_TPROXY) + # Disable use of libwrap (TCP wrappers) # it should be the last check! AC_MSG_CHECKING([whether to disable TCP wrappers library support]) diff -crb /tmp/stunnel-4.11/src/client.c stunnel-4.11/src/client.c *** /tmp/stunnel-4.11/src/client.c 2005-07-02 08:55:58.000000000 +0200 --- stunnel-4.11/src/client.c 2005-08-26 16:01:34.000000000 +0200 *************** *** 44,49 **** --- 44,65 ---- #define SHUT_RDWR 2 #endif + #ifdef USE_TPROXY + #define LINUX_NETFILTER + #define LINUX_TPROXY + #define TPROXY_MAJOR_VERSION(x) ((x >> 24) & 0xff) + #define TPROXY_MINOR_VERSION(x) ((x >> 16) & 0xff) + #define TPROXY_PATCH_VERSION(x) (x & 0xffff) + #endif + + /* transparent proxy */ + #ifdef LINUX_NETFILTER + #include <linux/netfilter_ipv4.h> + #endif + #ifdef LINUX_TPROXY + #include <linux/netfilter_ipv4/ip_tproxy.h> + #endif + /* TCP wrapper */ #ifdef USE_LIBWRAP #include <tcpd.h> *************** *** 77,82 **** --- 93,103 ---- static int connect_wait(CLI *, int, int); static void reset(int, char *); + #ifdef USE_TPROXY + static int determine_source_address(struct sockaddr_in *destination, + struct sockaddr_in *source); + #endif + int max_clients; #ifndef USE_WIN32 int max_fds; *************** *** 921,926 **** --- 942,954 ---- int s; /* destination socket */ u16 i; + // struct in_addr *local=NULL; + #ifdef USE_TPROXY + int f; + struct in_tproxy itp; + struct sockaddr_in tproxy_sin; + #endif + /* setup address_list */ if(c->opt->option.delayed_lookup) { resolved_list.num=0; *************** *** 945,959 **** if(alloc_fd(s)) return -1; ! if(c->bind_addr.num) { /* explicit local bind or transparent proxy */ memcpy(&bind_addr, &c->bind_addr.addr[0], sizeof(SOCKADDR_UNION)); if(bind(s, &bind_addr.sa, addr_len(bind_addr))<0) { sockerror("bind transparent"); closesocket(s); return -1; } } /* try to connect for the 1st time */ s_ntop(c->connecting_address, &addr); s_log(LOG_DEBUG, "%s connecting %s", --- 973,1066 ---- if(alloc_fd(s)) return -1; ! if(c->bind_addr.num ! #ifdef USE_TPROXY ! /* if we're using the tproxy patch, transparent proxy is ! handled below */ ! && !c->opt->option.transparent ! #endif ! ) { ! /* explicit local bind, not tproxy transparent mode */ ! memcpy(&bind_addr, &c->bind_addr.addr[0], sizeof(SOCKADDR_UNION)); if(bind(s, &bind_addr.sa, addr_len(bind_addr))<0) { sockerror("bind transparent"); closesocket(s); return -1; } + sockerror("local bind succeeded"); } + #ifdef USE_TPROXY + if (c->opt->option.transparent){ + /* transparent proxy support on 2.[46] linux kernels */ + /* added by MAtteo HCE Valsasna (matteo.valsasna(a)uninsubria.it), 20050826 */ + /* requires tproxy kernel patch (http://www.balabit.com/products/oss/tproxy */ + /* based on examples in cttproxy patch */ + /* this patch is released under the GNU General Public Licence, Version 2 */ + + memcpy(&bind_addr, &c->bind_addr.addr[0], sizeof(SOCKADDR_UNION)); + + /* check tproxy version */ + itp.op = TPROXY_VERSION; + itp.v.version = 0x00000000; + + getsockopt(s, SOL_IP, IP_TPROXY, &itp, &f); + s_log(LOG_NOTICE, "TPROXY_VERSION: %d.%d.%d", + TPROXY_MAJOR_VERSION(itp.v.version), + TPROXY_MINOR_VERSION(itp.v.version), + TPROXY_PATCH_VERSION(itp.v.version)); + + /* conservative: accepting only tproxy version 2.0.x */ + if (TPROXY_MAJOR_VERSION(itp.v.version) != 2 || + TPROXY_MINOR_VERSION(itp.v.version) != 0) + { + s_log(LOG_ERR, "unsupported tproxy version: %x (2.0.x required)", itp.v.version); + return -1; + } + + tproxy_sin.sin_family = AF_INET; + if (determine_source_address(&addr.in, &tproxy_sin) < 0){ + sockerror("determine_source_address"); + return -1; + } + + /* do not request a specific source port */ + tproxy_sin.sin_port = htons(0); + + /* bind to local source address */ + /* needed for tproxy magic */ + if (bind(s, (struct sockaddr *) &tproxy_sin, sizeof(tproxy_sin)) == -1) + { + sockerror("bind"); + return -1; + } + s_log(LOG_NOTICE, "bound to local: %s", inet_ntoa(tproxy_sin.sin_addr)); + + /* assign foreign address */ + itp.op = TPROXY_ASSIGN; + itp.v.addr.faddr = bind_addr.in.sin_addr; + itp.v.addr.fport = 0; + + if (setsockopt(s, SOL_IP, IP_TPROXY, &itp, sizeof(itp)) == -1) + { + s_log(LOG_NOTICE, "error assigning foreign address: %s", inet_ntoa(bind_addr.in.sin_addr)); + sockerror("setsockopt(SOL_IP, IP_TPROXY, TPROXY_ASSIGN)"); + return -1; + } + s_log(LOG_NOTICE, "assigned foreign address: %s", inet_ntoa(bind_addr.in.sin_addr)); + + /* set connect flag on socket */ + itp.op = TPROXY_FLAGS; + itp.v.flags = ITP_CONNECT|ITP_ONCE; + if (setsockopt(s, SOL_IP, IP_TPROXY, &itp, sizeof(itp)) == -1) + { + sockerror("setsockopt(SOL_IP, IP_TPROXY, TPROXY_FLAGS)"); + return -1; + } + } + #endif + /* try to connect for the 1st time */ s_ntop(c->connecting_address, &addr); s_log(LOG_DEBUG, "%s connecting %s", *************** *** 1020,1023 **** --- 1127,1175 ---- log_error(LOG_DEBUG, get_last_socket_error(), txt); } + + #ifdef USE_TPROXY + + /* from skaidrus */ + static int determine_source_address(struct sockaddr_in *destination, + struct sockaddr_in *source) + { + struct sockaddr_in addr; + socklen_t addrlen; + char textaddr[32]; + int sock; + + sock = socket(AF_INET, SOCK_DGRAM, 0); + if (sock < 0) { + syslog(LOG_CRIT, "determine_source_address: error " + "%d while creating socket", errno); + abort(); + } + + addr = *destination; + addr.sin_port = htons(80); + if (connect(sock, (struct sockaddr *)&addr, sizeof(addr)) < 0) { + syslog(LOG_ALERT, "determine_source_address: error %d " + "while looking up route for %d", errno, + inet_aton(textaddr, &(addr.sin_addr))); + close(sock); + return -1; + } + + addrlen = sizeof(*source); + if (getsockname(sock, (struct sockaddr *)source, &addrlen) < 0) { + syslog(LOG_CRIT, "determine_source_address: error %d " + "while retrieving source address", errno); + abort(); + } + source->sin_port = 0; + + close(sock); + + return 0; + } + + #endif + + /* End of client.c */

1 0

RE: stunnel and OpenSSL v0.9.8 - tunneling the UDP. Possible?
by rz1a＠mail.ru 22 Aug '05

22 Aug '05

Hello Michal, Just one thought: - if the stunnel on LAN1 joins a group to receive a multicasted stream does it really depend on DTLS's [in]ability to handle the multicasting? I see it this way - on LAN1 a machine running the (first instance of) stunnel joins a group, i.e. stunnel is told to open a socket with all the relevant socket options. Then, another machine on LAN2 (behind NAT + firewall + internet + firewall + NAT) connects to the first stunnel and tells it's own instance of stunnel to open a socket with all the relevant socket options to emit the (apparently) multicasted stream. Please comment. -- Best regards, Tony

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

stunnel-users