- stunnel-users - stunnel.org

Generic/general mechanism to forward mail servername, login, port from client to stunnel
by Ben Stover 27 Sep '13

27 Sep '13

Refering to my last posting I want to ask a related question: I read in the past somewhere that I can access stunnel from my local email client in more generic way: At first: stunnel always listens AUTOMATICALLY by default on port 127.0.0.1:9999 für incoming request and forwards the prepared/modified request to the outside world. The core parameter are NOT specified in the .conf file but by the User ID which is passed by the local client to local stunnel service. The syntax is as follows: userid=<servername>/<remotes-ssl-tls-port>/<loginname> Example: userid=pop.mail.yahoo.com/995/myname123 So as soon as stunnel receives at 127.0.0.1:9999 an incoming local connect he accepts the following userid string and tokenize it into the three parts. Given these three tokens stunnel is able to connect in the second step the remote mail server WITHOUT any further need of specification in the .conf file. Do I remember this correct? Is this mechanism described somewhere in detail? Thank you Ben

1 0

PATCH: multiple SNI options per slave section
by David Owen 27 Sep '13

27 Sep '13

Hello and thank you for stunnel! After switching from my web-server's built-in SSL support, I now have a much more secure system and SNI, too! In stunnel(8), I read this about the sni option: "sni option can also be specified more than once within a single slave service." However, I couldn't get it to work, and reading the source code verified that only one sni option is tracked per section. So, I present my patch to allow multiple sni options. It enables configurations like these: [https] ... [group1] sni = https:a.example.org sni = https:b.example.org ... [group2] sni = https:c.example.org sni = https:d.example.org ... If you have a naming scheme that doesn't lend itself to the wildcard matching already supported, this can cut your config size quite a bit. DETAILS The sni option for any section was originally tracked in the section->sni member (a string). Now, a linked-list of sni options is added to the section structure, with every sni option being appended to the end. For server setup, each slave section walks over its list, splitting each sni option and adding that slave section to the master's slave list. Splitting options and adding slaves to masters works as before, but now the slave section iterates over a list instead of referencing a single string. For client setup, each slave section checks that it has either no sni options, or exactly one. Multiple sni options results in an error. If exactly one option is found, it is copied to the old sni field of the section struct. The old sni field has been renamed to servername_to_request, as it is now used only in client mode, and this makes its purpose more clear. When no sni option is found, servername_to_request is initialized from the protocolHost or connect options, as before. I hope this patch is useful to others. Please let me know how I can make it acceptable for inclusing in the stunnel distribution. Thanks, David

1 0

Proxy HTTPS via stunnel without any certificates on proxy/stunnel box
by Gary Chodos 25 Sep '13

25 Sep '13

Greetings, We are trying to decide between SNIProxy and stunnel for the following task: - Client browser hits https://foo.bar.org, which resolves to an IP that corresponds to the stunnel machine listening on 443. - stunnel "forwards" (sorry if this is not the correct technical term) the connection to a different machine, specified by a different IP address, which is also configured to believe it is foo.bar.org and actually has a web server listening on 443 and houses the SSL key/cert. - when stunnel hits the end server, the latter sees the stunnel IP address as source, not the original user's (who initiated the web request for https://foo.bar.org) I believe this is default behavior, but just noting it for completeness. Is it possible to accomplish this (stunnel listening on and connecting to https endpoints) without housing any certs/keys on the stunnel machine itself, because we want the second server to deal with all that and we do not have access to those keys anyway. And of course, the users which go to the https://foo.bar.org should not see any cert mismatches as a result of loading https://foo.bar.org which, for the user, will resolve to the stunnel/proxy IP, rather than the end server which actually had a running web server and keys/cert. Sorry if the above detail is insufficient; do let me know. Thanks for your help. Gary

2 2

Port assignment in .conf file for local email client unique?
by Ben Stover 25 Sep '13

25 Sep '13

Assume I want to connect from my local email client to two (!) remote email servers The corresponding instructions in .conf file looks like (my guess): [smtps-firstacct] accept = 127.0.0.1:259 connect = smtps.myisp1.com:465 [smtps-secondacct] accept = 127.0.0.1:259 connect = smtps.myisp2.com:465 Questions: 1.) a configuration like above with the same "accept" port 259 is NOT possible because stunnel does not know to which remote email server he has to connect. To distinguish two different remote email server I always have to select TWO different accept-ports like [smtps-firstacct] accept = 127.0.0.1:259 connect = smtps.myisp1.com:465 [smtps-secondacct] accept = 127.0.0.1:258 connect = smtps.myisp2.com:465 Correct? 2.) Can I use arbitrary accept-ports like 1242 or 23199 or is there a port range from I have to select one? 3.) Moreover assume I want to make the SSL connection transparent can I select an accept-port 25? 4.) I read somewhere that I have always to specify in email client for POP3/SMTP an address 127.0.0.1:9999 and NOT 127.0.0.1:259 in order to connect to local stunnel service. Because local stunnel service is always listening on port 9999. Is this correct? Thank you Ben

2 2

One "client=yes" instruction per .conf file sufficient?
by Ben Stover 25 Sep '13

25 Sep '13

Is one client=yes instruction line per conf file enough? Does is mean all instructions in current .conf file belong to a client configuration or does it mean only the following command (=lines below) are intended for client usage? Ben

2 1

postgres protocol
by Robert Bernier 21 Sep '13

21 Sep '13

Hi, I've been looking at using stunnel connecting it directly to postgres. As per the man page, https://www.stunnel.org/static/stunnel.html, I was able to get postgres version 8.3 working. However, I've not suceeded using postgres version 9.2. Any insights would be appreciated. Thanks -- Robert Bernier PostgreSQL Business Intelligence Analyst robert7390(a)comcast.net http://www.linkedin.com/pub/robert-bernier/69/6a6/921 http://beknown.com/robert-bernier

1 0

Difference between verify=2, 3 and 4
by Nikolaus Rath 20 Sep '13

20 Sep '13

Hello, Thanks for writing stunnel, it looks like a great tool! I have, however, a really hard time understanding the difference between verify=2,3 and 4. In the manpage, I found verify = level verify peer certificate level 0 - request and ignore peer certificate level 1 - verify peer certificate if present level 2 - verify peer certificate level 3 - verify peer with locally installed certificate level 4 - ignore CA chain and only verify peer certificate default - no verify Levels 0-2 seem pretty clear cut, but then it becomes confusing for me. First, I do not understand how level 3 differs from level2. What does "against a locally installed certificate" mean? It seems to me that I certainly need to have a local copy of the trusted CAs even in level 2 -- at least I hope that they aren't somehow build in to stunnel. But there is also just one CApath option, so will that be used for level 2 or level 3? For level 4, the "ignore the CA chain" path is fine -- but where do I put the peer certificates that I'm willing to accept? CApath seems wrong, but cert is already used for the server's own certificate... Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C

6 13

Looking for a tech talk speaker on Secure Networking
by Chris Westin 16 Sep '13

16 Sep '13

I organize the speakers for the SF Bay Area Large-Scale Production Engineering meetup (http://www.meetup.com/SF-Bay-Area-Large-Scale-Production-Engineering/ ; take a look at the "PAST" tab to see the kinds of events we've had). For our event on Thursday October 17, 2013, I'm looking for speakers on the topic of "Secure Networking" (event: http://www.meetup.com/SF-Bay-Area-Large-Scale-Production-Engineering/events… ). As you can see from looking at our past events, I pick a topic, and then try to get 2-3 talks on that topic. Talks are usually 20-25 minutes long. This is a technical audience, and they don't appreciate a marketing pitch. They're eager to get into the nuts and bolts of the topic, including demos, code samples, and architecture. If you're going to be in the Bay Area then, and would be interested in giving a talk, please let me know here, or (preferably) through meetup.com. Thanks, Chris Westin

1 0

Re: [stunnel-users] IRC-Reconnect failed with "[10053] Software caused connection abort"(mIRC) and "SSL_connect: Peer suddenly disconnected"(tstunnel.exe)
by ralf29587＠gmx.de 13 Sep '13

13 Sep '13

Could some admin please remove my uploaded VCard and either my Name or my E-Mail-Adress shown on stunnel.org ?? Thanks a million!

1 0

stunnel accept a t3 connection?
by Scott Sikorski 10 Sep '13

10 Sep '13

I am curious if stunnel can support listening for an incoming t3 connection? I am having difficulty getting t3s to work between WebSphere and WebLogic for API calls and am curious if an alternative such as stunnel will work. I have stunnel installed betwen a client and the destination host, but the client doesn't seem to want to accept a t3://127.0.0.1:14010 connection but when I change this to http://127.0.0.1:14010 it works fine. Anything you can share would be appreciated. Mostly, if it will never work, that would be nice to know as to not spend more time troubleshooting. Best Regards, Scott Sikorski scottgsikorski(a)yahoo.com

2 1

Fullduplex in stunnel
by Krzysztof Kwiatkowski 07 Sep '13

07 Sep '13

Hi, I'm planning to use stunnel to do stress testing of my application. I decided to use stunnel because I've noticed that full-duplex has been added to version 3.2 (around 1999) and my application handles high throughput. AFAIK Stunnel uses openssl. Also I know that openssl doesn't handle fullduplex traffic very well. In fact without any tricks, half-duplex is most what I could get from openssl. As the full-duplex feature has been added to stunnel in 1999 (so long time ago) can you confirm that it is still there and full-duplex is still supported? If it is a case, how it is possible that stunnel handles fullduplex? Krzysztof Kwiatkowski

2 1

IRC-Reconnect failed with "[10053] Software caused connection abort"(mIRC) and "SSL_connect: Peer suddenly disconnected"(tstunnel.exe)
by ralf29587＠gmx.de 03 Sep '13

03 Sep '13

Hi, I have a problem using stunnel with mIRC: I was using a pretty old version of stunnel.exe that was packed with a mIRC script and could be ran as a command-line-only application without a configuration file (supplying all necessary informations parameters). I know that current mIRC version have their own ssl support, but I prefer an old version without because it has much better performance. The old one was used by "stunnel.exe -c -d localhost:<localport> -r <irc-server-ip>:<irc-server-port>" in command line and "/server localhost:<localport>" in irc. A few of my servers stopped supporting an old ssl version, this old stunnel.exe is no longer compatible to the new (open)ssl dll files and so I had to upgrade to the most recent version of stunnel - and I have some problems make it run properly. Here you can see my configuration file (stunnel.conf): ; Sample stunnel configuration file for Win32 by Michal Trojnara 2002-2012 ; Some options used here may be inadequate for your particular configuration ; This sample file does *not* represent stunnel.conf defaults ; Please consult the manual for detailed description of available options ; ************************************************************************** ; * Global options * ; ************************************************************************** ; Debugging stuff (may useful for troubleshooting) ;debug = 7 ;output = stunnel.log ; Disable FIPS mode to allow non-approved protocols and algorithms ;fips = no ; ************************************************************************** ; * Service defaults may also be specified in individual service sections * ; ************************************************************************** ; Certificate/key is needed in server mode and optional in client mode ;cert = stunnel.pem ;key = stunnel.pem ; Authentication stuff needs to be configured to prevent MITM attacks ; It is not enabled by default! ;verify = 2 ; Don't forget to c_rehash CApath ;CApath = certs ; It's often easier to use CAfile ;CAfile = certs.pem ; Don't forget to c_rehash CRLpath ;CRLpath = crls ; Alternatively CRLfile can be used ;CRLfile = crls.pem ; Disable support for insecure SSLv2 protocol options = NO_SSLv2 ; Workaround for Eudora bug ;options = DONT_INSERT_EMPTY_FRAGMENTS ; These options provide additional security at some performance degradation ;options = SINGLE_ECDH_USE ;options = SINGLE_DH_USE ; ************************************************************************** ; * Service definitions (at least one service has to be defined) * ; ************************************************************************** ; Example SSL server mode services ;[pop3s] ;accept = 995 ;connect = 110 ;[imaps] ;accept = 993 ;connect = 143 ;[ssmtp] ;accept = 465 ;connect = 25 ; Example SSL client mode services ;[gmail-pop3] ;client = yes ;accept = 127.0.0.1:110 ;connect = pop.gmail.com:995 ;[gmail-imap] ;client = yes ;accept = 127.0.0.1:143 ;connect = imap.gmail.com:993 ;[gmail-smtp] ;client = yes ;accept = 127.0.0.1:25 ;connect = smtp.gmail.com:465 ; Example SSL front-end to a web server ;[https] ;accept = 443 ;connect = 80 ; "TIMEOUTclose = 0" is a workaround for a design flaw in Microsoft SSL ; Microsoft implementations do not use SSL close-notify alert and thus ; they are vulnerable to truncation attacks ;TIMEOUTclose = 0 ; vim:ft=dosini [abjects] client = yes accept = 127.0.0.1:7001 connect = irc.abjects.net:9999 [Elite-IRC] client = yes accept = 127.0.0.1:7002 connect = SpeedSpace-IRC.eu:6697 [BodenTruppe] client = yes accept = 127.0.0.1:7003 connect = boden-truppe.zapto.org:7001 [LinkNet] client = yes accept = 127.0.0.1:7004 connect = irc.link-net.nl:7000 The first connect always works properly (as shown in the log below): 2013.09.03 12:30:45 LOG5[10696:9140]: stunnel 4.56 on x86-pc-msvc-1500 platform 2013.09.03 12:30:45 LOG5[10696:9140]: Compiled/running with OpenSSL 1.0.1e-fips11 Feb 2013 2013.09.03 12:30:45 LOG5[10696:9140]: Threading:WIN32 Sockets:SELECT,IPv6 SSL:ENGINE,OCSP,FIPS 2013.09.03 12:30:45 LOG5[10696:9140]: Reading configuration from file stunnel.conf 2013.09.03 12:30:45 LOG5[10696:9140]: FIPS mode is enabled 2013.09.03 12:30:45 LOG5[10696:9140]: Configuration successful 2013.09.03 12:30:53 LOG5[10696:10756]: Service [abjects] accepted connection from 127.0.0.1:3397 2013.09.03 12:30:53 LOG5[10696:10756]: connect_blocking: connected 188.126.73.62:9999 2013.09.03 12:30:53 LOG5[10696:10756]: Service [abjects] connected remote server from 192.168.1.10:3398 2013.09.03 12:30:54 LOG5[10696:14396]: Service [LinkNet] accepted connection from 127.0.0.1:3399 2013.09.03 12:30:54 LOG5[10696:14396]: connect_blocking: connected 194.126.217.98:7000 2013.09.03 12:30:54 LOG5[10696:14396]: Service [LinkNet] connected remote server from 192.168.1.10:3400 2013.09.03 12:30:54 LOG5[10696:2916]: Service [BodenTruppe] accepted connectionfrom 127.0.0.1:3401 2013.09.03 12:30:54 LOG5[10696:2916]: connect_blocking: connected 178.254.22.94:7001 2013.09.03 12:30:54 LOG5[10696:2916]: Service [BodenTruppe] connected remote server from 192.168.1.10:3402 2013.09.03 12:30:54 LOG5[10696:12260]: Service [Elite-IRC] accepted connection from 127.0.0.1:3403 2013.09.03 12:30:54 LOG5[10696:12260]: connect_blocking: connected 62.75.235.122:6697 2013.09.03 12:30:54 LOG5[10696:12260]: Service [Elite-IRC] connected remote server from 192.168.1.10:3404 But when I try to reconnect, it doesn't work for 2 of my 4 servers This is an example for what happens to Elite-IRC: 2013.09.03 12:32:22 LOG5[10696:12260]: Connection closed: 1972 byte(s) sent to SSL, 26903 byte(s) sent to socket 2013.09.03 12:32:23 LOG5[10696:17168]: Service [Elite-IRC] accepted connection from 127.0.0.1:3429 2013.09.03 12:32:23 LOG5[10696:17168]: connect_blocking: connected 62.75.235.122:6697 2013.09.03 12:32:23 LOG5[10696:17168]: Service [Elite-IRC] connected remote server from 192.168.1.10:3430 2013.09.03 12:32:23 LOG3[10696:17168]: SSL_connect: Peer suddenly disconnected 2013.09.03 12:32:23 LOG5[10696:17168]: Connection reset: 0 byte(s) sent to SSL,0 byte(s) sent to socket The frist line shows the manual disconnect occured by executing "/server localhost:7002" in mIRC. The second line shows the new incoming connection from my mIRC. The third line? ... I got no clue why it has to block anything. The fourth line: Successfully connected to IRC-Server? And then the fifth line occurs. I'm not sure if I interpret it right, but for some reason tstunnel.exe is kicking out my connected mIRC client which makes mIRC to tell me "[10053] Software caused connection abort". The whole lines in mIRC are: [12:34pm] * Connect retry #1 localhost (7003) ------------------------------------------------------------ [12:34pm] * [10053] Software caused connection abort ------------------------------------------------------------ [12:34pm] * Disconnected By the way, I have packed libeay32.dll, ssleay32.dll, stunnel.conf and tstunnel.exe in a subdir in mIRC directory and I'm starting it using "tstunnel.exe stunnel.conf" When this error occurs, I have to kill tstunnel.exe and start it again - then everything works fine again. For 1 of 4 servers, I also had this error with the old command-line stunnel.exe and I just wrote a script killing (only this) stunnel.exe and restarting it when this mIRC error occurs. Unfortunately this is no longer possible when tstunnel.exe is using a configuration file and one process is managing all connections. Is there any way I can fix this? (Maybe by fixing the logout of my local mIRC from my local tstunnel.exe?) Best regards

2 1

stunnel 4.56 to 4.50 on andriod
by Ronald Ning 03 Sep '13

03 Sep '13

Anyone have any luck running stunnel on android? I'm running the stock JB 4.2.2. I've tried every stunnel version from 4.50 to 4.56. When I try to run: root@andriod: /system/bin/stunnel stunnel.conf -> stunnel root@andriod: netstat -a netstat doesn't show the listening port: My stunnel.conf is this: client = yes debug = 7 [ssh] accept=2222 connect=myserver.com:22

2 1

Init script
by Alan Chester 29 Aug '13

29 Aug '13

Hello, I am currently working on using stunnel. I was wondering what everyones thoughts were on the creation of an init script for stunnel. This would help insure that the connections are brought up after a reboot. Or what is the best way to go about handling this? Thanks, Alan

2 1

no certificate available safari browser
by Scott McKeown 28 Aug '13

28 Aug '13

Hi Libin, If possible can you send over your STunnel config file but my guess would be that you would need to include your Root CA and Intermediate CA certificates into your PEM file. I would check to see what https://www.ssllabs.com/ssltest/analyze.html says about your certificates another quick test would be to have a look at http://www.digicert.com/help/ to see what they also say about the certificate chains. ~Scott Hi all, > > Sever OS: Linux/Centos 5.9 > SSLServer: Stunnel > ErrorMessage: no certificate available > CertType: SSL Web Server Certificate > Client Browser: Safari 5.1. > Client OS: OS X Lion > > When i am trying to hit the URL on safari browser it shows me the messages > "no certificate available" > No certificate meet the application . However, the same link is working > for all other browsers. Moreover, we have checked the stunnel logs, but > couldn't able to get any thing from the logs. > > Apache HTTPS config we have option *SSLVerifyClient none *in Stunnel I > have tried all option non of thing working. > * > * > Please help me.* * > > Thanks > Libin -- With Kind Regards. Scott McKeown Loadbalancer.org http://www.loadbalancer.org

3 2

stunnel 4.56 and 4.55 are not working on Android 4.3.1
by Mohsin Mirza 28 Aug '13

28 Aug '13

I tried both version of stunnel for android on Nexus 4 Build JWR66Y, Is it have to anything to do with SELinux or MAC secuirty model introduce by 4.3 It was working in initial 4.3 build OTA. root@mako:/system/bin # ./sh -c /system/xbin/stunnel root@mako:/system/bin # ________________________________________Disclaimer: This email and any attachments may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately by email and destroy this email. Any unauthorized copying, dissemination, disclosure or distribution of the material in this email is strictly forbidden. Unless expressly stated to the contrary, the sender of this email is not authorized by MBC to make any representations, negotiations or enter into any agreement on behalf of MBC. This e-mail message and any attached files have been scanned for the presence of computer viruses. However, it is the responsibility of the recipient to ensure that it is virus free; we accept no responsibility for any loss or damage arising in any way from its use.________________________________________

1 0

no certificate available safari browser
by Libindas 27 Aug '13

27 Aug '13

Hi Michal, Sever OS: Linux/Centos 5.9 SSLServer: Stunnel ErrorMessage: no certificate available CertType: SSL Web Server Certificate Client Browser: Safari 5.1. Client OS: OS X Lion When i am trying to hit the URL on safari browser it shows me the messages "no certificate available" No certificate meet the application . However, the same link is working for all other browsers. Moreover, we have checked the stunnel logs, but couldn't able to get any thing from the logs. Apache HTTPS config we have option *SSLVerifyClient none *in Stunnel I have tried all option non of thing working. * * Please help me.* * Thanks Libin

1 1

Re: [stunnel-users] Build failure for ARM32 with Yocto
by Ludolf Holzheid 23 Aug '13

23 Aug '13

On Thu, 2013-08-22 15:44:43 +0100, Laszlo Papp wrote: > On Thu, Aug 22, 2013 at 3:34 PM, Ludolf Holzheid < > lholzheid(a)bihl-wiedemann.de> wrote: > > > On Thu, 2013-08-22 14:43:55 +0100, Laszlo Papp wrote: > > > Here you can find the log file in question for details: > > > > > > [..] > > > > > > In file included from /usr//include/features.h:324:0, > > > from /usr//include/pthread.h:23, > > > from common.h:158, > > > from str.c:38: > > > > > /home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build/tmp/sysroots/foo/usr/include/bits/predefs.h:23:3: > > > error: #error "Never use <bits/predefs.h> directly; include > > <stdc-predef.h> > > > > Laszlo, > > > > Are you sure /usr//include is the right include directory for cross- > > compiling? I must confess, I'm not familiar with cross-compiling, but > > this looks fishy. > > > > Most certainly not, but other softwares get it right. I will assume that it > has something to do with how the Makefile is generated for stunnel. Got a > clue in that area? I would try to remove -I/usr//include (and -pedantic) from the compiler flags, but again, I'm no expert in autoconf and cross-compiling. Ludolf -- Bihl+Wiedemann GmbH Floßwörthstraße 41 68199 Mannheim, Germany Tel: +49 621 33996-0 Fax: +49 621 3392239 mailto:[email protected] http://www.bihl-wiedemann.de Sitz der Gesellschaft: Mannheim Geschäftsführer: Jochen Bihl, Bernhard Wiedemann Amtsgericht Mannheim, HRB 5796

3 3

REMOVE
by Bruce Edwards 22 Aug '13

22 Aug '13

Please remove me from your list server R. Bruce Edwards Communications Manager 1018 Pretlow St Franklin, VA 23851 bedwards(a)franklinpolice.org Office: 757-562-8696 Cell: 757-621-5295

1 0

Build failure for ARM32 with Yocto
by Laszlo Papp 22 Aug '13

22 Aug '13

Hi, if I build stunnel manually on my desktop machine (Archlinux), it works fine. However, when I am trying to use a Yocto/OE recipe for building it for my arm32 target, I am facing the issue below. Anyone any hint? Cheers, L. | /usr//include/linux/sysctl.h:836:20: warning: comma at end of enumerator list [-pedantic] | /usr//include/linux/sysctl.h:849:12: warning: comma at end of enumerator list [-pedantic] | /usr//include/linux/sysctl.h:892:31: warning: comma at end of enumerator list [-pedantic] | /usr//include/linux/sysctl.h:897:32: warning: comma at end of enumerator list [-pedantic] | /usr//include/linux/sysctl.h:912:26: warning: comma at end of enumerator list [-pedantic] | /usr//include/linux/sysctl.h:917:32: warning: comma at end of enumerator list [-pedantic] | /usr//include/linux/sysctl.h:928:20: warning: comma at end of enumerator list [-pedantic] | In file included from /usr//include/linux/netfilter_ipv4.h:8:0, | from common.h:383, | from network.c:38: | /usr//include/linux/netfilter.h:58:18: warning: comma at end of enumerator list [-pedantic] | In file included from common.h:383:0, | from network.c:38: | /usr//include/linux/netfilter_ipv4.h:68:26: warning: comma at end of enumerator list [-pedantic] | make[2]: *** [stunnel-str.o] Error 1 | make[2]: *** Waiting for unfinished jobs.... | make[2]: *** [stunnel-network.o] Error 1 | make[2]: *** [stunnel-resolver.o] Error 1 | make[2]: *** [stunnel-protocol.o] Error 1 | make[2]: *** [stunnel-log.o] Error 1 | make[2]: *** [stunnel-file.o] Error 1 | make[2]: *** [stunnel-options.o] Error 1 | make[2]: *** [stunnel-client.o] Error 1 | make[2]: Leaving directory `/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build/tmp/work/armv5te-linux-gnueabi/stunnel/4.56-r0/stunnel-4.56/src' | make[1]: *** [all] Error 2 | make[1]: Leaving directory `/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build/tmp/work/armv5te-linux-gnueabi/stunnel/4.56-r0/stunnel-4.56/src' | make: *** [all-recursive] Error 1 | ERROR: oe_runmake failed | ERROR: Function failed: do_compile (see /home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build/tmp/work/armv5te-linux-gnueabi/stunnel/4.56-r0/temp/log.do_compile.10590 for further information) ERROR: Task 6 (/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build/../meta-networking/recipes-support/stunnel/ stunnel_4.56.bb, do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 561 tasks of which 559 didn't need to be rerun and 1 failed. No currently running tasks (561 of 568) Summary: 1 task failed: /home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build/../meta-networking/recipes-support/stunnel/ stunnel_4.56.bb, do_compile Summary: There was 1 ERROR message shown, returning a non-zero exit code.

2 3

Problem Selecting Only Ecliptic Curve Ciphers
by Carter Browne 07 Aug '13

07 Aug '13

I'm using stunnel 4.56 on Windows 7. When I use the following cipher list: ciphers = ECDHE-ECDSA-AES256-SHA:ECDH-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDH-ECDSA-AES128-SHA to establish a connection, I get a "no shared cipher" response. The following set of ciphers does work: ciphers = ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:ECDH-RSA-AES256-SHA:ECDH-ECDSA-AES256-SHA:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDH-RSA-AES128-SHA:ECDH-ECDSA-AES128-SHA Other relevant settings: options = NO_SSLv2 sslVersion = all fips = no verify = 2 If I take out the first ECDHE-RSA-ASE256-SHA cipher from the list, the ECDHE-RSA-AES128-SHA cipher is selected. What am I doing wrong? Thanks. -- Carter Browne cbrowne(a)cbcs-usa.com

2 1

Unable to make SSL connexion work
by OLIVER Patrice 07 Aug '13

07 Aug '13

Hi, Since our company had to migrate to Orange Office365 platform, we cannot send simple SMTP message using smtp.office365.com We have to use SMTP over TLS. While I have to use some applications which cannot use SMTP, I installed and setup STunnel. When I try to send a simple mail like this : telnet myserver 25 ehlo ch-lepuy.fr mail from: toto(a)ch-lepuy.fr I cannot continue with rcpt to syntax and I have the following message : rcpt to:530 5.7.1 Client was not authenticated In the STunnel log file, I can see that : 2013.08.06 19:20:49 LOG7[1352:2832]: SSL state (connect): before/connect initialization 2013.08.06 19:20:49 LOG7[1352:2832]: SSL state (connect): SSLv3 write client hello A 2013.08.06 19:20:50 LOG7[1352:2832]: SSL state (connect): SSLv3 read server hello A 2013.08.06 19:20:50 LOG7[1352:2832]: SSL state (connect): SSLv3 read server certificate A 2013.08.06 19:20:50 LOG7[1352:2832]: SSL state (connect): SSLv3 read server key exchange A 2013.08.06 19:20:50 LOG7[1352:2832]: SSL state (connect): SSLv3 read server certificate request A 2013.08.06 19:20:50 LOG7[1352:2832]: SSL state (connect): SSLv3 read server done A 2013.08.06 19:20:50 LOG7[1352:2832]: SSL state (connect): SSLv3 write client certificate A 2013.08.06 19:20:50 LOG7[1352:2832]: SSL state (connect): SSLv3 write client key exchange A 2013.08.06 19:20:50 LOG7[1352:2832]: SSL state (connect): SSLv3 write certificate verify A 2013.08.06 19:20:50 LOG7[1352:2832]: SSL state (connect): SSLv3 write change cipher spec A 2013.08.06 19:20:50 LOG7[1352:2832]: SSL state (connect): SSLv3 write finished A 2013.08.06 19:20:50 LOG7[1352:2832]: SSL state (connect): SSLv3 flush data 2013.08.06 19:20:50 LOG7[1352:2832]: SSL state (connect): SSLv3 read finished A 2013.08.06 19:20:50 LOG7[1352:2832]: 1 items in the session cache 2013.08.06 19:20:50 LOG7[1352:2832]: 1 client connects (SSL_connect()) 2013.08.06 19:20:50 LOG7[1352:2832]: 1 client connects that finished 2013.08.06 19:20:50 LOG7[1352:2832]: 0 client renegotiations requested 2013.08.06 19:20:50 LOG7[1352:2832]: 0 server connects (SSL_accept()) 2013.08.06 19:20:50 LOG7[1352:2832]: 0 server connects that finished 2013.08.06 19:20:50 LOG7[1352:2832]: 0 server renegotiations requested 2013.08.06 19:20:50 LOG7[1352:2832]: 0 session cache hits 2013.08.06 19:20:50 LOG7[1352:2832]: 0 external session cache hits 2013.08.06 19:20:50 LOG7[1352:2832]: 0 session cache misses 2013.08.06 19:20:50 LOG7[1352:2832]: 0 session cache timeouts 2013.08.06 19:20:50 LOG7[1352:2832]: Peer certificate was cached (6184 bytes) 2013.08.06 19:20:50 LOG6[1352:2832]: SSL connected: new session negotiated 2013.08.06 19:20:50 LOG6[1352:2832]: Negotiated TLSv1/SSLv3 ciphersuite: ECDHE-RSA-AES256-SHA (256-bit encryption) 2013.08.06 19:20:50 LOG6[1352:2832]: Compression: null, expansion: null 2013.08.06 19:21:13 LOG3[1352:2832]: SSL_read: Connection reset by peer (WSAECONNRESET) (10054) 2013.08.06 19:21:13 LOG5[1352:2832]: Connection reset: 65 byte(s) sent to SSL, 231 byte(s) sent to socket 2013.08.06 19:21:13 LOG7[1352:2832]: Remote socket (FD=316) closed 2013.08.06 19:21:13 LOG7[1352:2832]: Local socket (FD=244) closed 2013.08.06 19:21:13 LOG7[1352:2832]: Service [SMTP Outgoing] finished (0 left) Here is my STunnel setup : client = yes output = stunnel-log.txt debug = 7 taskbar = yes ; Disable FIPS mode to allow non-approved protocols and algorithms ;fips = no ; ************************************************************************** ; * Service defaults may also be specified in individual service sections * ; ************************************************************************** ; Certificate/key is needed in server mode and optional in client mode cert = stunnel.pem ; Disable support for insecure SSLv2 protocol options = NO_SSLv2 [SMTP Outgoing] protocol = smtp accept = 25 connect = smtp.office365.com:587 Does anyone have an idea ? Regards? Patrice Oliver | Centre Hospitalier Emile Roux Responsable Informatique T. 04 71 04 38 30 12 Bd Andr? Chantemesse - 43012 LE PUY EN VELAY Cedex http://www.ch-lepuy.fr

3 3

Disable SSL session ticket
by dansmith 06 Aug '13

06 Aug '13

Hi, when connecting a stunnel client to a stunnel server, is it possible to disable the use of SSL session tickets? I need to be able to decrypt the stunnel traffic in wireshark. Unfortunately, wireshark still doesn't support SSL session tickets.

2 1

transparent = source, not working
by Ruben Cardenal 04 Aug '13

04 Aug '13

Hi, I'm trying to setup yet another service of this kind. I've seen this has been largely discussed several times on this list (but without valid solutions), and I'm writting this email as some kind of last resort after hours of testing and debugging. Pretty simple configuration: # cat /etc/stunnel/stunnel.conf cert = /etc/ssl/certs/stunnel4/my-cert.crt key = /etc/ssl/certs/stunnel4/my-cert.key sslVersion = SSLv3 foreground = yes pid = /tmp/stunnel4.pid socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 debug = 7 output = /var/log/stunnel.log [service] accept = 195.78.X.X:6697 connect = 195.78.X.X:1357 transparent = source Accept and connect IP's are the same. # /usr/local/bin/stunnel -version stunnel 4.56 on i686-pc-linux-gnu platform Compiled/running with OpenSSL 0.9.8o 01 Jun 2010 Threading:PTHREAD Sockets:POLL,IPv6 SSL:ENGINE,OCSP Global options: debug = daemon.notice pid = /usr/local/var/run/stunnel/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes Service-level options: ciphers = ALL:!SSLv2:!aNULL:!EXP:!LOW:-MEDIUM:RC4:+HIGH curve = prime256v1 sessionCacheSize = 1000 sessionCacheTimeout = 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 # /usr/local/bin/stunnel -sockets stunnel 4.56 on i686-pc-linux-gnu platform Compiled/running with OpenSSL 0.9.8o 01 Jun 2010 Threading:PTHREAD Sockets:POLL,IPv6 SSL:ENGINE,OCSP Socket option defaults: Option Name | Accept | Local | Remote |OS default ----------------+----------+----------+----------+---------- SO_DEBUG | -- | -- | -- | no SO_DONTROUTE | -- | -- | -- | no SO_KEEPALIVE | -- | -- | -- | no SO_LINGER | -- | -- | -- | 0:0 SO_OOBINLINE | -- | -- | -- | no SO_RCVBUF | -- | -- | -- | 87380 SO_SNDBUF | -- | -- | -- | 65536 SO_RCVLOWAT | -- | -- | -- | 1 SO_SNDLOWAT | -- | -- | -- | 1 SO_RCVTIMEO | -- | -- | -- | 0:0 SO_SNDTIMEO | -- | -- | -- | 0:0 SO_REUSEADDR | yes| -- | -- | no SO_BINDTODEVICE | -- | -- | -- |write-only TCP_KEEPCNT | -- | -- | -- | 9 TCP_KEEPIDLE | -- | -- | -- | 7200 TCP_KEEPINTVL | -- | -- | -- | 75 IP_TOS | -- | -- | -- | 0 IP_TTL | -- | -- | -- | 64 TCP_NODELAY | -- | yes| yes| no IP_FREEBIND | -- | -- | -- | no And the timeout, the same I've seen suffering to other people: 2013.08.03 19:52:12 LOG7[18496:3074533056]: Service [service] accepted (FD=3) from MY_HOME_ADDRESS:34836 2013.08.03 19:52:12 LOG7[18496:3074530160]: Service [service] started 2013.08.03 19:52:12 LOG5[18496:3074530160]: Service [service] accepted connection from MY_HOME_ADDRESS:34836 (blah blah ssl stuff) 2013.08.03 19:52:12 LOG6[18496:3074530160]: Negotiated TLSv1/SSLv3 ciphersuite: DHE-RSA-AES256-SHA (256-bit encryption) 2013.08.03 19:52:12 LOG6[18496:3074530160]: Compression: null, expansion: null 2013.08.03 19:52:12 LOG6[18496:3074530160]: IP_TRANSPARENT socket option set 2013.08.03 19:52:12 LOG6[18496:3074530160]: local_bind succeeded on the original port 2013.08.03 19:52:12 LOG6[18496:3074530160]: connect_blocking: connecting 195.78.X.X:1357 2013.08.03 19:52:12 LOG7[18496:3074530160]: connect_blocking: s_poll_wait 195.78.X.X:1357: waiting 60 seconds 2013.08.03 19:52:21 LOG3[18496:3074530160]: connect_blocking: connect 195.78.X.X:1357: Connection timed out (110) 2013.08.03 19:52:21 LOG5[18496:3074530160]: Connection reset: 0 byte(s) sent to SSL, 0 byte(s) sent to socket iptables stuff and that, is in place: # cat /proc/sys/net/ipv4/conf/all/rp_filter 0 # cat /proc/sys/net/ipv4/ip_forward 1 And did the iptables part: iptables -t mangle -N DIVERT iptables -t mangle -A PREROUTING -p tcp -m socket -j DIVERT iptables -t mangle -A DIVERT -j MARK --set-mark 1 iptables -t mangle -A DIVERT -j ACCEPT ip rule add fwmark 1 lookup 100 ip route add local 0.0.0.0/0 dev lo table 100 Debugging the whole thing, it can be seen that stunnel tries to connect: [pid 16823] connect(9, {sa_family=AF_INET, sin_port=htons(1357), sin_addr=inet_addr("195.78.X.X")}, 16) = -1 EINPROGRESS (Operation now in progress) BUT the service running in 1357 does this: # tcpdump -i eth1 -n port 1357 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes 19:52:52.586773 IP 195.78.X.X.1357 > MY_HOME_ADDRESS.34853: Flags [S.], seq 2655966098, ack 546202865, win 5840, options [mss 1460,nop,nop,sackOK], length 0 And, according to that, it looks obvious to me that this setup will never work, since that ACK packet goes to my home box, and not to the local connection. So either I'm doing something wrong (I hope I am!!) or this thing definitely doesn't work... Any help/ideas/whatever, please? Thanks, Rubén.

2 5

Library for iOS
by ios dev 29 Jul '13

29 Jul '13

Hi. I have to build static library for using in iOS application. Did anybody already built it? How can I do it? Thanks.

1 0

Reverse DNS lookup in stunnel log possible?
by mkanet＠yahoo.com 28 Jul '13

28 Jul '13

I currently have stunnel strip SSL from incoming https connections; which then passes the connections to a proxy before ultimately reaching my web server. So, the only easy way to see where incoming connections are coming from are in the stunnel log. Below, is a small example of what my stunnel log looks like (no, those arent the real IPs ). The information below would be much more useful to me if it included the DNS names in addition to their numeric IP. I currently have the latest Windows version of stunnel installed. It would be great to know how to get it to resolve DNS names as well in the log file; preferably without impeding general stunnel performance. I tried several debug levels; but none them did reverse DNS lookup. Hopefully someone know how to do this on a Windows stunnel setup. 2013.07.23 10:16:00 LOG5[10152:15136]: Service [stunnel-sslh] connected remote server from 24.12.152.129:58773 2013.07.23 10:16:00 LOG3[10152:15136]: SSL_read: Connection reset by peer (WSAECONNRESET) (10054) 2013.07.23 10:16:00 LOG5[10152:15136]: Connection reset: 272 byte(s) sent to SSL, 96 byte(s) sent to socket 2013.07.23 10:17:53 LOG5[10152:4000]: Service [stunnel-sslh] accepted connection from 71.194.51.232:5535 2013.07.23 10:17:53 LOG5[10152:4000]: connect_blocking: connected 24.12.152.129:7777 2013.07.23 10:17:53 LOG5[10152:4000]: Service [stunnel-sslh] connected remote server from 24.12.152.129:58799 2013.07.23 10:17:53 LOG5[10152:13212]: Service [stunnel-sslh] accepted connection from 71.194.51.232:5508 2013.07.23 10:17:53 LOG5[10152:3348]: Service [stunnel-sslh] accepted connection from 71.194.51.232:5509 2013.07.23 10:17:53 LOG5[10152:2884]: Service [stunnel-sslh] accepted connection from 71.194.51.232:5519

4 9

Re: [stunnel-users] Server down
by Ludolf Holzheid 24 Jul '13

24 Jul '13

On Wed, 2013-07-24 13:22:26 -0400, Walter Hankins wrote: > Hi Ludoff, > > I am new to stunnel. I trying to configure. > > Stunnel.conf: > socket = l: TCP_NODELAY = 1 > socket = r: TCP_NODELAY = 1 > > debug = 7 > output = stunnel.log Hi Walter, Always reply to the list, so others can comment. Your log says `Cannot open log file: stunnel.log´. I don't how you invoke stunnel, so I don't know if the directory it's working in is writable, but you may try to specify an output file in a writable directory with an absolute path, e.g. output=C:/stunnel.log if C:\ is writable on your box. HTH, Ludolf -- Bihl+Wiedemann GmbH Floßwörthstraße 41 68199 Mannheim, Germany Tel: +49 621 33996-0 Fax: +49 621 3392239 mailto:[email protected] http://www.bihl-wiedemann.de Sitz der Gesellschaft: Mannheim Geschäftsführer: Jochen Bihl, Bernhard Wiedemann Amtsgericht Mannheim, HRB 5796

1 0

Server down
by Walter Hankins 24 Jul '13

24 Jul '13

Server is down Reading configuration from file stunnel.conf FIPS mode is enabled Compression not enabled Snagged 64 random bytes from C:/.rnd Wrote 0 new random bytes to C:/.rnd PRNG seeded successfully Initializing service [Ssmtp] Certificate: stunnel.pem Certificate loaded Key file: stunnel.pem Private key loaded SSL options set: 0x01000004 Configuration successful Service [Ssmtp] (FD=672) bound to 127.0.0.1:25 Cannot open log file: stunnel.log Closing service [Ssmtp] Service [Ssmtp] closed (FD=672) Sessions cached before flush: 0 Sessions cached after flush: 0 Service [Ssmtp] closed Server is down

2 1

Re: [stunnel-users] stunnel and keepalive
by David H. Durgee 23 Jul '13

23 Jul '13

> `stunnel -sockets´ should show the available socket options and their > default values. > > For the box I'm writing this mail from, the default for TCP_KEEPIDLE > is 7200 and for TCP_KEEPINTVL 75 (both in seconds). You'll have to be > quite patient if you want to watch keepalive packets in wireshark > without tweaking the defaults ... > > HTH, > > Ludolf You hit the nail on the head. I set the parameters to something more reasonable and I now see the keepalive packets. Thank you for your speedy response. Dave

1 0

keepalive and stunnel
by David H. Durgee 23 Jul '13

23 Jul '13

I am attempting to use stunnel to provide secure telnet access to a server on my system. As it is possible that a user may be idle for long period I have attempted to enable keepalive with stunnel. My stunnel conf files contain: socket = l:SO_KEEPALIVE=1 socket = r:SO_KEEPALIVE=1 on both the server and client side. But wireshark shows no keepalive packets being exchanged. I am using socat to provide a service on the LAN and connections using socat do show keepalive packets. But to get this working with socat I had to use the following: socat -d -d -L/var/lock/Port$PORT - TCP:127.0.0.1:$PORT,keepalive,keepcnt=10,keepidle=3,keepintvl=1 I had originally tried it with only the keepalive option, but it took adding the other three options for it to work. Perhaps this is particular to my linux mint 13 maya x64 system and keepalive works by itself on windows? Are the other three options supported in stunnel? Dave

2 1

What do I need to provide an SSL service and verify individual clients?
by John Long 22 Jul '13

22 Jul '13

Hi, I want to set up a service using stunnel as a server. I want only specific clients to be able to connect. Each client will have an SSL-enabled client app. I understand the part about needing to create a self-signed cert for the stunnel server. I don't understand what Stunnel will require from each client. Do I have to create CSRs for each client and sign them with my self-signed cert, or will the keys from additional standalone self-signed certs for each client be good enough on the client side as long as I have a cert that for each key in the certificate path of the server? Is it correct that verify=3 will make sure only clients that have keys matching the certs in the server cert path can connect? If a client with a key that I have no cert for tries to connect, what should happen? Will it time out or will there be an error that the key isn't valid? Thanks, /jl

1 0

Stunnel log file limit
by mehmet ozisik 18 Jul '13

18 Jul '13

Hi, I would like to ask some questions regarding stunnel logging which I could not find answer with googling. 1) what is the limit of stunnel log file (can we define this)? 2) If there is a limit, when the limit is reached does it remove the filled file and starts with the same name an empty log file? Regards Mehmet

3 5

Feature requests
by Death Master 17 Jul '13

17 Jul '13

Can you implement some features? 1) Load balancing leastconn (like leastconn in haproxy) 2) UDT transport between stunnel instances(with several congestion controls which are already implemented for UDT) 3) SCTP transport between stunnel instances (if can be done in userspace) P.S. I'm using 400mbit WAN with 55-90ms latency+0-10%packet loss and on one end I can't control TCP settings at all (remote end is on OpenVZ VPS).

2 1

Line 51: "[pop3s]": Failed to initialize SSL
by Laura Fried 15 Jul '13

15 Jul '13

Beginning with Stunnel version 4.55 and continuing with 4.56 I can configure, make and make install without issue. But as soon as I try to start stunnel with the following command: /usr/local/bin/stunnel /usr/local/etc/stunnel/stunnel.conf I get the folllowing error message: Clients allowed=500 stunnel 4.56 on x86_64-unknown-linux-gnu platform Compiled/running with OpenSSL 1.0.1 14 Mar 2012 Threading:PTHREAD Sockets:POLL,IPv6 SSL:ENGINE,OCSP,FIPS Reading configuration from file /usr/local/etc/stunnel/stunnel.conf FIPS_mode_set: F06D065: error:0F06D065:common libcrypto routines:FIPS_mode_set:fips mode not supported Line 51: "[pop3s]": Failed to initialize SSL str_stats: 9 block(s), 163 data byte(s), 522 control byte(s) Any insight into this issue would be greatly appreciated. -- Laura J. Fried

3 5

is verify level 4 working?
by dansmith 11 Jul '13

11 Jul '13

I would expect that level 4 only compares locally installed certificates, however I get the same behaviour as with level 3, stunnel expects a CA cert. Here'e the relevant log when on level 4 Jul 6 23:46:31 mmm stunnel: LOG7[7870:140491349628672]: Starting certificate verification: depth=0, /C=qq/ST=qq/O=qqq/OU=rer/CN=redf/emailAddress=rfd Jul 6 23:46:31 mmm stunnel: LOG4[7870:140491349628672]: CERT: Verification error: unable to get local issuer certificate Jul 6 23:46:31 mmm stunnel: LOG4[7870:140491349628672]: Certificate check failed: depth=0, /C=qq/ST=qq/O=qqq/OU=rer/CN=redf/emailAddress=rfd Jul 6 23:46:31 mmm stunnel: LOG7[7872:140080853112576]: SSL alert (read): fatal: unknown CA What am I missing in understanding verify's level 4 ?

3 6

Creating a Centralized Secure Log Server with syslog-ng and Stunnel
by Szajt, Pablo 10 Jul '13

10 Jul '13

Hi guys, I have the task to install a secure syslog server using syslog-ng and stunnel. The Syslog server is a Solaris 10 and Syslog clients are HP-UX 11.31. I've spent already so many hours and I cannot make it run properly. I know syslog-ng works well without stunnel. I'm pretty sure someone is already using it. I'd like to have step by step installation process. I have no issue if I have to start from scratch. Thanks for your help, Pablo Pablo Szajt

2 1

Stunnel 4.56 and FIPS
by Ondrej Hrebicek 09 Jul '13

09 Jul '13

Hello stunnel users, I'm trying to compile stunnel 4.56 with FIPS support on Ubuntu 12.04. Always end up with the infamous "fingerprint does not match" error. I can't figure out what I'm doing wrong. 1. Download openssl-fips-2.0.2.tar.gz, unpack, ./config, make, and sudo make install (as specified in http://www.openssl.org/docs/fips/UserGuide-2.0.pdf) 2. Download openssl-1.0.1e.tar.gz, unpack, ./config fips --with-fipslibdir=/usr/local/ssl/fips-2.0/lib/ --with-fipsdir=/usr/local/ssl/fips-2.0/, make depend, make, and sudo make install 3. At this point, openssl is working in FIPS mode: > OPENSSL_FIPS=1 /usr/local/ssl/bin/openssl version OpenSSL 1.0.1e-fips 11 Feb 2013 > OPENSSL_FIPS=1 /usr/local/ssl/bin/openssl sha1 c_rehash SHA1(c_rehash)= 5af9e1479950bbbd9d3304c181b3f802c54f64fd > OPENSSL_FIPS=1 /usr/local/ssl/bin/openssl md5 c_rehash Error setting digest md5 139806582736544:error:060A80A3:digital envelope routines:FIPS_DIGESTINIT:disabled for fips:fips_md.c:180: 4. Download stunnel-4.56.tar.gz, unpack, ./configure --enable-fips --with-ssl=/usr/local/ssl, make, and sudo make install 5. While configuring and building stunnel completes as expected, the following does appear in ./configure's output: checking whether to enable FIPS mode support... yes configure: **************************************** SSL checking for SSL directory... /usr/local/ssl checking /usr/local/ssl/include/openssl/engine.h usability... yes checking /usr/local/ssl/include/openssl/engine.h presence... yes checking for /usr/local/ssl/include/openssl/engine.h... yes checking /usr/local/ssl/include/openssl/ocsp.h usability... yes checking /usr/local/ssl/include/openssl/ocsp.h presence... yes checking for /usr/local/ssl/include/openssl/ocsp.h... yes checking /usr/local/ssl/include/openssl/fips.h usability... no checking /usr/local/ssl/include/openssl/fips.h presence... no checking for /usr/local/ssl/include/openssl/fips.h... no configure: WARNING: OpenSSL fips header not found This is not entirely unexpected as fips.h only exists in /usr/local/ssl/fips-2.0/include/openssl. 6. Running stunnel however fails: > /usr/local/bin/stunnel Clients allowed=500 stunnel 4.56 on x86_64-unknown-linux-gnu platform Compiled/running with OpenSSL 1.0.1e-fips 11 Feb 2013 Threading:PTHREAD Sockets:POLL,IPv6 SSL:ENGINE,OCSP,FIPS Reading configuration from file /usr/local/etc/stunnel/stunnel.conf FIPS_mode_set: 2D06B06F: error:2D06B06F:FIPS routines:FIPS_check_incore_fingerprint:fingerprint does not match Line 61: "[pop3s]": Failed to initialize SSL str_stats: 5 block(s), 120 data byte(s), 290 control byte(s) I can't figure out what's causing this, hoping someone on the list may have a couple suggestions. Thanks in advance!

2 2

Re: [stunnel-users] is verify level 4 working?
by Thomas Eifert 08 Jul '13

08 Jul '13

dansmith, I'd be the last to argue with you. Purely as an experiment, I tried changing the verify level from 4 to 3, but it didn't fly. I most likely missed the entirety of the signing chain, as I only added the certificate of the *issuing* CA. Regards, Thomas On 7/8/2013 7:01 PM, dansmith wrote: > Thomas, the recent exception you are describing - needing a CA > sertificate and server certificate is what verify=3 does. > So, I guess there is some regression in the code. > When I look at stunnel's verify.c code, there is only one reference to > level 4 in line 225. It seems like verify=4 functionality is missing > from the code. > > On 07/08/2013 11:44 PM, Thomas Eifert wrote: >> dansmith, >> >> It's my understanding that verify = 4 should, theoretically, look only >> for the server certificate, and this is the way I've been using it >> with great success over the past year or so. Recently, however, I ran >> into an exception to that behavior. >> >> In my case, I only had to download and install one certificate; that >> of the signing CA. I simply pasted it directly below the server >> certificate in the associated .pem file. The CA certificate wasn't >> originally in .pem format, so I converted it beforehand. OpenSSL has >> conversion capability, and there are also online certificate tools >> available. Your mileage may vary. >> >> Good luck. >> >> Thomas >> >> >> On 7/8/2013 3:01 PM, dansmith wrote: >> >>> Could you kindly break it down for me. Are you saying that I need to >>> have two CAs A & B. A signs the certificate of B and B signs the >>> certificate of my server? >>> Do I understand correctly that verify=4 is supposed to simply ignore >> any >>> CAs and only look at the actual certificate, comparing it to the >>> certificate in CAfile ? >>> >>> >>> On 07/08/2013 06:32 PM, Thomas Eifert wrote: >>>> You're not missing anything. I've experienced a similar issue. While >>>> verify = 4 generally works well in most cases and will ignore the CA >>>> chain, I've encountered a few isolated incidences in which I've had to >>>> append or "chain" the server certificate with the certificate of the >>>> CA. Give it a shot and see if it resolves your issue. >>>> >>>> Thomas >>>> >>>> On 7/8/2013 3:02 AM, dansmith wrote: >>>>> I would expect that level 4 only compares locally installed >>>>> certificates, however I get the same behaviour as with level 3, >> stunnel >>>>> expects a CA cert. >>>>> Here'e the relevant log when on level 4 >>>>> >>>>> Jul 6 23:46:31 mmm stunnel: LOG7[7870:140491349628672]: Starting >>>>> certificate verification: depth=0, >>>>> /C=qq/ST=qq/O=qqq/OU=rer/CN=redf/emailAddress=rfd >>>>> Jul 6 23:46:31 mmm stunnel: LOG4[7870:140491349628672]: CERT: >>>>> Verification error: unable to get local issuer certificate >>>>> Jul 6 23:46:31 mmm stunnel: LOG4[7870:140491349628672]: Certificate >>>>> check failed: depth=0, >> /C=qq/ST=qq/O=qqq/OU=rer/CN=redf/emailAddress=rfd >>>>> Jul 6 23:46:31 mmm stunnel: LOG7[7872:140080853112576]: SSL alert >>>>> (read): fatal: unknown CA >>>>> >>>>> What am I missing in understanding verify's level 4 ? >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> stunnel-users mailing list >>>>> stunnel-users(a)stunnel.org >>>>> https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users >>>>> >>>> >>> >>> >> > > -- Attention: This message and all attachments are private and may contain information that is confidential and privileged. If you received this message in error, please notify the sender by reply email and delete the message immediately.

1 0

is verify level 4 working?
by Thomas Eifert 08 Jul '13

08 Jul '13

dansmith, It's my understanding that verify = 4 should, theoretically, look only for the server certificate, and this is the way I've been using it with great success over the past year or so. Recently, however, I ran into an exception to that behavior. In my case, I only had to download and install one certificate; that of the signing CA. I simply pasted it directly below the server certificate in the associated .pem file. The CA certificate wasn't originally in .pem format, so I converted it beforehand. OpenSSL has conversion capability, and there are also online certificate tools available. Your mileage may vary. Good luck. Thomas On 7/8/2013 3:01 PM, dansmith wrote: > Could you kindly break it down for me. Are you saying that I need to > have two CAs A & B. A signs the certificate of B and B signs the > certificate of my server? > Do I understand correctly that verify=4 is supposed to simply ignore any > CAs and only look at the actual certificate, comparing it to the > certificate in CAfile ? > > > On 07/08/2013 06:32 PM, Thomas Eifert wrote: >> You're not missing anything. I've experienced a similar issue. While >> verify = 4 generally works well in most cases and will ignore the CA >> chain, I've encountered a few isolated incidences in which I've had to >> append or "chain" the server certificate with the certificate of the >> CA. Give it a shot and see if it resolves your issue. >> >> Thomas >> >> On 7/8/2013 3:02 AM, dansmith wrote: >>> I would expect that level 4 only compares locally installed >>> certificates, however I get the same behaviour as with level 3, stunnel >>> expects a CA cert. >>> Here'e the relevant log when on level 4 >>> >>> Jul 6 23:46:31 mmm stunnel: LOG7[7870:140491349628672]: Starting >>> certificate verification: depth=0, >>> /C=qq/ST=qq/O=qqq/OU=rer/CN=redf/emailAddress=rfd >>> Jul 6 23:46:31 mmm stunnel: LOG4[7870:140491349628672]: CERT: >>> Verification error: unable to get local issuer certificate >>> Jul 6 23:46:31 mmm stunnel: LOG4[7870:140491349628672]: Certificate >>> check failed: depth=0, /C=qq/ST=qq/O=qqq/OU=rer/CN=redf/emailAddress=rfd >>> Jul 6 23:46:31 mmm stunnel: LOG7[7872:140080853112576]: SSL alert >>> (read): fatal: unknown CA >>> >>> What am I missing in understanding verify's level 4 ? >>> >>> >>> >>> >>> _______________________________________________ >>> stunnel-users mailing list >>> stunnel-users(a)stunnel.org >>> https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users >>> >> > > -- Attention: This message and all attachments are private and may contain information that is confidential and privileged. If you received this message in error, please notify the sender by reply email and delete the message immediately. -- Attention: This message and all attachments are private and may contain information that is confidential and privileged. If you received this message in error, please notify the sender by reply email and delete the message immediately.

1 0

Re: [stunnel-users] accept : too many open files error(24)
by Senthil Naidu 01 Jul '13

01 Jul '13

Hi, We are using 64 bit version of centos, and the ram of this system is 1gb so should we increase this limit to 100000 in the limits.conf Regards senthil On Sun, Jun 30, 2013 at 12:31 AM, Michael Curran <mike_curran(a)hotmail.com>wrote: > Are you running 32-kernel for centos? > > 32-bit limits in the 4500 range for open connections due to the memory > constraints > > We usually set our open file limits to 100I specifically for Stunnel user > > *Sent from my Verizon Wireless 4G LTE DROID* > > > Senthil Naidu <senthil.naidu(a)gmail.com> wrote: > > Hi > > > > We are using stunnel 4.32 on centos and our ulimits in limits.conf are as > follows > > > > * soft nofile 16384 > > * hard nofile 65536 > > > > We keep getting the error “too many open files(24)” and stunnel does not > accept new connection till we restart the same > > > > Is this ulimit proper or we need to increase the same , we are look for > 3000 to 5000 connections > > > > Regards > > Senthil >

2 2

accept : too many open files error(24)
by Senthil Naidu 29 Jun '13

29 Jun '13

Hi We are using stunnel 4.32 on centos and our ulimits in limits.conf are as follows * soft nofile 16384 * hard nofile 65536 We keep getting the error “too many open files(24)” and stunnel does not accept new connection till we restart the same Is this ulimit proper or we need to increase the same , we are look for 3000 to 5000 connections Regards Senthil

1 0

Re: [stunnel-users] Sending Email Without Authentication with gmail
by Stephen Gates 28 Jun '13

28 Jun '13

I downloaded the old argosoft freeware and it works! Praise God! Thanks to all for your time, help and suggestions!! Much appreciated. Stephen Gates Harold K. Scholz Company 7800 Serum Avenue Ralston, NE 68127 402-339-7600

2 1

Re: [stunnel-users] Sending Email from PLC Without Authentication with gmail - static ip/argosoft/php script
by Stephen Gates 28 Jun '13

28 Jun '13

> The only limitation I can recall on this freeware version is in the file size (5MB) and in the retries between relay errors. > > But you have to be aware when using a mail server that, thanks to Spamhaus, you need a static IP or almost all SMTPs out there will block your server to accept mail from (including Gmail)." > The router that my network is connected to has a static IP as far as I can tell and so does the PC and PLC on the LAN. How can I determine for sure if I have a static IP? I will try the Argosoft link. > Question? What does this device have available for resources. I use a php script that checks server status emails via gmail when there are changes in status, and it handles the connection directly to gmail. > I'm not sure. I don't know what php script is. I am about to try emailrelay from sourceforge.net. Anybody have experience with that? http://emailrelay.sourceforge.net/ Thanks, Stephen Gates Harold K. Scholz Company 7800 Serum Avenue Ralston, NE 68127 402-339-7600

1 0

Re: [stunnel-users] Sending Email from PLC Without Authentication with gmail
by Stephen Gates 27 Jun '13

27 Jun '13

"The issue with your situation is not stunnel but the fact that your SMTP client does not have the capability to provide authentication. As you mentioned, Gmail will require authentication information from the client. If that information is not provided by the SMTP client application, then the SMTP transaction will fail. ? I would suggest you consider setting up some kind of SMTP Relay. Which will serve as a proxy between your PLC and Google SMTP servers. ? You can also take a look at this document and if possible implement the last approach? http://support.google.com/a/bin/answer.py?hl=en <http://support.google.com/a/bin/answer.py?hl=en&answer=176600> &answer=176600" Thanks for your help Leandro. Do you have a suggestion for a SMTP Relay?? I have tried Free SMTP Server which was the only thing that has worked so far and worked almost perfectly except that it can only send out 10 emails a day. And I need more capacity for sending than that. I also have used trial versions of ArgoSoft, 1st Mail Server and QK SMTP Server but couldn't get those to work. I have tried the Google suggestion for using asmpx.l.google.com but I need to send to vtext.com addresses which are outside of the google domain. I tried adding the vtext.com addresses to googlegroups.com and sending emails using the asmpx.l.google.com server but vtext did not receive the emails for googlegroups.com. So I'm desperate to find some sort of solution. Thanks, Stephen Gates Harold K. Scholz Company 7800 Serum Avenue Ralston, NE 68127 402-339-7600

3 2

Stunnel | connection reset by peer
by Prem Vikash Upadhyay 27 Jun '13

27 Jun '13

Hi, Is there any configuration that can be used, to change the 'connection reset by peer' to 'connection refused'?. In our setup we are using day cq dispatcher with sticky session enabled, but dispatcher is invalidating sticky session only when it receiving error as 'connection refused', while stunnel is always sending error as 'connection reset by peer', whenever the connect server is down/crashed. Thanks Prem

2 1

Sending Email from PLC Without Authentication with gmail
by Stephen Gates 27 Jun '13

27 Jun '13

A customer needs to send emails from a Programmable Logic Controller (PLC) which cannot provide authentication. The customer's email server is gmail which obviously requires authentication. The PLC IP is 192.168.1.2 and the PC IP on which stunnel is installed is 192.168.1.31 My config is: cert = stunnel.pem [smtps] client = yes accept = 25 connect = smtp.gmail.com:465 The PLC is set up to send emails to the IP of the PC 192.168.1.31 When I try to send emails I get the following in the stunnel log: 2013.06.26 14:26:30 LOG5[12384:13048]: Service [smtps] accepted connection from 192.168.1.2:2938 2013.06.26 14:26:30 LOG5[12384:13048]: connect_blocking: connected 74.125.130.108:465 2013.06.26 14:26:30 LOG5[12384:13048]: Service [smtps] connected remote server from 192.168.1.31:53599 Any help would be greatly appreciated! Stephen Gates Harold K. Scholz Company 7800 Serum Avenue Ralston, NE 68127 402-339-7600

2 1

Re: [stunnel-users] Sending Email from PLC Without Authentication - With debug = 7 log
by Stephen Gates 26 Jun '13

26 Jun '13

Just wanted to send this again with a clarified subject. Still getting the connect_blocking error. Any more ideas? Thanks for replying, Brian. From: Stephen Gates [mailto:[email protected]] Sent: Wednesday, June 26, 2013 3:09 PM To: 'stunnel-users(a)stunnel.org' Subject: RE: Sending Email from PLC Without Authentication with gmail I added the following as Brian suggested. debug = 7 I tried doing output = stunnel.log but that cause an error when I reloded the config file. Here's the log after adding the above and trying to send another email. 2013.06.26 15:03:37 LOG7[10620:10992]: Service [smtps] (FD=416) bound to 0.0.0.0:25 2013.06.26 15:03:58 LOG7[10620:10992]: Service [smtps] accepted (FD=296) from 192.168.1.2:2946 2013.06.26 15:03:58 LOG7[10620:10992]: Creating a new thread 2013.06.26 15:03:58 LOG7[10620:10992]: New thread created 2013.06.26 15:03:58 LOG7[10620:10360]: Service [smtps] started 2013.06.26 15:03:58 LOG5[10620:10360]: Service [smtps] accepted connection from 192.168.1.2:2946 2013.06.26 15:03:58 LOG6[10620:10360]: connect_blocking: connecting 74.125.130.108:465 2013.06.26 15:03:58 LOG7[10620:10360]: connect_blocking: s_poll_wait 74.125.130.108:465: waiting 10 seconds 2013.06.26 15:03:58 LOG5[10620:10360]: connect_blocking: connected 74.125.130.108:465 2013.06.26 15:03:58 LOG5[10620:10360]: Service [smtps] connected remote server from 192.168.1.31:53640 2013.06.26 15:03:58 LOG7[10620:10360]: Remote socket (FD=368) initialized 2013.06.26 15:03:58 LOG7[10620:10360]: SNI: sending servername: smtp.gmail.com 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): before/connect initialization 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 write client hello A 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 read server hello A 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 read server certificate A 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 read server done A 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 write client key exchange A 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 write change cipher spec A 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 write finished A 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 flush data 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 read server session ticket A 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 read finished A 2013.06.26 15:03:58 LOG7[10620:10360]: 1 items in the session cache 2013.06.26 15:03:58 LOG7[10620:10360]: 1 client connects (SSL_connect()) 2013.06.26 15:03:58 LOG7[10620:10360]: 1 client connects that finished 2013.06.26 15:03:58 LOG7[10620:10360]: 0 client renegotiations requested 2013.06.26 15:03:58 LOG7[10620:10360]: 0 server connects (SSL_accept()) 2013.06.26 15:03:58 LOG7[10620:10360]: 0 server connects that finished 2013.06.26 15:03:58 LOG7[10620:10360]: 0 server renegotiations requested 2013.06.26 15:03:58 LOG7[10620:10360]: 0 session cache hits 2013.06.26 15:03:58 LOG7[10620:10360]: 0 external session cache hits 2013.06.26 15:03:58 LOG7[10620:10360]: 0 session cache misses 2013.06.26 15:03:58 LOG7[10620:10360]: 0 session cache timeouts 2013.06.26 15:03:58 LOG7[10620:10360]: Peer certificate was cached (2266 bytes) 2013.06.26 15:03:58 LOG6[10620:10360]: SSL connected: new session negotiated 2013.06.26 15:03:58 LOG6[10620:10360]: Negotiated TLSv1/SSLv3 ciphersuite: AES128-SHA (128-bit encryption) 2013.06.26 15:03:58 LOG6[10620:10360]: Compression: null, expansion: null 2013.06.26 15:03:59 LOG6[10620:10360]: SSL socket closed (SSL_read) 2013.06.26 15:03:59 LOG7[10620:10360]: Sent socket write shutdown 2013.06.26 15:03:59 LOG5[10620:10360]: Connection closed: 65 byte(s) sent to SSL, 293 byte(s) sent to socket 2013.06.26 15:03:59 LOG7[10620:10360]: Remote socket (FD=368) closed 2013.06.26 15:03:59 LOG7[10620:10360]: Local socket (FD=296) closed 2013.06.26 15:03:59 LOG7[10620:10360]: Service [smtps] finished (0 left) 2013.06.26 15:03:59 LOG7[10620:10992]: Service [smtps] accepted (FD=364) from 192.168.1.2:2947 2013.06.26 15:03:59 LOG7[10620:10992]: Creating a new thread 2013.06.26 15:03:59 LOG7[10620:10992]: New thread created 2013.06.26 15:03:59 LOG7[10620:7792]: Service [smtps] started 2013.06.26 15:03:59 LOG5[10620:7792]: Service [smtps] accepted connection from 192.168.1.2:2947 2013.06.26 15:03:59 LOG6[10620:7792]: connect_blocking: connecting 74.125.130.109:465 2013.06.26 15:03:59 LOG7[10620:7792]: connect_blocking: s_poll_wait 74.125.130.109:465: waiting 10 seconds 2013.06.26 15:03:59 LOG5[10620:7792]: connect_blocking: connected 74.125.130.109:465 2013.06.26 15:03:59 LOG5[10620:7792]: Service [smtps] connected remote server from 192.168.1.31:53641 2013.06.26 15:03:59 LOG7[10620:7792]: Remote socket (FD=368) initialized 2013.06.26 15:03:59 LOG7[10620:7792]: SNI: sending servername: smtp.gmail.com 2013.06.26 15:03:59 LOG7[10620:7792]: SSL state (connect): before/connect initialization 2013.06.26 15:03:59 LOG7[10620:7792]: SSL state (connect): SSLv3 write client hello A 2013.06.26 15:03:59 LOG7[10620:7792]: SSL state (connect): SSLv3 read server hello A 2013.06.26 15:03:59 LOG7[10620:7792]: SSL state (connect): SSLv3 read finished A 2013.06.26 15:03:59 LOG7[10620:7792]: SSL state (connect): SSLv3 write change cipher spec A 2013.06.26 15:03:59 LOG7[10620:7792]: SSL state (connect): SSLv3 write finished A 2013.06.26 15:03:59 LOG7[10620:7792]: SSL state (connect): SSLv3 flush data 2013.06.26 15:03:59 LOG7[10620:7792]: 1 items in the session cache 2013.06.26 15:03:59 LOG7[10620:7792]: 2 client connects (SSL_connect()) 2013.06.26 15:03:59 LOG7[10620:7792]: 2 client connects that finished 2013.06.26 15:03:59 LOG7[10620:7792]: 0 client renegotiations requested 2013.06.26 15:03:59 LOG7[10620:7792]: 0 server connects (SSL_accept()) 2013.06.26 15:03:59 LOG7[10620:7792]: 0 server connects that finished 2013.06.26 15:03:59 LOG7[10620:7792]: 0 server renegotiations requested 2013.06.26 15:03:59 LOG7[10620:7792]: 1 session cache hits 2013.06.26 15:03:59 LOG7[10620:7792]: 0 external session cache hits 2013.06.26 15:03:59 LOG7[10620:7792]: 0 session cache misses 2013.06.26 15:03:59 LOG7[10620:7792]: 0 session cache timeouts 2013.06.26 15:03:59 LOG6[10620:7792]: SSL connected: previous session reused 2013.06.26 15:04:00 LOG6[10620:7792]: SSL socket closed (SSL_read) 2013.06.26 15:04:00 LOG7[10620:7792]: Sent socket write shutdown 2013.06.26 15:04:00 LOG5[10620:7792]: Connection closed: 65 byte(s) sent to SSL, 287 byte(s) sent to socket 2013.06.26 15:04:00 LOG7[10620:7792]: Remote socket (FD=368) closed 2013.06.26 15:04:00 LOG7[10620:7792]: Local socket (FD=364) closed 2013.06.26 15:04:00 LOG7[10620:7792]: Service [smtps] finished (0 left) 2013.06.26 15:04:00 LOG7[10620:10992]: Service [smtps] accepted (FD=372) from 192.168.1.2:2948 2013.06.26 15:04:00 LOG7[10620:10992]: Creating a new thread 2013.06.26 15:04:00 LOG7[10620:10992]: New thread created 2013.06.26 15:04:00 LOG7[10620:12944]: Service [smtps] started 2013.06.26 15:04:00 LOG5[10620:12944]: Service [smtps] accepted connection from 192.168.1.2:2948 2013.06.26 15:04:00 LOG6[10620:12944]: connect_blocking: connecting 74.125.130.108:465 2013.06.26 15:04:00 LOG7[10620:12944]: connect_blocking: s_poll_wait 74.125.130.108:465: waiting 10 seconds 2013.06.26 15:04:00 LOG5[10620:12944]: connect_blocking: connected 74.125.130.108:465 2013.06.26 15:04:00 LOG5[10620:12944]: Service [smtps] connected remote server from 192.168.1.31:53642 2013.06.26 15:04:00 LOG7[10620:12944]: Remote socket (FD=368) initialized 2013.06.26 15:04:00 LOG7[10620:12944]: SNI: sending servername: smtp.gmail.com 2013.06.26 15:04:00 LOG7[10620:12944]: SSL state (connect): before/connect initialization 2013.06.26 15:04:00 LOG7[10620:12944]: SSL state (connect): SSLv3 write client hello A 2013.06.26 15:04:00 LOG7[10620:12944]: SSL state (connect): SSLv3 read server hello A 2013.06.26 15:04:00 LOG7[10620:12944]: SSL state (connect): SSLv3 read finished A 2013.06.26 15:04:00 LOG7[10620:12944]: SSL state (connect): SSLv3 write change cipher spec A 2013.06.26 15:04:00 LOG7[10620:12944]: SSL state (connect): SSLv3 write finished A 2013.06.26 15:04:00 LOG7[10620:12944]: SSL state (connect): SSLv3 flush data 2013.06.26 15:04:00 LOG7[10620:12944]: 1 items in the session cache 2013.06.26 15:04:00 LOG7[10620:12944]: 3 client connects (SSL_connect()) 2013.06.26 15:04:00 LOG7[10620:12944]: 3 client connects that finished 2013.06.26 15:04:00 LOG7[10620:12944]: 0 client renegotiations requested 2013.06.26 15:04:00 LOG7[10620:12944]: 0 server connects (SSL_accept()) 2013.06.26 15:04:00 LOG7[10620:12944]: 0 server connects that finished 2013.06.26 15:04:00 LOG7[10620:12944]: 0 server renegotiations requested 2013.06.26 15:04:00 LOG7[10620:12944]: 2 session cache hits 2013.06.26 15:04:00 LOG7[10620:12944]: 0 external session cache hits 2013.06.26 15:04:00 LOG7[10620:12944]: 0 session cache misses 2013.06.26 15:04:00 LOG7[10620:12944]: 0 session cache timeouts 2013.06.26 15:04:00 LOG6[10620:12944]: SSL connected: previous session reused 2013.06.26 15:04:01 LOG6[10620:12944]: SSL socket closed (SSL_read) 2013.06.26 15:04:01 LOG7[10620:12944]: Sent socket write shutdown 2013.06.26 15:04:01 LOG5[10620:12944]: Connection closed: 65 byte(s) sent to SSL, 290 byte(s) sent to socket 2013.06.26 15:04:01 LOG7[10620:12944]: Remote socket (FD=368) closed 2013.06.26 15:04:01 LOG7[10620:12944]: Local socket (FD=372) closed 2013.06.26 15:04:01 LOG7[10620:12944]: Service [smtps] finished (0 left) 2013.06.26 15:04:01 LOG7[10620:10992]: Service [smtps] accepted (FD=288) from 192.168.1.2:2949 2013.06.26 15:04:01 LOG7[10620:10992]: Creating a new thread 2013.06.26 15:04:01 LOG7[10620:10992]: New thread created 2013.06.26 15:04:01 LOG7[10620:12900]: Service [smtps] started 2013.06.26 15:04:01 LOG5[10620:12900]: Service [smtps] accepted connection from 192.168.1.2:2949 2013.06.26 15:04:01 LOG6[10620:12900]: connect_blocking: connecting 74.125.130.109:465 2013.06.26 15:04:01 LOG7[10620:12900]: connect_blocking: s_poll_wait 74.125.130.109:465: waiting 10 seconds 2013.06.26 15:04:01 LOG5[10620:12900]: connect_blocking: connected 74.125.130.109:465 2013.06.26 15:04:01 LOG5[10620:12900]: Service [smtps] connected remote server from 192.168.1.31:53643 2013.06.26 15:04:01 LOG7[10620:12900]: Remote socket (FD=368) initialized 2013.06.26 15:04:01 LOG7[10620:12900]: SNI: sending servername: smtp.gmail.com 2013.06.26 15:04:01 LOG7[10620:12900]: SSL state (connect): before/connect initialization 2013.06.26 15:04:01 LOG7[10620:12900]: SSL state (connect): SSLv3 write client hello A 2013.06.26 15:04:01 LOG7[10620:12900]: SSL state (connect): SSLv3 read server hello A 2013.06.26 15:04:01 LOG7[10620:12900]: SSL state (connect): SSLv3 read finished A 2013.06.26 15:04:01 LOG7[10620:12900]: SSL state (connect): SSLv3 write change cipher spec A 2013.06.26 15:04:01 LOG7[10620:12900]: SSL state (connect): SSLv3 write finished A 2013.06.26 15:04:01 LOG7[10620:12900]: SSL state (connect): SSLv3 flush data 2013.06.26 15:04:01 LOG7[10620:12900]: 1 items in the session cache 2013.06.26 15:04:01 LOG7[10620:12900]: 4 client connects (SSL_connect()) 2013.06.26 15:04:01 LOG7[10620:12900]: 4 client connects that finished 2013.06.26 15:04:01 LOG7[10620:12900]: 0 client renegotiations requested 2013.06.26 15:04:01 LOG7[10620:12900]: 0 server connects (SSL_accept()) 2013.06.26 15:04:01 LOG7[10620:12900]: 0 server connects that finished 2013.06.26 15:04:01 LOG7[10620:12900]: 0 server renegotiations requested 2013.06.26 15:04:01 LOG7[10620:12900]: 3 session cache hits 2013.06.26 15:04:01 LOG7[10620:12900]: 0 external session cache hits 2013.06.26 15:04:01 LOG7[10620:12900]: 0 session cache misses 2013.06.26 15:04:01 LOG7[10620:12900]: 0 session cache timeouts 2013.06.26 15:04:01 LOG6[10620:12900]: SSL connected: previous session reused 2013.06.26 15:04:02 LOG6[10620:12900]: SSL socket closed (SSL_read) 2013.06.26 15:04:02 LOG7[10620:12900]: Sent socket write shutdown 2013.06.26 15:04:02 LOG5[10620:12900]: Connection closed: 65 byte(s) sent to SSL, 293 byte(s) sent to socket 2013.06.26 15:04:02 LOG7[10620:12900]: Remote socket (FD=368) closed 2013.06.26 15:04:02 LOG7[10620:12900]: Local socket (FD=288) closed 2013.06.26 15:04:02 LOG7[10620:12900]: Service [smtps] finished (0 left) 2013.06.26 15:04:02 LOG7[10620:10992]: Service [smtps] accepted (FD=292) from 192.168.1.2:2950 2013.06.26 15:04:02 LOG7[10620:10992]: Creating a new thread 2013.06.26 15:04:02 LOG7[10620:10992]: New thread created 2013.06.26 15:04:02 LOG7[10620:11560]: Service [smtps] started 2013.06.26 15:04:02 LOG5[10620:11560]: Service [smtps] accepted connection from 192.168.1.2:2950 2013.06.26 15:04:02 LOG6[10620:11560]: connect_blocking: connecting 74.125.130.108:465 2013.06.26 15:04:02 LOG7[10620:11560]: connect_blocking: s_poll_wait 74.125.130.108:465: waiting 10 seconds 2013.06.26 15:04:02 LOG5[10620:11560]: connect_blocking: connected 74.125.130.108:465 2013.06.26 15:04:02 LOG5[10620:11560]: Service [smtps] connected remote server from 192.168.1.31:53644 2013.06.26 15:04:02 LOG7[10620:11560]: Remote socket (FD=368) initialized 2013.06.26 15:04:02 LOG7[10620:11560]: SNI: sending servername: smtp.gmail.com 2013.06.26 15:04:02 LOG7[10620:11560]: SSL state (connect): before/connect initialization 2013.06.26 15:04:02 LOG7[10620:11560]: SSL state (connect): SSLv3 write client hello A 2013.06.26 15:04:02 LOG7[10620:11560]: SSL state (connect): SSLv3 read server hello A 2013.06.26 15:04:02 LOG7[10620:11560]: SSL state (connect): SSLv3 read finished A 2013.06.26 15:04:02 LOG7[10620:11560]: SSL state (connect): SSLv3 write change cipher spec A 2013.06.26 15:04:02 LOG7[10620:11560]: SSL state (connect): SSLv3 write finished A 2013.06.26 15:04:02 LOG7[10620:11560]: SSL state (connect): SSLv3 flush data 2013.06.26 15:04:02 LOG7[10620:11560]: 1 items in the session cache 2013.06.26 15:04:02 LOG7[10620:11560]: 5 client connects (SSL_connect()) 2013.06.26 15:04:02 LOG7[10620:11560]: 5 client connects that finished 2013.06.26 15:04:02 LOG7[10620:11560]: 0 client renegotiations requested 2013.06.26 15:04:02 LOG7[10620:11560]: 0 server connects (SSL_accept()) 2013.06.26 15:04:02 LOG7[10620:11560]: 0 server connects that finished 2013.06.26 15:04:02 LOG7[10620:11560]: 0 server renegotiations requested 2013.06.26 15:04:02 LOG7[10620:11560]: 4 session cache hits 2013.06.26 15:04:02 LOG7[10620:11560]: 0 external session cache hits 2013.06.26 15:04:02 LOG7[10620:11560]: 0 session cache misses 2013.06.26 15:04:02 LOG7[10620:11560]: 0 session cache timeouts 2013.06.26 15:04:02 LOG6[10620:11560]: SSL connected: previous session reused 2013.06.26 15:04:03 LOG6[10620:11560]: SSL socket closed (SSL_read) 2013.06.26 15:04:03 LOG7[10620:11560]: Sent socket write shutdown 2013.06.26 15:04:03 LOG5[10620:11560]: Connection closed: 65 byte(s) sent to SSL, 296 byte(s) sent to socket 2013.06.26 15:04:03 LOG7[10620:11560]: Remote socket (FD=368) closed 2013.06.26 15:04:03 LOG7[10620:11560]: Local socket (FD=292) closed 2013.06.26 15:04:03 LOG7[10620:11560]: Service [smtps] finished (0 left) 2013.06.26 15:04:03 LOG7[10620:10992]: Service [smtps] accepted (FD=296) from 192.168.1.2:2951 2013.06.26 15:04:03 LOG7[10620:10992]: Creating a new thread 2013.06.26 15:04:03 LOG7[10620:10992]: New thread created 2013.06.26 15:04:03 LOG7[10620:10092]: Service [smtps] started 2013.06.26 15:04:03 LOG5[10620:10092]: Service [smtps] accepted connection from 192.168.1.2:2951 2013.06.26 15:04:03 LOG6[10620:10092]: connect_blocking: connecting 74.125.130.109:465 2013.06.26 15:04:03 LOG7[10620:10092]: connect_blocking: s_poll_wait 74.125.130.109:465: waiting 10 seconds 2013.06.26 15:04:03 LOG5[10620:10092]: connect_blocking: connected 74.125.130.109:465 2013.06.26 15:04:03 LOG5[10620:10092]: Service [smtps] connected remote server from 192.168.1.31:53645 2013.06.26 15:04:03 LOG7[10620:10092]: Remote socket (FD=368) initialized 2013.06.26 15:04:03 LOG7[10620:10092]: SNI: sending servername: smtp.gmail.com 2013.06.26 15:04:03 LOG7[10620:10092]: SSL state (connect): before/connect initialization 2013.06.26 15:04:03 LOG7[10620:10092]: SSL state (connect): SSLv3 write client hello A 2013.06.26 15:04:03 LOG7[10620:10092]: SSL state (connect): SSLv3 read server hello A 2013.06.26 15:04:03 LOG7[10620:10092]: SSL state (connect): SSLv3 read finished A 2013.06.26 15:04:03 LOG7[10620:10092]: SSL state (connect): SSLv3 write change cipher spec A 2013.06.26 15:04:03 LOG7[10620:10092]: SSL state (connect): SSLv3 write finished A 2013.06.26 15:04:03 LOG7[10620:10092]: SSL state (connect): SSLv3 flush data 2013.06.26 15:04:03 LOG7[10620:10092]: 1 items in the session cache 2013.06.26 15:04:03 LOG7[10620:10092]: 6 client connects (SSL_connect()) 2013.06.26 15:04:03 LOG7[10620:10092]: 6 client connects that finished 2013.06.26 15:04:03 LOG7[10620:10092]: 0 client renegotiations requested 2013.06.26 15:04:03 LOG7[10620:10092]: 0 server connects (SSL_accept()) 2013.06.26 15:04:03 LOG7[10620:10092]: 0 server connects that finished 2013.06.26 15:04:03 LOG7[10620:10092]: 0 server renegotiations requested 2013.06.26 15:04:03 LOG7[10620:10092]: 5 session cache hits 2013.06.26 15:04:03 LOG7[10620:10092]: 0 external session cache hits 2013.06.26 15:04:03 LOG7[10620:10092]: 0 session cache misses 2013.06.26 15:04:03 LOG7[10620:10092]: 0 session cache timeouts 2013.06.26 15:04:03 LOG6[10620:10092]: SSL connected: previous session reused 2013.06.26 15:04:04 LOG6[10620:10092]: SSL socket closed (SSL_read) 2013.06.26 15:04:04 LOG7[10620:10092]: Sent socket write shutdown 2013.06.26 15:04:04 LOG5[10620:10092]: Connection closed: 65 byte(s) sent to SSL, 290 byte(s) sent to socket 2013.06.26 15:04:04 LOG7[10620:10092]: Remote socket (FD=368) closed 2013.06.26 15:04:04 LOG7[10620:10092]: Local socket (FD=296) closed 2013.06.26 15:04:04 LOG7[10620:10092]: Service [smtps] finished (0 left) 2013.06.26 15:04:04 LOG7[10620:10992]: Service [smtps] accepted (FD=364) from 192.168.1.2:2952 2013.06.26 15:04:04 LOG7[10620:10992]: Creating a new thread 2013.06.26 15:04:04 LOG7[10620:10992]: New thread created 2013.06.26 15:04:04 LOG7[10620:1404]: Service [smtps] started 2013.06.26 15:04:04 LOG5[10620:1404]: Service [smtps] accepted connection from 192.168.1.2:2952 2013.06.26 15:04:04 LOG6[10620:1404]: connect_blocking: connecting 74.125.130.108:465 2013.06.26 15:04:04 LOG7[10620:1404]: connect_blocking: s_poll_wait 74.125.130.108:465: waiting 10 seconds 2013.06.26 15:04:04 LOG5[10620:1404]: connect_blocking: connected 74.125.130.108:465 2013.06.26 15:04:04 LOG5[10620:1404]: Service [smtps] connected remote server from 192.168.1.31:53646 2013.06.26 15:04:04 LOG7[10620:1404]: Remote socket (FD=368) initialized 2013.06.26 15:04:04 LOG7[10620:1404]: SNI: sending servername: smtp.gmail.com 2013.06.26 15:04:04 LOG7[10620:1404]: SSL state (connect): before/connect initialization 2013.06.26 15:04:04 LOG7[10620:1404]: SSL state (connect): SSLv3 write client hello A 2013.06.26 15:04:05 LOG7[10620:1404]: SSL state (connect): SSLv3 read server hello A 2013.06.26 15:04:05 LOG7[10620:1404]: SSL state (connect): SSLv3 read finished A 2013.06.26 15:04:05 LOG7[10620:1404]: SSL state (connect): SSLv3 write change cipher spec A 2013.06.26 15:04:05 LOG7[10620:1404]: SSL state (connect): SSLv3 write finished A 2013.06.26 15:04:05 LOG7[10620:1404]: SSL state (connect): SSLv3 flush data 2013.06.26 15:04:05 LOG7[10620:1404]: 1 items in the session cache 2013.06.26 15:04:05 LOG7[10620:1404]: 7 client connects (SSL_connect()) 2013.06.26 15:04:05 LOG7[10620:1404]: 7 client connects that finished 2013.06.26 15:04:05 LOG7[10620:1404]: 0 client renegotiations requested 2013.06.26 15:04:05 LOG7[10620:1404]: 0 server connects (SSL_accept()) 2013.06.26 15:04:05 LOG7[10620:1404]: 0 server connects that finished 2013.06.26 15:04:05 LOG7[10620:1404]: 0 server renegotiations requested 2013.06.26 15:04:05 LOG7[10620:1404]: 6 session cache hits 2013.06.26 15:04:05 LOG7[10620:1404]: 0 external session cache hits 2013.06.26 15:04:05 LOG7[10620:1404]: 0 session cache misses 2013.06.26 15:04:05 LOG7[10620:1404]: 0 session cache timeouts 2013.06.26 15:04:05 LOG6[10620:1404]: SSL connected: previous session reused 2013.06.26 15:04:05 LOG6[10620:1404]: SSL socket closed (SSL_read) 2013.06.26 15:04:05 LOG7[10620:1404]: Sent socket write shutdown 2013.06.26 15:04:05 LOG5[10620:1404]: Connection closed: 65 byte(s) sent to SSL, 290 byte(s) sent to socket 2013.06.26 15:04:05 LOG7[10620:1404]: Remote socket (FD=368) closed 2013.06.26 15:04:05 LOG7[10620:1404]: Local socket (FD=364) closed 2013.06.26 15:04:05 LOG7[10620:1404]: Service [smtps] finished (0 left) 2013.06.26 15:04:05 LOG7[10620:10992]: Service [smtps] accepted (FD=372) from 192.168.1.2:2953 2013.06.26 15:04:05 LOG7[10620:10992]: Creating a new thread 2013.06.26 15:04:05 LOG7[10620:10992]: New thread created 2013.06.26 15:04:05 LOG7[10620:11904]: Service [smtps] started 2013.06.26 15:04:05 LOG5[10620:11904]: Service [smtps] accepted connection from 192.168.1.2:2953 2013.06.26 15:04:05 LOG6[10620:11904]: connect_blocking: connecting 74.125.130.109:465 2013.06.26 15:04:05 LOG7[10620:11904]: connect_blocking: s_poll_wait 74.125.130.109:465: waiting 10 seconds 2013.06.26 15:04:06 LOG5[10620:11904]: connect_blocking: connected 74.125.130.109:465 2013.06.26 15:04:06 LOG5[10620:11904]: Service [smtps] connected remote server from 192.168.1.31:53647 2013.06.26 15:04:06 LOG7[10620:11904]: Remote socket (FD=368) initialized 2013.06.26 15:04:06 LOG7[10620:11904]: SNI: sending servername: smtp.gmail.com 2013.06.26 15:04:06 LOG7[10620:11904]: SSL state (connect): before/connect initialization 2013.06.26 15:04:06 LOG7[10620:11904]: SSL state (connect): SSLv3 write client hello A 2013.06.26 15:04:06 LOG7[10620:11904]: SSL state (connect): SSLv3 read server hello A 2013.06.26 15:04:06 LOG7[10620:11904]: SSL state (connect): SSLv3 read finished A 2013.06.26 15:04:06 LOG7[10620:11904]: SSL state (connect): SSLv3 write change cipher spec A 2013.06.26 15:04:06 LOG7[10620:11904]: SSL state (connect): SSLv3 write finished A 2013.06.26 15:04:06 LOG7[10620:11904]: SSL state (connect): SSLv3 flush data 2013.06.26 15:04:06 LOG7[10620:11904]: 1 items in the session cache 2013.06.26 15:04:06 LOG7[10620:11904]: 8 client connects (SSL_connect()) 2013.06.26 15:04:06 LOG7[10620:11904]: 8 client connects that finished 2013.06.26 15:04:06 LOG7[10620:11904]: 0 client renegotiations requested 2013.06.26 15:04:06 LOG7[10620:11904]: 0 server connects (SSL_accept()) 2013.06.26 15:04:06 LOG7[10620:11904]: 0 server connects that finished 2013.06.26 15:04:06 LOG7[10620:11904]: 0 server renegotiations requested 2013.06.26 15:04:06 LOG7[10620:11904]: 7 session cache hits 2013.06.26 15:04:06 LOG7[10620:11904]: 0 external session cache hits 2013.06.26 15:04:06 LOG7[10620:11904]: 0 session cache misses 2013.06.26 15:04:06 LOG7[10620:11904]: 0 session cache timeouts 2013.06.26 15:04:06 LOG6[10620:11904]: SSL connected: previous session reused 2013.06.26 15:04:06 LOG6[10620:11904]: SSL socket closed (SSL_read) 2013.06.26 15:04:06 LOG7[10620:11904]: Sent socket write shutdown 2013.06.26 15:04:06 LOG5[10620:11904]: Connection closed: 65 byte(s) sent to SSL, 290 byte(s) sent to socket 2013.06.26 15:04:06 LOG7[10620:11904]: Remote socket (FD=368) closed 2013.06.26 15:04:06 LOG7[10620:11904]: Local socket (FD=372) closed 2013.06.26 15:04:06 LOG7[10620:11904]: Service [smtps] finished (0 left) From: Stephen Gates [mailto:[email protected]] Sent: Wednesday, June 26, 2013 2:25 PM To: 'stunnel-users(a)stunnel.org' Subject: Sending Email from PLC Without Authentication with gmail A customer needs to send emails from a Programmable Logic Controller (PLC) which cannot provide authentication. The customer's email server is gmail which obviously requires authentication. The PLC IP is 192.168.1.2 and the PC IP on which stunnel is installed is 192.168.1.31 My config is: cert = stunnel.pem [smtps] client = yes accept = 25 connect = smtp.gmail.com:465 The PLC is set up to send emails to the IP of the PC 192.168.1.31 When I try to send emails I get the following in the stunnel log: 2013.06.26 14:26:30 LOG5[12384:13048]: Service [smtps] accepted connection from 192.168.1.2:2938 2013.06.26 14:26:30 LOG5[12384:13048]: connect_blocking: connected 74.125.130.108:465 2013.06.26 14:26:30 LOG5[12384:13048]: Service [smtps] connected remote server from 192.168.1.31:53599 Any help would be greatly appreciated! Stephen Gates Harold K. Scholz Company 7800 Serum Avenue Ralston, NE 68127 402-339-7600

1 0

Re: [stunnel-users] Sending Email from PLC Without Authentication with gmail
by Stephen Gates 26 Jun '13

26 Jun '13

I added the following as Bruce suggested. debug = 7 I tried doing output = stunnel.log but that cause an error when I reloded the config file. Here's the log after adding the above and trying to send another email. 2013.06.26 15:03:37 LOG7[10620:10992]: Service [smtps] (FD=416) bound to 0.0.0.0:25 2013.06.26 15:03:58 LOG7[10620:10992]: Service [smtps] accepted (FD=296) from 192.168.1.2:2946 2013.06.26 15:03:58 LOG7[10620:10992]: Creating a new thread 2013.06.26 15:03:58 LOG7[10620:10992]: New thread created 2013.06.26 15:03:58 LOG7[10620:10360]: Service [smtps] started 2013.06.26 15:03:58 LOG5[10620:10360]: Service [smtps] accepted connection from 192.168.1.2:2946 2013.06.26 15:03:58 LOG6[10620:10360]: connect_blocking: connecting 74.125.130.108:465 2013.06.26 15:03:58 LOG7[10620:10360]: connect_blocking: s_poll_wait 74.125.130.108:465: waiting 10 seconds 2013.06.26 15:03:58 LOG5[10620:10360]: connect_blocking: connected 74.125.130.108:465 2013.06.26 15:03:58 LOG5[10620:10360]: Service [smtps] connected remote server from 192.168.1.31:53640 2013.06.26 15:03:58 LOG7[10620:10360]: Remote socket (FD=368) initialized 2013.06.26 15:03:58 LOG7[10620:10360]: SNI: sending servername: smtp.gmail.com 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): before/connect initialization 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 write client hello A 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 read server hello A 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 read server certificate A 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 read server done A 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 write client key exchange A 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 write change cipher spec A 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 write finished A 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 flush data 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 read server session ticket A 2013.06.26 15:03:58 LOG7[10620:10360]: SSL state (connect): SSLv3 read finished A 2013.06.26 15:03:58 LOG7[10620:10360]: 1 items in the session cache 2013.06.26 15:03:58 LOG7[10620:10360]: 1 client connects (SSL_connect()) 2013.06.26 15:03:58 LOG7[10620:10360]: 1 client connects that finished 2013.06.26 15:03:58 LOG7[10620:10360]: 0 client renegotiations requested 2013.06.26 15:03:58 LOG7[10620:10360]: 0 server connects (SSL_accept()) 2013.06.26 15:03:58 LOG7[10620:10360]: 0 server connects that finished 2013.06.26 15:03:58 LOG7[10620:10360]: 0 server renegotiations requested 2013.06.26 15:03:58 LOG7[10620:10360]: 0 session cache hits 2013.06.26 15:03:58 LOG7[10620:10360]: 0 external session cache hits 2013.06.26 15:03:58 LOG7[10620:10360]: 0 session cache misses 2013.06.26 15:03:58 LOG7[10620:10360]: 0 session cache timeouts 2013.06.26 15:03:58 LOG7[10620:10360]: Peer certificate was cached (2266 bytes) 2013.06.26 15:03:58 LOG6[10620:10360]: SSL connected: new session negotiated 2013.06.26 15:03:58 LOG6[10620:10360]: Negotiated TLSv1/SSLv3 ciphersuite: AES128-SHA (128-bit encryption) 2013.06.26 15:03:58 LOG6[10620:10360]: Compression: null, expansion: null 2013.06.26 15:03:59 LOG6[10620:10360]: SSL socket closed (SSL_read) 2013.06.26 15:03:59 LOG7[10620:10360]: Sent socket write shutdown 2013.06.26 15:03:59 LOG5[10620:10360]: Connection closed: 65 byte(s) sent to SSL, 293 byte(s) sent to socket 2013.06.26 15:03:59 LOG7[10620:10360]: Remote socket (FD=368) closed 2013.06.26 15:03:59 LOG7[10620:10360]: Local socket (FD=296) closed 2013.06.26 15:03:59 LOG7[10620:10360]: Service [smtps] finished (0 left) 2013.06.26 15:03:59 LOG7[10620:10992]: Service [smtps] accepted (FD=364) from 192.168.1.2:2947 2013.06.26 15:03:59 LOG7[10620:10992]: Creating a new thread 2013.06.26 15:03:59 LOG7[10620:10992]: New thread created 2013.06.26 15:03:59 LOG7[10620:7792]: Service [smtps] started 2013.06.26 15:03:59 LOG5[10620:7792]: Service [smtps] accepted connection from 192.168.1.2:2947 2013.06.26 15:03:59 LOG6[10620:7792]: connect_blocking: connecting 74.125.130.109:465 2013.06.26 15:03:59 LOG7[10620:7792]: connect_blocking: s_poll_wait 74.125.130.109:465: waiting 10 seconds 2013.06.26 15:03:59 LOG5[10620:7792]: connect_blocking: connected 74.125.130.109:465 2013.06.26 15:03:59 LOG5[10620:7792]: Service [smtps] connected remote server from 192.168.1.31:53641 2013.06.26 15:03:59 LOG7[10620:7792]: Remote socket (FD=368) initialized 2013.06.26 15:03:59 LOG7[10620:7792]: SNI: sending servername: smtp.gmail.com 2013.06.26 15:03:59 LOG7[10620:7792]: SSL state (connect): before/connect initialization 2013.06.26 15:03:59 LOG7[10620:7792]: SSL state (connect): SSLv3 write client hello A 2013.06.26 15:03:59 LOG7[10620:7792]: SSL state (connect): SSLv3 read server hello A 2013.06.26 15:03:59 LOG7[10620:7792]: SSL state (connect): SSLv3 read finished A 2013.06.26 15:03:59 LOG7[10620:7792]: SSL state (connect): SSLv3 write change cipher spec A 2013.06.26 15:03:59 LOG7[10620:7792]: SSL state (connect): SSLv3 write finished A 2013.06.26 15:03:59 LOG7[10620:7792]: SSL state (connect): SSLv3 flush data 2013.06.26 15:03:59 LOG7[10620:7792]: 1 items in the session cache 2013.06.26 15:03:59 LOG7[10620:7792]: 2 client connects (SSL_connect()) 2013.06.26 15:03:59 LOG7[10620:7792]: 2 client connects that finished 2013.06.26 15:03:59 LOG7[10620:7792]: 0 client renegotiations requested 2013.06.26 15:03:59 LOG7[10620:7792]: 0 server connects (SSL_accept()) 2013.06.26 15:03:59 LOG7[10620:7792]: 0 server connects that finished 2013.06.26 15:03:59 LOG7[10620:7792]: 0 server renegotiations requested 2013.06.26 15:03:59 LOG7[10620:7792]: 1 session cache hits 2013.06.26 15:03:59 LOG7[10620:7792]: 0 external session cache hits 2013.06.26 15:03:59 LOG7[10620:7792]: 0 session cache misses 2013.06.26 15:03:59 LOG7[10620:7792]: 0 session cache timeouts 2013.06.26 15:03:59 LOG6[10620:7792]: SSL connected: previous session reused 2013.06.26 15:04:00 LOG6[10620:7792]: SSL socket closed (SSL_read) 2013.06.26 15:04:00 LOG7[10620:7792]: Sent socket write shutdown 2013.06.26 15:04:00 LOG5[10620:7792]: Connection closed: 65 byte(s) sent to SSL, 287 byte(s) sent to socket 2013.06.26 15:04:00 LOG7[10620:7792]: Remote socket (FD=368) closed 2013.06.26 15:04:00 LOG7[10620:7792]: Local socket (FD=364) closed 2013.06.26 15:04:00 LOG7[10620:7792]: Service [smtps] finished (0 left) 2013.06.26 15:04:00 LOG7[10620:10992]: Service [smtps] accepted (FD=372) from 192.168.1.2:2948 2013.06.26 15:04:00 LOG7[10620:10992]: Creating a new thread 2013.06.26 15:04:00 LOG7[10620:10992]: New thread created 2013.06.26 15:04:00 LOG7[10620:12944]: Service [smtps] started 2013.06.26 15:04:00 LOG5[10620:12944]: Service [smtps] accepted connection from 192.168.1.2:2948 2013.06.26 15:04:00 LOG6[10620:12944]: connect_blocking: connecting 74.125.130.108:465 2013.06.26 15:04:00 LOG7[10620:12944]: connect_blocking: s_poll_wait 74.125.130.108:465: waiting 10 seconds 2013.06.26 15:04:00 LOG5[10620:12944]: connect_blocking: connected 74.125.130.108:465 2013.06.26 15:04:00 LOG5[10620:12944]: Service [smtps] connected remote server from 192.168.1.31:53642 2013.06.26 15:04:00 LOG7[10620:12944]: Remote socket (FD=368) initialized 2013.06.26 15:04:00 LOG7[10620:12944]: SNI: sending servername: smtp.gmail.com 2013.06.26 15:04:00 LOG7[10620:12944]: SSL state (connect): before/connect initialization 2013.06.26 15:04:00 LOG7[10620:12944]: SSL state (connect): SSLv3 write client hello A 2013.06.26 15:04:00 LOG7[10620:12944]: SSL state (connect): SSLv3 read server hello A 2013.06.26 15:04:00 LOG7[10620:12944]: SSL state (connect): SSLv3 read finished A 2013.06.26 15:04:00 LOG7[10620:12944]: SSL state (connect): SSLv3 write change cipher spec A 2013.06.26 15:04:00 LOG7[10620:12944]: SSL state (connect): SSLv3 write finished A 2013.06.26 15:04:00 LOG7[10620:12944]: SSL state (connect): SSLv3 flush data 2013.06.26 15:04:00 LOG7[10620:12944]: 1 items in the session cache 2013.06.26 15:04:00 LOG7[10620:12944]: 3 client connects (SSL_connect()) 2013.06.26 15:04:00 LOG7[10620:12944]: 3 client connects that finished 2013.06.26 15:04:00 LOG7[10620:12944]: 0 client renegotiations requested 2013.06.26 15:04:00 LOG7[10620:12944]: 0 server connects (SSL_accept()) 2013.06.26 15:04:00 LOG7[10620:12944]: 0 server connects that finished 2013.06.26 15:04:00 LOG7[10620:12944]: 0 server renegotiations requested 2013.06.26 15:04:00 LOG7[10620:12944]: 2 session cache hits 2013.06.26 15:04:00 LOG7[10620:12944]: 0 external session cache hits 2013.06.26 15:04:00 LOG7[10620:12944]: 0 session cache misses 2013.06.26 15:04:00 LOG7[10620:12944]: 0 session cache timeouts 2013.06.26 15:04:00 LOG6[10620:12944]: SSL connected: previous session reused 2013.06.26 15:04:01 LOG6[10620:12944]: SSL socket closed (SSL_read) 2013.06.26 15:04:01 LOG7[10620:12944]: Sent socket write shutdown 2013.06.26 15:04:01 LOG5[10620:12944]: Connection closed: 65 byte(s) sent to SSL, 290 byte(s) sent to socket 2013.06.26 15:04:01 LOG7[10620:12944]: Remote socket (FD=368) closed 2013.06.26 15:04:01 LOG7[10620:12944]: Local socket (FD=372) closed 2013.06.26 15:04:01 LOG7[10620:12944]: Service [smtps] finished (0 left) 2013.06.26 15:04:01 LOG7[10620:10992]: Service [smtps] accepted (FD=288) from 192.168.1.2:2949 2013.06.26 15:04:01 LOG7[10620:10992]: Creating a new thread 2013.06.26 15:04:01 LOG7[10620:10992]: New thread created 2013.06.26 15:04:01 LOG7[10620:12900]: Service [smtps] started 2013.06.26 15:04:01 LOG5[10620:12900]: Service [smtps] accepted connection from 192.168.1.2:2949 2013.06.26 15:04:01 LOG6[10620:12900]: connect_blocking: connecting 74.125.130.109:465 2013.06.26 15:04:01 LOG7[10620:12900]: connect_blocking: s_poll_wait 74.125.130.109:465: waiting 10 seconds 2013.06.26 15:04:01 LOG5[10620:12900]: connect_blocking: connected 74.125.130.109:465 2013.06.26 15:04:01 LOG5[10620:12900]: Service [smtps] connected remote server from 192.168.1.31:53643 2013.06.26 15:04:01 LOG7[10620:12900]: Remote socket (FD=368) initialized 2013.06.26 15:04:01 LOG7[10620:12900]: SNI: sending servername: smtp.gmail.com 2013.06.26 15:04:01 LOG7[10620:12900]: SSL state (connect): before/connect initialization 2013.06.26 15:04:01 LOG7[10620:12900]: SSL state (connect): SSLv3 write client hello A 2013.06.26 15:04:01 LOG7[10620:12900]: SSL state (connect): SSLv3 read server hello A 2013.06.26 15:04:01 LOG7[10620:12900]: SSL state (connect): SSLv3 read finished A 2013.06.26 15:04:01 LOG7[10620:12900]: SSL state (connect): SSLv3 write change cipher spec A 2013.06.26 15:04:01 LOG7[10620:12900]: SSL state (connect): SSLv3 write finished A 2013.06.26 15:04:01 LOG7[10620:12900]: SSL state (connect): SSLv3 flush data 2013.06.26 15:04:01 LOG7[10620:12900]: 1 items in the session cache 2013.06.26 15:04:01 LOG7[10620:12900]: 4 client connects (SSL_connect()) 2013.06.26 15:04:01 LOG7[10620:12900]: 4 client connects that finished 2013.06.26 15:04:01 LOG7[10620:12900]: 0 client renegotiations requested 2013.06.26 15:04:01 LOG7[10620:12900]: 0 server connects (SSL_accept()) 2013.06.26 15:04:01 LOG7[10620:12900]: 0 server connects that finished 2013.06.26 15:04:01 LOG7[10620:12900]: 0 server renegotiations requested 2013.06.26 15:04:01 LOG7[10620:12900]: 3 session cache hits 2013.06.26 15:04:01 LOG7[10620:12900]: 0 external session cache hits 2013.06.26 15:04:01 LOG7[10620:12900]: 0 session cache misses 2013.06.26 15:04:01 LOG7[10620:12900]: 0 session cache timeouts 2013.06.26 15:04:01 LOG6[10620:12900]: SSL connected: previous session reused 2013.06.26 15:04:02 LOG6[10620:12900]: SSL socket closed (SSL_read) 2013.06.26 15:04:02 LOG7[10620:12900]: Sent socket write shutdown 2013.06.26 15:04:02 LOG5[10620:12900]: Connection closed: 65 byte(s) sent to SSL, 293 byte(s) sent to socket 2013.06.26 15:04:02 LOG7[10620:12900]: Remote socket (FD=368) closed 2013.06.26 15:04:02 LOG7[10620:12900]: Local socket (FD=288) closed 2013.06.26 15:04:02 LOG7[10620:12900]: Service [smtps] finished (0 left) 2013.06.26 15:04:02 LOG7[10620:10992]: Service [smtps] accepted (FD=292) from 192.168.1.2:2950 2013.06.26 15:04:02 LOG7[10620:10992]: Creating a new thread 2013.06.26 15:04:02 LOG7[10620:10992]: New thread created 2013.06.26 15:04:02 LOG7[10620:11560]: Service [smtps] started 2013.06.26 15:04:02 LOG5[10620:11560]: Service [smtps] accepted connection from 192.168.1.2:2950 2013.06.26 15:04:02 LOG6[10620:11560]: connect_blocking: connecting 74.125.130.108:465 2013.06.26 15:04:02 LOG7[10620:11560]: connect_blocking: s_poll_wait 74.125.130.108:465: waiting 10 seconds 2013.06.26 15:04:02 LOG5[10620:11560]: connect_blocking: connected 74.125.130.108:465 2013.06.26 15:04:02 LOG5[10620:11560]: Service [smtps] connected remote server from 192.168.1.31:53644 2013.06.26 15:04:02 LOG7[10620:11560]: Remote socket (FD=368) initialized 2013.06.26 15:04:02 LOG7[10620:11560]: SNI: sending servername: smtp.gmail.com 2013.06.26 15:04:02 LOG7[10620:11560]: SSL state (connect): before/connect initialization 2013.06.26 15:04:02 LOG7[10620:11560]: SSL state (connect): SSLv3 write client hello A 2013.06.26 15:04:02 LOG7[10620:11560]: SSL state (connect): SSLv3 read server hello A 2013.06.26 15:04:02 LOG7[10620:11560]: SSL state (connect): SSLv3 read finished A 2013.06.26 15:04:02 LOG7[10620:11560]: SSL state (connect): SSLv3 write change cipher spec A 2013.06.26 15:04:02 LOG7[10620:11560]: SSL state (connect): SSLv3 write finished A 2013.06.26 15:04:02 LOG7[10620:11560]: SSL state (connect): SSLv3 flush data 2013.06.26 15:04:02 LOG7[10620:11560]: 1 items in the session cache 2013.06.26 15:04:02 LOG7[10620:11560]: 5 client connects (SSL_connect()) 2013.06.26 15:04:02 LOG7[10620:11560]: 5 client connects that finished 2013.06.26 15:04:02 LOG7[10620:11560]: 0 client renegotiations requested 2013.06.26 15:04:02 LOG7[10620:11560]: 0 server connects (SSL_accept()) 2013.06.26 15:04:02 LOG7[10620:11560]: 0 server connects that finished 2013.06.26 15:04:02 LOG7[10620:11560]: 0 server renegotiations requested 2013.06.26 15:04:02 LOG7[10620:11560]: 4 session cache hits 2013.06.26 15:04:02 LOG7[10620:11560]: 0 external session cache hits 2013.06.26 15:04:02 LOG7[10620:11560]: 0 session cache misses 2013.06.26 15:04:02 LOG7[10620:11560]: 0 session cache timeouts 2013.06.26 15:04:02 LOG6[10620:11560]: SSL connected: previous session reused 2013.06.26 15:04:03 LOG6[10620:11560]: SSL socket closed (SSL_read) 2013.06.26 15:04:03 LOG7[10620:11560]: Sent socket write shutdown 2013.06.26 15:04:03 LOG5[10620:11560]: Connection closed: 65 byte(s) sent to SSL, 296 byte(s) sent to socket 2013.06.26 15:04:03 LOG7[10620:11560]: Remote socket (FD=368) closed 2013.06.26 15:04:03 LOG7[10620:11560]: Local socket (FD=292) closed 2013.06.26 15:04:03 LOG7[10620:11560]: Service [smtps] finished (0 left) 2013.06.26 15:04:03 LOG7[10620:10992]: Service [smtps] accepted (FD=296) from 192.168.1.2:2951 2013.06.26 15:04:03 LOG7[10620:10992]: Creating a new thread 2013.06.26 15:04:03 LOG7[10620:10992]: New thread created 2013.06.26 15:04:03 LOG7[10620:10092]: Service [smtps] started 2013.06.26 15:04:03 LOG5[10620:10092]: Service [smtps] accepted connection from 192.168.1.2:2951 2013.06.26 15:04:03 LOG6[10620:10092]: connect_blocking: connecting 74.125.130.109:465 2013.06.26 15:04:03 LOG7[10620:10092]: connect_blocking: s_poll_wait 74.125.130.109:465: waiting 10 seconds 2013.06.26 15:04:03 LOG5[10620:10092]: connect_blocking: connected 74.125.130.109:465 2013.06.26 15:04:03 LOG5[10620:10092]: Service [smtps] connected remote server from 192.168.1.31:53645 2013.06.26 15:04:03 LOG7[10620:10092]: Remote socket (FD=368) initialized 2013.06.26 15:04:03 LOG7[10620:10092]: SNI: sending servername: smtp.gmail.com 2013.06.26 15:04:03 LOG7[10620:10092]: SSL state (connect): before/connect initialization 2013.06.26 15:04:03 LOG7[10620:10092]: SSL state (connect): SSLv3 write client hello A 2013.06.26 15:04:03 LOG7[10620:10092]: SSL state (connect): SSLv3 read server hello A 2013.06.26 15:04:03 LOG7[10620:10092]: SSL state (connect): SSLv3 read finished A 2013.06.26 15:04:03 LOG7[10620:10092]: SSL state (connect): SSLv3 write change cipher spec A 2013.06.26 15:04:03 LOG7[10620:10092]: SSL state (connect): SSLv3 write finished A 2013.06.26 15:04:03 LOG7[10620:10092]: SSL state (connect): SSLv3 flush data 2013.06.26 15:04:03 LOG7[10620:10092]: 1 items in the session cache 2013.06.26 15:04:03 LOG7[10620:10092]: 6 client connects (SSL_connect()) 2013.06.26 15:04:03 LOG7[10620:10092]: 6 client connects that finished 2013.06.26 15:04:03 LOG7[10620:10092]: 0 client renegotiations requested 2013.06.26 15:04:03 LOG7[10620:10092]: 0 server connects (SSL_accept()) 2013.06.26 15:04:03 LOG7[10620:10092]: 0 server connects that finished 2013.06.26 15:04:03 LOG7[10620:10092]: 0 server renegotiations requested 2013.06.26 15:04:03 LOG7[10620:10092]: 5 session cache hits 2013.06.26 15:04:03 LOG7[10620:10092]: 0 external session cache hits 2013.06.26 15:04:03 LOG7[10620:10092]: 0 session cache misses 2013.06.26 15:04:03 LOG7[10620:10092]: 0 session cache timeouts 2013.06.26 15:04:03 LOG6[10620:10092]: SSL connected: previous session reused 2013.06.26 15:04:04 LOG6[10620:10092]: SSL socket closed (SSL_read) 2013.06.26 15:04:04 LOG7[10620:10092]: Sent socket write shutdown 2013.06.26 15:04:04 LOG5[10620:10092]: Connection closed: 65 byte(s) sent to SSL, 290 byte(s) sent to socket 2013.06.26 15:04:04 LOG7[10620:10092]: Remote socket (FD=368) closed 2013.06.26 15:04:04 LOG7[10620:10092]: Local socket (FD=296) closed 2013.06.26 15:04:04 LOG7[10620:10092]: Service [smtps] finished (0 left) 2013.06.26 15:04:04 LOG7[10620:10992]: Service [smtps] accepted (FD=364) from 192.168.1.2:2952 2013.06.26 15:04:04 LOG7[10620:10992]: Creating a new thread 2013.06.26 15:04:04 LOG7[10620:10992]: New thread created 2013.06.26 15:04:04 LOG7[10620:1404]: Service [smtps] started 2013.06.26 15:04:04 LOG5[10620:1404]: Service [smtps] accepted connection from 192.168.1.2:2952 2013.06.26 15:04:04 LOG6[10620:1404]: connect_blocking: connecting 74.125.130.108:465 2013.06.26 15:04:04 LOG7[10620:1404]: connect_blocking: s_poll_wait 74.125.130.108:465: waiting 10 seconds 2013.06.26 15:04:04 LOG5[10620:1404]: connect_blocking: connected 74.125.130.108:465 2013.06.26 15:04:04 LOG5[10620:1404]: Service [smtps] connected remote server from 192.168.1.31:53646 2013.06.26 15:04:04 LOG7[10620:1404]: Remote socket (FD=368) initialized 2013.06.26 15:04:04 LOG7[10620:1404]: SNI: sending servername: smtp.gmail.com 2013.06.26 15:04:04 LOG7[10620:1404]: SSL state (connect): before/connect initialization 2013.06.26 15:04:04 LOG7[10620:1404]: SSL state (connect): SSLv3 write client hello A 2013.06.26 15:04:05 LOG7[10620:1404]: SSL state (connect): SSLv3 read server hello A 2013.06.26 15:04:05 LOG7[10620:1404]: SSL state (connect): SSLv3 read finished A 2013.06.26 15:04:05 LOG7[10620:1404]: SSL state (connect): SSLv3 write change cipher spec A 2013.06.26 15:04:05 LOG7[10620:1404]: SSL state (connect): SSLv3 write finished A 2013.06.26 15:04:05 LOG7[10620:1404]: SSL state (connect): SSLv3 flush data 2013.06.26 15:04:05 LOG7[10620:1404]: 1 items in the session cache 2013.06.26 15:04:05 LOG7[10620:1404]: 7 client connects (SSL_connect()) 2013.06.26 15:04:05 LOG7[10620:1404]: 7 client connects that finished 2013.06.26 15:04:05 LOG7[10620:1404]: 0 client renegotiations requested 2013.06.26 15:04:05 LOG7[10620:1404]: 0 server connects (SSL_accept()) 2013.06.26 15:04:05 LOG7[10620:1404]: 0 server connects that finished 2013.06.26 15:04:05 LOG7[10620:1404]: 0 server renegotiations requested 2013.06.26 15:04:05 LOG7[10620:1404]: 6 session cache hits 2013.06.26 15:04:05 LOG7[10620:1404]: 0 external session cache hits 2013.06.26 15:04:05 LOG7[10620:1404]: 0 session cache misses 2013.06.26 15:04:05 LOG7[10620:1404]: 0 session cache timeouts 2013.06.26 15:04:05 LOG6[10620:1404]: SSL connected: previous session reused 2013.06.26 15:04:05 LOG6[10620:1404]: SSL socket closed (SSL_read) 2013.06.26 15:04:05 LOG7[10620:1404]: Sent socket write shutdown 2013.06.26 15:04:05 LOG5[10620:1404]: Connection closed: 65 byte(s) sent to SSL, 290 byte(s) sent to socket 2013.06.26 15:04:05 LOG7[10620:1404]: Remote socket (FD=368) closed 2013.06.26 15:04:05 LOG7[10620:1404]: Local socket (FD=364) closed 2013.06.26 15:04:05 LOG7[10620:1404]: Service [smtps] finished (0 left) 2013.06.26 15:04:05 LOG7[10620:10992]: Service [smtps] accepted (FD=372) from 192.168.1.2:2953 2013.06.26 15:04:05 LOG7[10620:10992]: Creating a new thread 2013.06.26 15:04:05 LOG7[10620:10992]: New thread created 2013.06.26 15:04:05 LOG7[10620:11904]: Service [smtps] started 2013.06.26 15:04:05 LOG5[10620:11904]: Service [smtps] accepted connection from 192.168.1.2:2953 2013.06.26 15:04:05 LOG6[10620:11904]: connect_blocking: connecting 74.125.130.109:465 2013.06.26 15:04:05 LOG7[10620:11904]: connect_blocking: s_poll_wait 74.125.130.109:465: waiting 10 seconds 2013.06.26 15:04:06 LOG5[10620:11904]: connect_blocking: connected 74.125.130.109:465 2013.06.26 15:04:06 LOG5[10620:11904]: Service [smtps] connected remote server from 192.168.1.31:53647 2013.06.26 15:04:06 LOG7[10620:11904]: Remote socket (FD=368) initialized 2013.06.26 15:04:06 LOG7[10620:11904]: SNI: sending servername: smtp.gmail.com 2013.06.26 15:04:06 LOG7[10620:11904]: SSL state (connect): before/connect initialization 2013.06.26 15:04:06 LOG7[10620:11904]: SSL state (connect): SSLv3 write client hello A 2013.06.26 15:04:06 LOG7[10620:11904]: SSL state (connect): SSLv3 read server hello A 2013.06.26 15:04:06 LOG7[10620:11904]: SSL state (connect): SSLv3 read finished A 2013.06.26 15:04:06 LOG7[10620:11904]: SSL state (connect): SSLv3 write change cipher spec A 2013.06.26 15:04:06 LOG7[10620:11904]: SSL state (connect): SSLv3 write finished A 2013.06.26 15:04:06 LOG7[10620:11904]: SSL state (connect): SSLv3 flush data 2013.06.26 15:04:06 LOG7[10620:11904]: 1 items in the session cache 2013.06.26 15:04:06 LOG7[10620:11904]: 8 client connects (SSL_connect()) 2013.06.26 15:04:06 LOG7[10620:11904]: 8 client connects that finished 2013.06.26 15:04:06 LOG7[10620:11904]: 0 client renegotiations requested 2013.06.26 15:04:06 LOG7[10620:11904]: 0 server connects (SSL_accept()) 2013.06.26 15:04:06 LOG7[10620:11904]: 0 server connects that finished 2013.06.26 15:04:06 LOG7[10620:11904]: 0 server renegotiations requested 2013.06.26 15:04:06 LOG7[10620:11904]: 7 session cache hits 2013.06.26 15:04:06 LOG7[10620:11904]: 0 external session cache hits 2013.06.26 15:04:06 LOG7[10620:11904]: 0 session cache misses 2013.06.26 15:04:06 LOG7[10620:11904]: 0 session cache timeouts 2013.06.26 15:04:06 LOG6[10620:11904]: SSL connected: previous session reused 2013.06.26 15:04:06 LOG6[10620:11904]: SSL socket closed (SSL_read) 2013.06.26 15:04:06 LOG7[10620:11904]: Sent socket write shutdown 2013.06.26 15:04:06 LOG5[10620:11904]: Connection closed: 65 byte(s) sent to SSL, 290 byte(s) sent to socket 2013.06.26 15:04:06 LOG7[10620:11904]: Remote socket (FD=368) closed 2013.06.26 15:04:06 LOG7[10620:11904]: Local socket (FD=372) closed 2013.06.26 15:04:06 LOG7[10620:11904]: Service [smtps] finished (0 left) From: Stephen Gates [mailto:[email protected]] Sent: Wednesday, June 26, 2013 2:25 PM To: 'stunnel-users(a)stunnel.org' Subject: Sending Email from PLC Without Authentication with gmail A customer needs to send emails from a Programmable Logic Controller (PLC) which cannot provide authentication. The customer's email server is gmail which obviously requires authentication. The PLC IP is 192.168.1.2 and the PC IP on which stunnel is installed is 192.168.1.31 My config is: cert = stunnel.pem [smtps] client = yes accept = 25 connect = smtp.gmail.com:465 The PLC is set up to send emails to the IP of the PC 192.168.1.31 When I try to send emails I get the following in the stunnel log: 2013.06.26 14:26:30 LOG5[12384:13048]: Service [smtps] accepted connection from 192.168.1.2:2938 2013.06.26 14:26:30 LOG5[12384:13048]: connect_blocking: connected 74.125.130.108:465 2013.06.26 14:26:30 LOG5[12384:13048]: Service [smtps] connected remote server from 192.168.1.31:53599 Any help would be greatly appreciated! Stephen Gates Harold K. Scholz Company 7800 Serum Avenue Ralston, NE 68127 402-339-7600

1 0

Re: [stunnel-users] "Broken pipe" issue
by Ron McWilliams 21 Jun '13

21 Jun '13

I have the same issue with the broken pipe on my stunnel. Here is the revealing log clip. appsadmin@MIRTHTEST:/etc/stunnel.d$ sudo tail -f /var/log/stunnel_mirth.log 2013.06.21 17:28:03 LOG7[30980:3077569344]: Service hl7_client prod finished (1 left) 2013.06.21 17:28:03 LOG7[30980:3077569344]: str_stats: 0 block(s), 0 data byte(s), 0 control byte(s) 2013.06.21 17:28:14 LOG6[30980:3073227584]: SSL connected: previous session reused 2013.06.21 17:28:14 LOG7[30980:3073227584]: Socket closed on read 2013.06.21 17:28:14 LOG7[30980:3073227584]: Sending SSL write shutdown 2013.06.21 17:28:14 LOG6[30980:3073227584]: SSL_shutdown successfully sent close_notify 2013.06.21 17:28:24 LOG5[30980:3073227584]: Error detected on socket (read) file descriptor: Broken pipe (32) 2013.06.21 17:28:24 LOG5[30980:3073227584]: Connection reset: 661 bytes sent to SSL, 124 bytes sent to socket 2013.06.21 17:28:24 LOG7[30980:3073227584]: Service hl7_client prod finished (0 left) 2013.06.21 17:28:24 LOG7[30980:3073227584]: str_stats: 0 block(s), 0 data byte(s), 0 control byte(s) Was there a simple edit to the conf file and if so, could you send the sample settings. Thank you, rmcwilli

1 0

Re: [stunnel-users] Broken pipes and TCP resets on parallel requests over stunnel
by Ron McWilliams 21 Jun '13

21 Jun '13

I have essentially the same issue. We were successfully sending messages and receiving ACK prior to this glitch. I am on Ubuntu 12.04 LTS using stunnel 4.50. appsadmin@MIRTHTEST:/etc/stunnel.d$ sudo tail -f /var/log/stunnel_mirth.log 2013.06.21 17:28:03 LOG7[30980:3077569344]: Service hl7_client prod finished (1 left) 2013.06.21 17:28:03 LOG7[30980:3077569344]: str_stats: 0 block(s), 0 data byte(s), 0 control byte(s) 2013.06.21 17:28:14 LOG6[30980:3073227584]: SSL connected: previous session reused 2013.06.21 17:28:14 LOG7[30980:3073227584]: Socket closed on read 2013.06.21 17:28:14 LOG7[30980:3073227584]: Sending SSL write shutdown 2013.06.21 17:28:14 LOG6[30980:3073227584]: SSL_shutdown successfully sent close_notify 2013.06.21 17:28:24 LOG5[30980:3073227584]: Error detected on socket (read) file descriptor: Broken pipe (32) 2013.06.21 17:28:24 LOG5[30980:3073227584]: Connection reset: 661 bytes sent to SSL, 124 bytes sent to socket 2013.06.21 17:28:24 LOG7[30980:3073227584]: Service hl7_client prod finished (0 left) 2013.06.21 17:28:24 LOG7[30980:3073227584]: str_stats: 0 block(s), 0 data byte(s), 0 control byte(s) rmcwilli

1 0