stunnel-users June 2013

stunnel-users@stunnel.org

19 participants
24 discussions

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:sgates@hkscholz.com] 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

stunnel FIPS mode 140-2/ Other Modes
by mehmet ozisik 24 Jun '13

24 Jun '13

Hi All, I would like to ask a question about stunnel fips mode. There are lots of question and answers on the internet related with this, but I could not find any answer related with mine. I am compiling with openssl (auto detecting fips) . Here is a part of confgiure output : checking for FIPS_mode_set... yes configure: FIPS mode detected So I am thinking that fips also is being included. Then I try to run stunnel on target platform (in stunnel.conf fips=yes) and it gives below error : Compiled/running with OpenSSL 0.9.8w-fips 23 Apr 2012 Threading:PTHREAD Sockets:POLL,IPv6 SSL:ENGINE,OCSP,FIPS Reading configuration from file stunnel.conf FIPS_mode_set: 2D06906E: error:2D06906E:FIPS routines:FIPS_CHECK_INCORE_FINGERPRINT:fingerprint does not match there are lots of information about this errror on internet. Then when I configure stunnel.conf with fips=no, stunnel is running successfully. I know that fips=yes means that enables FIPS 140-2 mode and I guess my fips canister does not supoort fips 140-2 mode (I do not know which fips mode it has supported). Now my question is coming : When I set fips=no, stunnel also starts with other available fips modes which the canister included? Or it skips running fips mode completely? Plase inform me if anyone has any idea? Regards

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

certificate verify failed
by Roman Tuchyna 19 Jun '13

19 Jun '13

Hi All, I'm trying to create SSl tunnel between my server (Win 2008 R2, 4.56 version of stunnel) and remote application server - I have merged both root and sub certificate into 1 file and it looks like it can verify them and accept them as well, but then it tries to verify it at depth=0 and says certificate not found in local repository. Am I missing anything here ? (I modified messages to not disclose details of certificates in the debug below). Thank you! BR, Roman 2013.06.18 11:22:34 LOG7[272:2156]: Service [SZX] started 2013.06.18 11:22:34 LOG5[272:2156]: Service [SZX] accepted connection from 127.0.0.1:49397 2013.06.18 11:22:34 LOG6[272:2156]: connect_blocking: connecting 10.254.0.21:443 2013.06.18 11:22:34 LOG7[272:2156]: connect_blocking: s_poll_wait 10.254.0.21:443: waiting 10 seconds 2013.06.18 11:22:34 LOG5[272:2156]: connect_blocking: connected 10.254.0.21:443 2013.06.18 11:22:34 LOG5[272:2156]: Service [SZX] connected remote server from 192.168.20.23:49398 2013.06.18 11:22:34 LOG7[272:2156]: Remote socket (FD=396) initialized 2013.06.18 11:22:34 LOG7[272:2156]: SNI: sending servername: 10.254.0.21 2013.06.18 11:22:34 LOG7[272:2156]: SSL state (connect): before/connect initialization 2013.06.18 11:22:34 LOG7[272:2156]: SSL state (connect): SSLv3 write client hello A 2013.06.18 11:22:34 LOG7[272:2156]: SSL state (connect): SSLv3 read server hello A 2013.06.18 11:22:34 LOG7[272:2156]: Starting certificate verification: depth=2, /CN=xxx RootCA 2013.06.18 11:22:34 LOG5[272:2156]: Certificate accepted: depth=2, /CN=xxx RootCA 2013.06.18 11:22:34 LOG7[272:2156]: Starting certificate verification: depth=1, /CN=xxx 2013.06.18 11:22:34 LOG5[272:2156]: Certificate accepted: depth=1, /CN=xxx SubCA1 2013.06.18 11:22:34 LOG7[272:2156]: Starting certificate verification: depth=0, /C=zzz 2013.06.18 11:22:34 LOG4[272:2156]: CERT: Certificate not found in local repository 2013.06.18 11:22:34 LOG4[272:2156]: Certificate check failed: depth=0, /C=zzz 2013.06.18 11:22:34 LOG7[272:2156]: SSL alert (write): fatal: certificate unknown 2013.06.18 11:22:34 LOG3[272:2156]: SSL_connect: 14090086: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed 2013.06.18 11:22:34 LOG5[272:2156]: Connection reset: 0 byte(s) sent to SSL, 0 byte(s) sent to socket 2013.06.18 11:22:34 LOG7[272:2156]: Remote socket (FD=396) closed 2013.06.18 11:22:34 LOG7[272:2156]: Local socket (FD=376) closed 2013.06.18 11:22:34 LOG7[272:2156]: Service [SZX] finished (0 left)

3 2

stunnel RHEL 6.3 and HTTPS header fields
by xxxxxxxxxxxxxxxxx 16 Jun '13

16 Jun '13

I'm an Stunnel newbie so forgive me if this question has been asked previously. I am using stunnel to accept a connection from http://127.0.0.1:someport/url/to/wsdland connect to hostname.somewhere.abc:443 Everything is working fine with the exception of a certain endpoint that responds with an HTTP status code of 403 "forbidden". What I have determined is that the server is rejecting the request due to the HTTP "Host:" field value, it's set to 127.0.0.1. Is there anyway to pass the value of the config file "connect" property instead (in my case "hostname.somewhere")?I have tried various config settings without success. Config entry: [testnesiis]client = yesaccept = 127.0.0.1:1445connect = testnesiis:443;protocolHost = testnesiis:443protocol = proxy;sni = testnesiis;transparent = both Thanks and Kudos to the authors of stunnel !

2 1

Certificate failure to verify with verify = 4 option
by Thomas Eifert 16 Jun '13

16 Jun '13

Greetings; Stunnel 4.56 running under Win 7 SP1 x86. Recently, the owners of a server I regularly connect to updated their server certificate; the former had expired at the end of May. As soon as that event occurred, I deleted the old certificate, then used the "save peer certificate" function of Stunnel to get the updated one. However, the new certificate fails to verify, even with the verify = 4 option in Stunnel. The error message is similar to what I used to get when doing a verify = 3 with some certificates. The general error output of Stunnel is: CERT: Verification error: unable to get local issuer certificate 2013.06.09 16:37:46 LOG4[608:2336]: Certificate check failed: depth=0 When I open the new certificate with: openssl x509 -text -in certname.pem and view the certificate details, I'm not seeing anything obvious. The certificate is within a valid date range, and contains the same basic elements as other certs I've viewed. The certificate appears to have been issued by Startcom LLC. If I comment out the verify statement, I'm able to successfully negotiate an SSL connection with the server. I realize that this may be more of an openssl issue than an issue with Stunnel. Nevertheless, I thought I'd start here and throw it out to the floor for comments. Anyone have any ideas or have run into this issue? Regards, Thomas -- 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.

2 2

tuning/multiple stunnel instance
by William Kwan 13 Jun '13

13 Jun '13

Dear all, I would like to find out if there's anyway to tune stunnel or what's the best practice you would recommend. I have a bit more than 100 sessions defined in stunnel.conf. It appears that clients started to see latency increase. Would you say 1. Split the conf file to multiple conf files and start multiple stunnel with each conf file? 2. Any way to tune stunnel to run muliple process with more threads? 3. Any other options? Thanks Will

2 1

stunnel doesn't create tunnel
by Roman Tuchyna 13 Jun '13

13 Jun '13

Hi All, I'm trying to create SSL tunnel between my server and remote application server and according to log file, stunnel fails to 0.0.0.0:43 Service [SZR] (FD=716) bound to 0.0.0.0:443 (although connect and accept are configured for this service). I'm using stunnel on Windows and apparently I'm doing something wrong - any hint or advice would be appreciated. I was searching for the reason, but couldn't find any pointer... Thank you! BR, Roman 2013.06.13 16:25:19 LOG7[2884:3032]: Dispatching signals from the signal pipe 2013.06.13 16:25:19 LOG7[2884:3032]: Processing SIGNAL_RELOAD_CONFIG 2013.06.13 16:25:19 LOG5[2884:3032]: Reading configuration from file stunnel.conf 2013.06.13 16:25:19 LOG5[2884:3032]: FIPS mode is enabled 2013.06.13 16:25:19 LOG7[2884:3032]: Compression not enabled 2013.06.13 16:25:19 LOG7[2884:3032]: Snagged 64 random bytes from C:/.rnd 2013.06.13 16:25:19 LOG7[2884:3032]: Wrote 1024 new random bytes to C:/.rnd 2013.06.13 16:25:19 LOG7[2884:3032]: PRNG seeded successfully 2013.06.13 16:25:19 LOG6[2884:3032]: Initializing service [SZR] 2013.06.13 16:25:19 LOG7[2884:3032]: Loaded verify certificates from SZR.pem 2013.06.13 16:25:19 LOG7[2884:3032]: Loaded SZR.pem revocation lookup file 2013.06.13 16:25:19 LOG7[2884:3032]: SSL options set: 0x01000004 2013.06.13 16:25:19 LOG5[2884:3032]: Configuration successful 2013.06.13 16:25:19 LOG7[2884:3032]: Closing service [SZR] 2013.06.13 16:25:19 LOG7[2884:3032]: Service [SZR] closed (FD=716) 2013.06.13 16:25:19 LOG7[2884:3032]: Sessions cached before flush: 0 2013.06.13 16:25:19 LOG7[2884:3032]: Sessions cached after flush: 0 2013.06.13 16:25:19 LOG7[2884:3032]: Service [SZR] closed 2013.06.13 16:25:19 LOG7[2884:3032]: Service [SZR] (FD=716) bound to 0.0.0.0:443 2013.06.13 16:25:19 LOG7[2884:3032]: Signal pipe is empty

1 0

Re: [stunnel-users] Getting Stunnel working with Verizon.net SMTP
by Gary Kuznitz 13 Jun '13

13 Jun '13

Hi Jochen, With your help I selected "Do not use CRAM-MD5 authentication even if it is advertised" It's now woking. Thank you very much for your help. Do you know if there is any way to remove the emails with the user name and password from the archives? Thanks, Gary On 12 Jun 2013 at 23:08, Jochen (Jochen Bern <Jochen.Bern(a)LINworks.de>) commented about Re: [stunnel-users] Getting Stunnel working with : > On 12.06.2013 21:28, Gary Kuznitz wrote: > > On your first post I didn't see the difference in port numbers. I have corrected that. > > I'm getting this log from my email client: > > --- Wed, 12 Jun 2013 12:22:46 --- > > Connect to 'localhost' port 10115, timeout 60. > > 12:22:46.960 [*] Connection established to 127.0.0.1 > > 12:22:47.226 >> 0120 220 vms173007pub.verizon.net -- Server ESMTP (Sun Java(tm) > > System Messaging Server 7u2-7.02 32bit (built Apr 16 2009))\0D\0A > > First and foremost, this shows that your e-mail client can now talk to > the server, which means that stunnel's job (the SSL negotiation) gets > done successfully. > > > 12:22:47.288 >> 0042 250-AUTH DIGEST-MD5 PLAIN LOGIN CRAM-MD5\0D\0A > > 12:22:47.288 >> 0022 250-AUTH=LOGIN PLAIN\0D\0A > > This part of the server's reply to the EHLO command shows the auth > mechanisms the server supports; CRAM-MD5 is listed ... > > > 12:22:47.288 << 0015 AUTH CRAM-MD5\0D\0A > > ... and your client requests it. > > > 12:22:47.335 >> 0050 334 PDEzNTYyOTY5MjEuMTIxMTA1NTFAdm1zMTczMDA3Pg==\0D\0A > > The servers issues (a base64 encoded version of) > "<1356296921.12110551@vms173007>" as a "random" string challenge. > > > 12:22:47.335 << 0058 YXR1cHJlcyBkYTlmZTI3MWFjODNjYWUxOTVjNmZhZWQ5ZGE0NTUzYg==\0D\0A > > This is a base64 encoded version of "atupres > da9fe271ac83cae195c6faed9da4553b". "atupres" should be your username and > da9fe271ac83cae195c6faed9da4553b the HMAC-MD5 digest of the challenge > with your password as the key. > > I don't know a tool to compute HMAC-MD5 digests that is readily > available under Windows, I'm afraid. If you're desperate, try > http://www.freeformatter.com/hmac-generator.html > (note that they won't know a) on which server and b) with what username > you'll be using the password ...). > > > 12:22:47.397 >> 0066 500 5.7.0 Unknown AUTH error -1 (Internal authentication error).\0D\0A > > ... and there the server says it cannot verify that. > > > Do you have any idea why I am getting [that]? > > I can think of several *possible* reasons, but ultimately, the server > doesn't tell us what exactly is wrong. > > 1. It may be that the server is announcing CRAM-MD5 auth though it > actually does *not* support it. (The DIGEST-MD5 and CRAM-MD5 mechs > require that the server *knows* the (plaintext) password, while for > PLAIN and LOGIN, storing only a hash of the password is enough, and > foils attackers who manage to steal a copy of the password database.) > Enforcing use of a different mechanism can probably be done through > your e-mail client's settings, but I'm afraid that it's usually > rather cryptic how exactly to do that ... > If you want to have a *manual* try at another mech, here's a web > page explaining what to input for PLAIN and LOGIN: > http://www.gadgetwiz.com/protocols/smtp-auth-example.html > and here's an MS KB article with a base64 en-/decoder: > http://support.microsoft.com/kb/191239 > Problem is that the strings to be base64 encoded are supposed *not* > to have an end-of-line, and sometimes even to contain NUL bytes > ("\0") ... Verify that your method of choice properly reproduces the > examples in the howto page. :-C > 2. I'm a bit surprised that your username supposedly is "atupres", > rather than "atupres(a)your.dom.ain", "atupres%your.dom.ain" or > something to that effect ... ? > 3. The obvious one, a mistyped password ... > > Regards, > J. Bern > -- > *NEU* - NEC IT-Infrastruktur-Produkte im <http://www.linworks-shop.de/>: > Server--Storage--Virtualisierung--Management SW--Passion for Performance > Jochen Bern, Systemingenieur --- LINworks GmbH <http://www.LINworks.de/> > Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt > PGP (1024D/4096g) FP = D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C27 > Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202 > Unternehmenssitz Weiterstadt, Geschäftsführer Metin Dogan, Oliver Michel

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

stunnel-users June 2013