- stunnel-users - stunnel.org

Re: [stunnel-users] Stunnel and Outlook Web Access Problems
by Craig Retief 20 Nov '07

20 Nov '07

I see that you have client = yes in the config file. When client = yes is set outside the service block, it becomes a global setting that tells all the services that it should tunnel that they are clients and not servers. If you specify the client = yes within a service eg. [pop3s] client = yes accept = 995 connect = 110 then stunnel knows that the specified service alone is a client. What I recommend is that you disable the client = yes in the global area and change you config file to something like this: I have removed the comments to shorten the config for explanation: socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 CRLpath = crls CRLfile = certnew.pem debug = 7 output = stunnel.log ;client = yes [https] accept = 443 connect = 192.168.0.5:443 TIMEOUTclose = 0 Try using this as your config and see if it works or not. Cheers Craig From: Dan Vespa [mailto:dan@sideshow.sytes.net] Sent: 19 November 2007 05:07 PM To: Craig Retief Subject: RE: [stunnel-users] Stunnel and Outlook Web Access Problems Craig, Here it is.... ; Sample stunnel configuration file by Michal Trojnara 2002-2006 ; Some options used here may not be adequate for your particular configuration ; Certificate/key is needed in server mode and optional in client mode ; The default certificate is provided only for testing and should not ; be used in a production environment ;cert = stunnel.pem ;key = stunnel.pem ; Some performance tunings socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 ; Workaround for Eudora bug ;options = DONT_INSERT_EMPTY_FRAGMENTS ; Authentication stuff ;verify = 2 ; Don't forget to c_rehash CApath ;CApath = crls ; It's often easier to use CAfile ;CAfile = certnew.pem ; Don't forget to c_rehash CRLpath CRLpath = crls ; Alternatively you can use CRLfile CRLfile = certnew.pem ; Some debugging stuff useful for troubleshooting debug = 7 output = stunnel.log ; Use it for client mode client = yes ; Service-level configuration ;[pop3s] ;accept = 995 ;connect = 110 ;[imaps] ;accept = 993 ;connect = 143 ;[ssmtp] ;accept = 465 ;connect = 25 [https] accept = 443 connect = 192.168.0.5:443 TIMEOUTclose = 0 ; vim:ft=dosini _____ From: Craig Retief Sent: Mon 19/11/2007 9:54 AM To: 'Dan Vespa' Cc: stunnel-users(a)mirt.net Subject: RE: [stunnel-users] Stunnel and Outlook Web Access Problems Please Post your stunnel configs. Makes life easier. Cheers Craig From: Dan Vespa [mailto:dan@sideshow.sytes.net] Sent: 19 November 2007 03:35 PM To: Craig Subject: RE: [stunnel-users] Stunnel and Outlook Web Access Problems Craig, I set the debug level higher and this is what my log outputs.... 2007.11.19 08:25:54 LOG7[1596:2656]: RAND_status claims sufficient entropy for the PRNG 2007.11.19 08:25:54 LOG7[1596:2656]: PRNG seeded successfully 2007.11.19 08:25:54 LOG7[1596:2656]: SSL context initialized for service https 2007.11.19 08:25:54 LOG5[1596:2656]: stunnel 4.21 on x86-pc-mingw32-gnu with OpenSSL 0.9.8g 19 Oct 2007 2007.11.19 08:25:54 LOG5[1596:2656]: Threading:WIN32 SSL:ENGINE Sockets:SELECT,IPv6 2007.11.19 08:25:54 LOG5[1596:3012]: No limit detected for the number of clients 2007.11.19 08:25:54 LOG7[1596:3012]: FD 188 in non-blocking mode 2007.11.19 08:25:54 LOG7[1596:3012]: SO_REUSEADDR option set on accept socket 2007.11.19 08:25:54 LOG7[1596:3012]: https bound to 0.0.0.0:443 2007.11.19 08:26:32 LOG7[1596:3012]: https accepted FD=236 from 127.0.0.1:1409 2007.11.19 08:26:32 LOG7[1596:3012]: Creating a new thread 2007.11.19 08:26:32 LOG7[1596:3012]: New thread created 2007.11.19 08:26:32 LOG7[1596:2576]: https started 2007.11.19 08:26:32 LOG7[1596:2576]: FD 236 in non-blocking mode 2007.11.19 08:26:32 LOG7[1596:2576]: TCP_NODELAY option set on local socket 2007.11.19 08:26:32 LOG5[1596:2576]: https accepted connection from 127.0.0.1:1409 2007.11.19 08:26:32 LOG7[1596:2576]: FD 260 in non-blocking mode 2007.11.19 08:26:32 LOG7[1596:2576]: https connecting 192.168.0.5:443 2007.11.19 08:26:32 LOG7[1596:2576]: connect_wait: waiting 10 seconds 2007.11.19 08:26:32 LOG7[1596:2576]: connect_wait: connected 2007.11.19 08:26:32 LOG5[1596:2576]: https connected remote server from 192.168.0.24:1410 2007.11.19 08:26:32 LOG7[1596:2576]: Remote FD=260 initialized 2007.11.19 08:26:32 LOG7[1596:2576]: TCP_NODELAY option set on remote socket 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): before/connect initialization 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 write client hello A 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 read server hello A 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 read server certificate A 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 read server done A 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 write client key exchange A 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 write change cipher spec A 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 write finished A 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 flush data 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 read finished A 2007.11.19 08:26:32 LOG7[1596:2576]: 1 items in the session cache 2007.11.19 08:26:32 LOG7[1596:2576]: 1 client connects (SSL_connect()) 2007.11.19 08:26:32 LOG7[1596:2576]: 1 client connects that finished 2007.11.19 08:26:32 LOG7[1596:2576]: 0 client renegotiations requested 2007.11.19 08:26:32 LOG7[1596:2576]: 0 server connects (SSL_accept()) 2007.11.19 08:26:32 LOG7[1596:2576]: 0 server connects that finished 2007.11.19 08:26:32 LOG7[1596:2576]: 0 server renegotiations requested 2007.11.19 08:26:32 LOG7[1596:2576]: 0 session cache hits 2007.11.19 08:26:32 LOG7[1596:2576]: 0 session cache misses 2007.11.19 08:26:32 LOG7[1596:2576]: 0 session cache timeouts 2007.11.19 08:26:32 LOG6[1596:2576]: SSL connected: new session negotiated 2007.11.19 08:26:32 LOG6[1596:2576]: Negotiated ciphers: RC4-MD5 SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 2007.11.19 08:26:53 LOG7[1596:3012]: https accepted FD=288 from 127.0.0.1:1411 2007.11.19 08:26:53 LOG7[1596:3012]: Creating a new thread 2007.11.19 08:26:53 LOG7[1596:3012]: New thread created 2007.11.19 08:26:53 LOG7[1596:1060]: https started 2007.11.19 08:26:53 LOG7[1596:1060]: FD 288 in non-blocking mode 2007.11.19 08:26:53 LOG7[1596:1060]: TCP_NODELAY option set on local socket 2007.11.19 08:26:53 LOG5[1596:1060]: https accepted connection from 127.0.0.1:1411 2007.11.19 08:26:53 LOG7[1596:1060]: FD 312 in non-blocking mode 2007.11.19 08:26:53 LOG7[1596:1060]: https connecting 192.168.0.5:443 2007.11.19 08:26:53 LOG7[1596:1060]: connect_wait: waiting 10 seconds 2007.11.19 08:26:53 LOG7[1596:1060]: connect_wait: connected 2007.11.19 08:26:53 LOG5[1596:1060]: https connected remote server from 192.168.0.24:1412 2007.11.19 08:26:53 LOG7[1596:1060]: Remote FD=312 initialized 2007.11.19 08:26:53 LOG7[1596:1060]: TCP_NODELAY option set on remote socket 2007.11.19 08:26:53 LOG7[1596:1060]: SSL state (connect): before/connect initialization 2007.11.19 08:26:53 LOG7[1596:1060]: SSL state (connect): SSLv3 write client hello A 2007.11.19 08:26:53 LOG7[1596:1060]: SSL state (connect): SSLv3 read server hello A 2007.11.19 08:26:53 LOG7[1596:1060]: SSL state (connect): SSLv3 read finished A 2007.11.19 08:26:53 LOG7[1596:1060]: SSL state (connect): SSLv3 write change cipher spec A 2007.11.19 08:26:53 LOG7[1596:1060]: SSL state (connect): SSLv3 write finished A 2007.11.19 08:26:53 LOG7[1596:1060]: SSL state (connect): SSLv3 flush data 2007.11.19 08:26:53 LOG7[1596:1060]: 1 items in the session cache 2007.11.19 08:26:53 LOG7[1596:1060]: 2 client connects (SSL_connect()) 2007.11.19 08:26:53 LOG7[1596:1060]: 2 client connects that finished 2007.11.19 08:26:53 LOG7[1596:1060]: 0 client renegotiations requested 2007.11.19 08:26:53 LOG7[1596:1060]: 0 server connects (SSL_accept()) 2007.11.19 08:26:53 LOG7[1596:1060]: 0 server connects that finished 2007.11.19 08:26:53 LOG7[1596:1060]: 0 server renegotiations requested 2007.11.19 08:26:53 LOG7[1596:1060]: 1 session cache hits 2007.11.19 08:26:53 LOG7[1596:1060]: 0 session cache misses 2007.11.19 08:26:53 LOG7[1596:1060]: 0 session cache timeouts 2007.11.19 08:26:53 LOG6[1596:1060]: SSL connected: previous session reused 2007.11.19 08:26:53 LOG7[1596:1060]: SSL socket closed on SSL_read 2007.11.19 08:26:53 LOG7[1596:1060]: Socket write shutdown 2007.11.19 08:26:53 LOG5[1596:1060]: Connection closed: 70 bytes sent to SSL, 164 bytes sent to socket 2007.11.19 08:26:53 LOG7[1596:1060]: https finished (1 left) 2007.11.19 08:27:53 LOG3[1596:2576]: readsocket: Connection reset by peer (WSAECONNRESET) (10054) 2007.11.19 08:27:53 LOG5[1596:2576]: Connection reset: 1102 bytes sent to SSL, 1241 bytes sent to socket 2007.11.19 08:27:53 LOG7[1596:2576]: https finished (0 left) Does this make any sense to you???? Dan _____ From: Craig Sent: Mon 19/11/2007 1:34 AM To: stunnel-users(a)mirt.net Subject: Re: [stunnel-users] Stunnel and Outlook Web Access Problems OWA rewrites the URL when you log in and I have found that it causes problems when doing that with a Stunnel connection. What I think might be happening is that your initial connection says http://server.tld/ then when you log in OWA rewrites the URL to https://server.tld/ What I think is happening is that your stunnel is listening on port 80 and when you log in, OWA changes the listening port in the browser to port 443. Try running the listening server (stunnel server) to listen on port 443 instead of port 80 and see if that fixes the problem. Cheers Craig From: stunnel-users-bounces(a)mirt.net [mailto:stunnel-users-bounces@mirt.net] On Behalf Of Dan Vespa Sent: 17 November 2007 07:21 PM To: stunnel-users(a)mirt.net Subject: [stunnel-users] Stunnel and Outlook Web Access Problems I am trying to use the latest version of stunnel to connect to OWA. I set stunnel to listen on port 80 (localhost) and then connect to myserverip on port 443. I get the login screen but can go no further after I Enter my credentials and Click OK. Checking the stunnel log screen it shows that a connect has been made? I don't understand why It won't connect any further?? OWA is on Exchange Server 2003 and I am using Windows XP SP2. I have also updated to Open SSL latest version. Thanks in Advance. Dan

1 0

Re: [stunnel-users] Stunnel and Outlook Web Access Problems
by Craig Retief 19 Nov '07

19 Nov '07

Please Post your stunnel configs. Makes life easier. Cheers Craig From: Dan Vespa [mailto:dan@sideshow.sytes.net] Sent: 19 November 2007 03:35 PM To: Craig Subject: RE: [stunnel-users] Stunnel and Outlook Web Access Problems Craig, I set the debug level higher and this is what my log outputs.... 2007.11.19 08:25:54 LOG7[1596:2656]: RAND_status claims sufficient entropy for the PRNG 2007.11.19 08:25:54 LOG7[1596:2656]: PRNG seeded successfully 2007.11.19 08:25:54 LOG7[1596:2656]: SSL context initialized for service https 2007.11.19 08:25:54 LOG5[1596:2656]: stunnel 4.21 on x86-pc-mingw32-gnu with OpenSSL 0.9.8g 19 Oct 2007 2007.11.19 08:25:54 LOG5[1596:2656]: Threading:WIN32 SSL:ENGINE Sockets:SELECT,IPv6 2007.11.19 08:25:54 LOG5[1596:3012]: No limit detected for the number of clients 2007.11.19 08:25:54 LOG7[1596:3012]: FD 188 in non-blocking mode 2007.11.19 08:25:54 LOG7[1596:3012]: SO_REUSEADDR option set on accept socket 2007.11.19 08:25:54 LOG7[1596:3012]: https bound to 0.0.0.0:443 2007.11.19 08:26:32 LOG7[1596:3012]: https accepted FD=236 from 127.0.0.1:1409 2007.11.19 08:26:32 LOG7[1596:3012]: Creating a new thread 2007.11.19 08:26:32 LOG7[1596:3012]: New thread created 2007.11.19 08:26:32 LOG7[1596:2576]: https started 2007.11.19 08:26:32 LOG7[1596:2576]: FD 236 in non-blocking mode 2007.11.19 08:26:32 LOG7[1596:2576]: TCP_NODELAY option set on local socket 2007.11.19 08:26:32 LOG5[1596:2576]: https accepted connection from 127.0.0.1:1409 2007.11.19 08:26:32 LOG7[1596:2576]: FD 260 in non-blocking mode 2007.11.19 08:26:32 LOG7[1596:2576]: https connecting 192.168.0.5:443 2007.11.19 08:26:32 LOG7[1596:2576]: connect_wait: waiting 10 seconds 2007.11.19 08:26:32 LOG7[1596:2576]: connect_wait: connected 2007.11.19 08:26:32 LOG5[1596:2576]: https connected remote server from 192.168.0.24:1410 2007.11.19 08:26:32 LOG7[1596:2576]: Remote FD=260 initialized 2007.11.19 08:26:32 LOG7[1596:2576]: TCP_NODELAY option set on remote socket 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): before/connect initialization 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 write client hello A 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 read server hello A 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 read server certificate A 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 read server done A 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 write client key exchange A 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 write change cipher spec A 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 write finished A 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 flush data 2007.11.19 08:26:32 LOG7[1596:2576]: SSL state (connect): SSLv3 read finished A 2007.11.19 08:26:32 LOG7[1596:2576]: 1 items in the session cache 2007.11.19 08:26:32 LOG7[1596:2576]: 1 client connects (SSL_connect()) 2007.11.19 08:26:32 LOG7[1596:2576]: 1 client connects that finished 2007.11.19 08:26:32 LOG7[1596:2576]: 0 client renegotiations requested 2007.11.19 08:26:32 LOG7[1596:2576]: 0 server connects (SSL_accept()) 2007.11.19 08:26:32 LOG7[1596:2576]: 0 server connects that finished 2007.11.19 08:26:32 LOG7[1596:2576]: 0 server renegotiations requested 2007.11.19 08:26:32 LOG7[1596:2576]: 0 session cache hits 2007.11.19 08:26:32 LOG7[1596:2576]: 0 session cache misses 2007.11.19 08:26:32 LOG7[1596:2576]: 0 session cache timeouts 2007.11.19 08:26:32 LOG6[1596:2576]: SSL connected: new session negotiated 2007.11.19 08:26:32 LOG6[1596:2576]: Negotiated ciphers: RC4-MD5 SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 2007.11.19 08:26:53 LOG7[1596:3012]: https accepted FD=288 from 127.0.0.1:1411 2007.11.19 08:26:53 LOG7[1596:3012]: Creating a new thread 2007.11.19 08:26:53 LOG7[1596:3012]: New thread created 2007.11.19 08:26:53 LOG7[1596:1060]: https started 2007.11.19 08:26:53 LOG7[1596:1060]: FD 288 in non-blocking mode 2007.11.19 08:26:53 LOG7[1596:1060]: TCP_NODELAY option set on local socket 2007.11.19 08:26:53 LOG5[1596:1060]: https accepted connection from 127.0.0.1:1411 2007.11.19 08:26:53 LOG7[1596:1060]: FD 312 in non-blocking mode 2007.11.19 08:26:53 LOG7[1596:1060]: https connecting 192.168.0.5:443 2007.11.19 08:26:53 LOG7[1596:1060]: connect_wait: waiting 10 seconds 2007.11.19 08:26:53 LOG7[1596:1060]: connect_wait: connected 2007.11.19 08:26:53 LOG5[1596:1060]: https connected remote server from 192.168.0.24:1412 2007.11.19 08:26:53 LOG7[1596:1060]: Remote FD=312 initialized 2007.11.19 08:26:53 LOG7[1596:1060]: TCP_NODELAY option set on remote socket 2007.11.19 08:26:53 LOG7[1596:1060]: SSL state (connect): before/connect initialization 2007.11.19 08:26:53 LOG7[1596:1060]: SSL state (connect): SSLv3 write client hello A 2007.11.19 08:26:53 LOG7[1596:1060]: SSL state (connect): SSLv3 read server hello A 2007.11.19 08:26:53 LOG7[1596:1060]: SSL state (connect): SSLv3 read finished A 2007.11.19 08:26:53 LOG7[1596:1060]: SSL state (connect): SSLv3 write change cipher spec A 2007.11.19 08:26:53 LOG7[1596:1060]: SSL state (connect): SSLv3 write finished A 2007.11.19 08:26:53 LOG7[1596:1060]: SSL state (connect): SSLv3 flush data 2007.11.19 08:26:53 LOG7[1596:1060]: 1 items in the session cache 2007.11.19 08:26:53 LOG7[1596:1060]: 2 client connects (SSL_connect()) 2007.11.19 08:26:53 LOG7[1596:1060]: 2 client connects that finished 2007.11.19 08:26:53 LOG7[1596:1060]: 0 client renegotiations requested 2007.11.19 08:26:53 LOG7[1596:1060]: 0 server connects (SSL_accept()) 2007.11.19 08:26:53 LOG7[1596:1060]: 0 server connects that finished 2007.11.19 08:26:53 LOG7[1596:1060]: 0 server renegotiations requested 2007.11.19 08:26:53 LOG7[1596:1060]: 1 session cache hits 2007.11.19 08:26:53 LOG7[1596:1060]: 0 session cache misses 2007.11.19 08:26:53 LOG7[1596:1060]: 0 session cache timeouts 2007.11.19 08:26:53 LOG6[1596:1060]: SSL connected: previous session reused 2007.11.19 08:26:53 LOG7[1596:1060]: SSL socket closed on SSL_read 2007.11.19 08:26:53 LOG7[1596:1060]: Socket write shutdown 2007.11.19 08:26:53 LOG5[1596:1060]: Connection closed: 70 bytes sent to SSL, 164 bytes sent to socket 2007.11.19 08:26:53 LOG7[1596:1060]: https finished (1 left) 2007.11.19 08:27:53 LOG3[1596:2576]: readsocket: Connection reset by peer (WSAECONNRESET) (10054) 2007.11.19 08:27:53 LOG5[1596:2576]: Connection reset: 1102 bytes sent to SSL, 1241 bytes sent to socket 2007.11.19 08:27:53 LOG7[1596:2576]: https finished (0 left) Does this make any sense to you???? Dan _____ From: Craig Sent: Mon 19/11/2007 1:34 AM To: stunnel-users(a)mirt.net Subject: Re: [stunnel-users] Stunnel and Outlook Web Access Problems OWA rewrites the URL when you log in and I have found that it causes problems when doing that with a Stunnel connection. What I think might be happening is that your initial connection says http://server.tld/ then when you log in OWA rewrites the URL to https://server.tld/ What I think is happening is that your stunnel is listening on port 80 and when you log in, OWA changes the listening port in the browser to port 443. Try running the listening server (stunnel server) to listen on port 443 instead of port 80 and see if that fixes the problem. Cheers Craig From: stunnel-users-bounces(a)mirt.net [mailto:stunnel-users-bounces@mirt.net] On Behalf Of Dan Vespa Sent: 17 November 2007 07:21 PM To: stunnel-users(a)mirt.net Subject: [stunnel-users] Stunnel and Outlook Web Access Problems I am trying to use the latest version of stunnel to connect to OWA. I set stunnel to listen on port 80 (localhost) and then connect to myserverip on port 443. I get the login screen but can go no further after I Enter my credentials and Click OK. Checking the stunnel log screen it shows that a connect has been made? I don't understand why It won't connect any further?? OWA is on Exchange Server 2003 and I am using Windows XP SP2. I have also updated to Open SSL latest version. Thanks in Advance. Dan

1 0

Stunnel and Outlook Web Access Problems
by Dan Vespa 19 Nov '07

19 Nov '07

I am trying to use the latest version of stunnel to connect to OWA. I set stunnel to listen on port 80 (localhost) and then connect to myserverip on port 443. I get the login screen but can go no further after I Enter my credentials and Click OK. Checking the stunnel log screen it shows that a connect has been made? I don't understand why It won't connect any further?? OWA is on Exchange Server 2003 and I am using Windows XP SP2. I have also updated to Open SSL latest version. Thanks in Advance. Dan

2 1

NFS over stunnel
by Andy Wettstein 19 Nov '07

19 Nov '07

Hi, I wrote a document about how I am running NFS over stunnel. Using some firewall rules I was able to eliminate most of the complications for using secure NFS. It could probably use more detailed explanations, but the scripts I am using are all there. It still kind of in test phase, but I am currently mounting my home directory using stunnel. I haven't really noticed much of a speed problem in day to day activities. https://w3.physics.uiuc.edu/physwiki/doku.php?id=pcs:unix:nfs_over_stunnel Please send any questions you might have. -- andy wettstein unix administrator department of physics university of illinois at urbana-champaign

2 2

receive error
by Protect Girl 14 Nov '07

14 Nov '07

Hi When run stunnel.exe, I was receive "the procedure entry point SSL_CTX_xet_info_callback could not be located in the dynamic library libssl32.dll" error.

2 1

can't get client address
by Draeath Spamtrap 14 Nov '07

14 Nov '07

Stunnel appears to be working fine, but when started it spams my syslog about 5 times with the following message: "stunnel: warning: can't get client address: Bad file descriptor" There are no other messages from stunnel. I'm not sure where it's coming from... It looks like it is running without command line arguments. My init script has the following snippets that make me think that: > PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin > PREFIX=/usr/local > DAEMON=/usr/local/bin/stunnel > PIDFILE=/var/lib/stunnel/stunnel.pid > > test -f $DAEMON || exit 0 > > case "$1" in > start) > echo -n "Starting universal SSL tunnel: stunnel" > $DAEMON || echo -n " failed" > echo "." > ;; > {TRIMMED REST OF FILE} My stunnel version info: > stunnel 4.21 on i686-pc-linux-gnu with OpenSSL 0.9.8e 23 Feb 2007 > Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv6 Auth:LIBWRAP > > Global options > debug = 5 > pid = /usr/local/var/run/stunnel/stunnel.pid > RNDbytes = 64 > RNDfile = /dev/urandom > RNDoverwrite = yes > Service-level options > cert = /usr/local/etc/stunnel/stunnel.pem > ciphers = ALL:!ADH:+RC4:@STRENGTH > key = /usr/local/etc/stunnel/stunnel.pem > session = 300 seconds > sslVersion = SSLv3 for client, all for server > TIMEOUTbusy = 300 seconds > TIMEOUTclose = 60 seconds > TIMEOUTconnect = 10 seconds > TIMEOUTidle = 43200 seconds > verify = none My stunnel config file: > cert = /usr/local/etc/stunnel/stunnel.pem > key = /usr/local/etc/stunnel/stunnel.pem > sslVersion = SSLv3 > chroot = /var/lib/stunnel/ > setuid = 99 > setgid = 99 > pid = /stunnel.pid > socket = l:TCP_NODELAY=1 > socket = r:TCP_NODELAY=1 > client = yes > [nntps] > accept = 127.0.0.1:119 > connect = secure.news.easynews.com:563 Again, it is all working, and aside from my TCP_NODELAY flags, everything in my conf would be a show-stopper if it was invalid or not working... *of note: I had to set the uid/gid number. for some reason it couldn't resolve the gid/uid on it's own. My /etc/passwd is world-readable (with hashes in shadow) as is standard. I'm not sure I should even be worried about this...

2 2

Reporting bugs in stunnel 4.21
by Michal Trojnara 10 Nov '07

10 Nov '07

Dear Users, Please test the new stunnel 4.21 and report your issues on the Bug Tracking System (http://stunnel.mirt.net/bts.html) or email the information to the stunnel-users mailing list. This is the easiest way to help stunnel working fine on your various systems. I was developing it for quite a long time and I likely failed to fix all the bugs. I'm especially interested in all compilation or runtime issues with the new FIPS and libwrap code. By the time you can find a patch for setuid/setgid+chroot problem here: ftp://stunnel.mirt.net/stunnel/setuid.patch Best regards, Mike

2 2

How is it working?
by fuzzy_4711 07 Nov '07

07 Nov '07

Hello list. After a few tries, my stunnel configuration is working well. I am using it to tunnel my vnc connections to my winXP box. Now I have a question about how the software is working. In the past, when I was using VNC at port 5900 and I did a telnet to that box with port 5900, VNC was answering with something like 003005 which was the VNC protocol version the server was able to communicate. Now because of the tunneling effect, my vnc server still listens at 127.0.0.1:5900 but is expecting ssled connections at xxx.xxx.xxx.xxx:9999. When I do a telnet at xxx.xxx.xxx.xxx at port 9999 my box is answering something like: Connected to xxx.xxx.xxx.xxx Escape character is ... Now if enter something like "test" the telnet window shows me that the connection is closed by foreign host (means: my xp box). Lets assume, someone is trying to hack my computer and doing a port scan. She/he will find out for sure, that my port 9999 is opened. Usually the server listening behind the port is sending something the attacker could use to point to the software running behind the port. In this case, as far as I can see nothing is sent to give a hint that stunnel is waiting there to route my connection attempt to 127.0.0.1:5900. Is it right, that this is the magic - for sure besides encryption and all the algorithms necessary to do the port forwarding - stunnel provides? I mean as long as an attacker doesnt know what is hiding behind the port he/she also doesnt know how to attack or how to get through. Is that conclusion right? Please tell me, if my conclusions are wrong or if I got something wrong. Stefan

3 2

PATCH: Support PostgreSQL SSL
by Marko Kreen 06 Nov '07

06 Nov '07

PostgreSQL protocol has small handshake on connecting before SSL can be initialized. But that means that Stunnel cannot be used by default as it expects the SSL initialization to be the first thing when getting connection. Attached patch adds PostgreSQL protocol support to Stunnel, so that Stunnel can be used to provide SSL when either client or server is not able to do it natively. SSL handshake is described here: http://www.postgresql.org/docs/8.3/static/protocol-flow.html#AEN73013 Patch is tested and works, hopefully it can be included in main Stunnel source. -- marko

1 0

STUNNEL Licensing
by Menon, Sreejith Mohan 06 Nov '07

06 Nov '07

Dear Users, Is there any special licensing required to use STUNNEL ? In case, it is not required from STUNNEL , is there anything to be done on the OPENSSL side ? Thanks and best regards, Sreejith Mohan Menon

1 0

Re: [stunnel-users] almost working
by Tom Allison 05 Nov '07

05 Nov '07

Luke Deller wrote: > Hi Tom, > >> OK, this has been nothing but a bust. > > I've just read this thread, and it looks to me that you have stunnel configured incorrectly for use with inetd. > > Did you see this documentation? > http://www.stunnel.org/faq/stunnel.html#inetd_mode > >> the error keeps saying that port 993 is already in use. > > This is because you have configured stunnel to bind to port 993 using an "accept" option in the configuration file. When using stunnel with inetd, stunnel should not bind to any port; it is inetd which binds to a port. When a client connects to inetd, then inetd will launch stunnel with stunnel's stdin and stdout streams hooked up to the connected socket. > Made some progress. Got past the SSL version. Fixed my firewall to permit IMAPS sessions. confirmed my firewall settings by changing to IMAP and running directly against the imap server. Changed firewall settings from imap to imaps. Keep timing out. Same problem for Mac Mail application (which isn't great) and Debian's Icedove. This is as far as I can get. 2007.11.05 05:43:56 LOG7[27692:47518144360528]: Connection from 65.29.101.30:49841 permitted by libwrap 2007.11.05 05:43:56 LOG5[27692:47518144360528]: inetd connected from 65.29.101.30:49841 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): before/accept initialization 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): SSLv3 read client hello A 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): SSLv3 write server hello A 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): SSLv3 write certificate A 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): SSLv3 write server done A 2007.11.05 05:43:56 LOG7[27692:47518144360528]: SSL state (accept): SSLv3 flush data

1 0

Re: [stunnel-users] Using stunnel for RDP / Proxy / Firewall
by Frank Garber 30 Oct '07

30 Oct '07

I tried using the port you suggested and got the same result. I'm able to verify my firewall is letting the traffic through and that my ISP is not blocking the port by using www.canyouseeme.org . Again, all my settings work when I'm not going through the corporate firewall. Can you send me your whole config file for both your client and server sides? I'm wondering if it has to do with my certificate settings. Thanks, Frank ----- Original Message ---- From: Carter Browne <xxxx> To: garberfc <xxxx> Sent: Monday, October 22, 2007 8:07:11 AM Subject: Re: [stunnel-users] Using stunnel for RDP / Proxy / Firewall I do this all the time. The way I do it is to connect locally to RDP on a non-stardard port. In the RDP dialog box, I have 127.0.0.10:12121, then in stunnel on the local side is: [xxx-rdp] accept = 127.0.0.10:12121 connect = server:12122 client = yes on the remote side is [rdp-incoming] accept = 12122 connect = 3389 client = no. Normally RDP listens for any connection to port 3389, so I found it was easiest to get to to work by moving off that port. Note that you have to open port 12122 in the firewall on the remote side. On the other hand, you can close 3389 on the remote side which takes away an obvious port for hackers. Carter garberfc wrote: > Hi All > > I'm a relative newbie to Stunnel, and am trying to set up a tunnel so I can > Remote Desktop from work to my PC/server at home. > > I'm using versions 4.20 of the Windows binaries. > > I've tested the configuration and it works from home using a laptop that is > going through my firewall > when I enter my domain home (so my firewall is set up correctly). I tried a > variety of common ports and got the same response every time. I had to use > the 127.0.0.2 on the client because Remote Desktop didn't want me connecting > to myself... > > When I try if from work I get a dialog box: > The client could not establish a connection to the remote computer. > The most likely causes for this error are: > 1) Remote connections might not be enabled at the remote computer. > 2)The maximum number of connections was exceeded at the remote computer. > 3) A network error occurred while establishing the connection. > > My config is as follows: > > #Client > ;cert = stunnel.pem > ;key = stunnel.pem > > ; Some performance tunings > socket = l:TCP_NODELAY=1 > socket = r:TCP_NODELAY=1 > > ; Some debugging stuff useful for troubleshooting > debug = 7 > output = stunnel.log > > ; Use it for client mode > client = yes > > ; Service-level configuration > [https-RDT] > accept = 127.0.0.2:3389 > connect = xx.xx.xx.xx:1494 > > > #Server > ; Some performance tunings > socket = l:TCP_NODELAY=1 > socket = r:TCP_NODELAY=1 > > ; Some debugging stuff useful for troubleshooting > debug = 7 > output = stunnel.log > > ; Use it for client mode > client = no > > ; Service-level configuration > [https-RDT] > accept = 1494 > connect = localhost:3389 > > > Is there something I need to do to traverse this proxy? Any help would be > greatly appreciated! > >

3 4

Re: [stunnel-users] almost working
by Tom Allison 30 Oct '07

30 Oct '07

On Oct 29, 2007, at 9:39 PM, Luke Deller wrote: > > Hi Tom, > >> OK, this has been nothing but a bust. > > I've just read this thread, and it looks to me that you have > stunnel configured incorrectly for use with inetd. > > Did you see this documentation? > http://www.stunnel.org/faq/stunnel.html#inetd_mode > >> the error keeps saying that port 993 is already in use. > > This is because you have configured stunnel to bind to port 993 > using an "accept" option in the configuration file. When using > stunnel with inetd, stunnel should not bind to any port; it is > inetd which binds to a port. When a client connects to inetd, then > inetd will launch stunnel with stunnel's stdin and stdout streams > hooked up to the connected socket. Amazing how much progess can be made in a minute. Thank you very much. I did miss that line in the docs. I've moved on to a slightly different error, but it's probably going to be easier for me to sort this one out. I have to go to out, so I'll read up on it and try it when I get back. I'm going to guess I have a ssl version/imap version issue to sort out. I'm trying to connect from a macbook to this server. Thank You!!! 2007.10.30 07:07:59 LOG5[22402:47915096707152]: stunnel 4.18 on x86_64-pc-linux-gnu with OpenSSL 0.9.8c 05 Sep 2006 2007.10.30 07:07:59 LOG5[22402:47915096707152]: Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv6 Auth:LIBWRAP 2007.10.30 07:07:59 LOG7[22402:47915096707152]: inetd started 2007.10.30 07:07:59 LOG7[22402:47915096707152]: FD 0 in non-blocking mode 2007.10.30 07:07:59 LOG7[22402:47915096707152]: FD 1 in non-blocking mode 2007.10.30 07:07:59 LOG7[22402:47915096707152]: TCP_NODELAY option set on local socket 2007.10.30 07:07:59 LOG7[22402:47915096707152]: FD 4 in non-blocking mode 2007.10.30 07:07:59 LOG7[22402:47915096707152]: FD 5 in non-blocking mode 2007.10.30 07:07:59 LOG7[22402:47915096707152]: Connection from 65.29.101.30:53036 permitted by libwrap 2007.10.30 07:07:59 LOG5[22402:47915096707152]: inetd connected from 65.29.101.30:53036 2007.10.30 07:07:59 LOG7[22402:47915096707152]: SSL state (accept): before/accept initialization 2007.10.30 07:07:59 LOG3[22402:47915096707152]: SSL_accept: 1408F10B: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number 2007.10.30 07:07:59 LOG5[22402:47915096707152]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2007.10.30 07:07:59 LOG7[22402:47915096707152]: inetd finished (0 left)

1 0

almost working
by Tom Allison 30 Oct '07

30 Oct '07

I'm trying to tunnel imap but I'm not getting past this: 2007.10.08 05:56:28 LOG5[5355:47656983060560]: stunnel 4.18 on x86_64-pc-linux-gnu with OpenSSL 0.9.8c 05 Sep 2006 2007.10.08 05:56:28 LOG5[5355:47656983060560]: Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv6 Auth:LIBWRAP 2007.10.08 05:56:28 LOG6[5355:47656983060560]: file ulimit = 1024 (can be changed with 'ulimit -n') 2007.10.08 05:56:28 LOG6[5355:47656983060560]: poll() used - no FD_SETSIZE limit for file descriptors 2007.10.08 05:56:28 LOG5[5355:47656983060560]: 500 clients allowed 2007.10.08 05:56:28 LOG7[5355:47656983060560]: FD 4 in non-blocking mode 2007.10.08 05:56:28 LOG7[5355:47656983060560]: FD 5 in non-blocking mode 2007.10.08 05:56:28 LOG7[5355:47656983060560]: FD 6 in non-blocking mode 2007.10.08 05:56:28 LOG7[5355:47656983060560]: SO_REUSEADDR option set on accept socket 2007.10.08 05:56:28 LOG3[5355:47656983060560]: Error binding imaps to 0.0.0.0:993 2007.10.08 05:56:28 LOG3[5355:47656983060560]: bind: Address already in use (98) I can't find where to begin. I set SO_REUSEADDR and it didn't do anything different. How do I test this stuff sanely?

4 8

stunnel 4.21 released
by Michal Trojnara 27 Oct '07

27 Oct '07

Dear Users, The new version is available for download on: ftp://stunnel.mirt.net/stunnel/ Version 4.21, 2007.10.27, urgency: LOW/EXPERIMENTAL: * New features sponsored by Open-Source Software Institute - Initial FIPS 140-2 support (see INSTALL.FIPS for details). Win32 platform is not currently supported. * New features - Experimental fast support for non-MT-safe libwrap is provided with pre-spawned processes. - Stunnel binary moved from /usr/local/sbin to /usr/local/bin in order to meet FHS and LSB requirements. Please delete the /usr/local/sbin/stunnel when upgrading. - Added code to disallow compiling stunnel with pthreads when OpenSSL is compiled without threads support. - Win32 DLLs for OpenSSL 0.9.8g. - Minor manual update. - TODO file updated. * Bugfixes - Dynamic locking callbacks added (needed by some engines to work). - AC_ARG_ENABLE fixed in configure.am to accept yes/no arguments. - On some systems libwrap requires yp_get_default_domain from libnsl, additional checking was added. - Sending a list of trusted CAs for the client to choose the right certificate restored. - Some compatibility issues with NTLM authentication fixed. - Taskbar icon (unless there is a config file parsing error) and "Save As" disabled in the service mode for local Win32 security (it's much like Yeti -- some people claim they have seen it). sha1 hash for stunnel-4.21.tar.gz file: 7785c45167d902aa728b839adee02a8cc056d86a Best regards, Mike

1 0

Re: [stunnel-users] stunnel-users Digest, Vol 39, Issue 16
by Frank Garber 24 Oct '07

24 Oct '07

I tested with my firewall with both PCs at home. I can make it work with the port open and when I close the port it fails. it's only when I try to connect from behind the corporate firewall that it fails. I've tried several other port numbers and always get the same results. Can you send me your entire client and server config files so I can see the settings? Thanks, Frank ----- Original Message ---- From: "stunnel-users-request(a)mirt.net" <stunnel-users-request(a)mirt.net> To: stunnel-users(a)mirt.net Sent: Tuesday, October 23, 2007 6:00:06 AM Subject: stunnel-users Digest, Vol 39, Issue 16 Send stunnel-users mailing list submissions to stunnel-users(a)mirt.net To subscribe or unsubscribe via the World Wide Web, visit http://stunnel.mirt.net/mailman/listinfo/stunnel-users or, via email, send a message with subject or body 'help' to stunnel-users-request(a)mirt.net You can reach the person managing the list at stunnel-users-owner(a)mirt.net When replying, please edit your Subject line so it is more specific than "Re: Contents of stunnel-users digest..." Today's Topics: 1. [RE] Using stunnel for RDP / Proxy / Firewall (Algol Tradent) Hello, I think your problem might be related to your configuration firewall/router. Have you enabled port-forwarding for the connection? >From your configuration files I can see you are using port 1494. Check that you are forwarding that port. Also make sure you configure any firewall software running on the machine you want to connect to, in order to allow connections. Best Regards __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ stunnel-users mailing list stunnel-users(a)mirt.net http://stunnel.mirt.net/mailman/listinfo/stunnel-users

1 0

[RE] Using stunnel for RDP / Proxy / Firewall
by Algol Tradent 22 Oct '07

22 Oct '07

Hello, I think your problem might be related to your configuration firewall/router. Have you enabled port-forwarding for the connection? >From your configuration files I can see you are using port 1494. Check that you are forwarding that port. Also make sure you configure any firewall software running on the machine you want to connect to, in order to allow connections. Best Regards __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Using stunnel for RDP / Proxy / Firewall
by garberfc 20 Oct '07

20 Oct '07

Hi All I'm a relative newbie to Stunnel, and am trying to set up a tunnel so I can Remote Desktop from work to my PC/server at home. I'm using versions 4.20 of the Windows binaries. I've tested the configuration and it works from home using a laptop that is going through my firewall when I enter my domain home (so my firewall is set up correctly). I tried a variety of common ports and got the same response every time. I had to use the 127.0.0.2 on the client because Remote Desktop didn't want me connecting to myself... When I try if from work I get a dialog box: The client could not establish a connection to the remote computer. The most likely causes for this error are: 1) Remote connections might not be enabled at the remote computer. 2)The maximum number of connections was exceeded at the remote computer. 3) A network error occurred while establishing the connection. My config is as follows: #Client ;cert = stunnel.pem ;key = stunnel.pem ; Some performance tunings socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 ; Some debugging stuff useful for troubleshooting debug = 7 output = stunnel.log ; Use it for client mode client = yes ; Service-level configuration [https-RDT] accept = 127.0.0.2:3389 connect = xx.xx.xx.xx:1494 #Server ; Some performance tunings socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 ; Some debugging stuff useful for troubleshooting debug = 7 output = stunnel.log ; Use it for client mode client = no ; Service-level configuration [https-RDT] accept = 1494 connect = localhost:3389 Is there something I need to do to traverse this proxy? Any help would be greatly appreciated! -- View this message in context: http://www.nabble.com/Using-stunnel-for-RDP---Proxy---Firewall-tf4654985.ht… Sent from the Stunnel - Users mailing list archive at Nabble.com.

1 0

scaling stunnel
by Ben Hartshorne 19 Oct '07

19 Oct '07

Hi, I am trying to set up syslog + stunnel in a large environment. I am curious about the experience of members of this mailing list regarding how stunnel + syslog-ng scale. I set up a test environment using stunnel 3.26 (because that's what is in my debian installation)[*]. I configured stunnel to run as a daemon (starting on boot), and syslog passes off messages and receives messages from localhost:514. In the stunnel log, it tells me that there is a limit of 500 clients, and it seems that with stunnel 3.x, it must be recompiled to increase this limit. I found some posts on this list that say that while stunnel 3.x uses select(), stunnel 4.x uses poll(), which is much more efficient. So I figure that if I will have to roll my own package, I may as well upgrade to 4.x at the same time. Agree? If so, which version? It's my understanding that this configuration will create a persistent connection between the client and server, holding it open until such time as syslog needs to send a message across it. How many clients have you experienced being able to connect to the log aggregator? My logs are rather sparse, so I expect I will hit a limit based on processor / filehandle / memory usage before I start overloading the local disk. Eventually, I realize that I will have to build a tree structure with intermediate nodes aggregating logs and passing them on to the central host, but I would like to know where people have hit that limit. I would love to have ~5000 clients connected to each aggregating server. Is this within the realm of experience? Does anybody have tuning suggestions for such high numbers of connections? I saw one person mention on the mailing list that compiling without libwrap allowed him to pass ~2500 connections (though he didn't give a new ceiling). Thanks, -ben [*] I was actually impressed at how easy this was. Aside from having to write my own /etc/init.d/ scripts to start the client and server, I could bring down either end of the stunnel connection, and things would just pick up where they left off when the tunnel was reconnected. Add monit into the picture and you've got a nice resilient secure logging system. Slick! -- Ben Hartshorne email: ben(a)hartshorne.net http://ben.hartshorne.net

2 5

SSL Accelerator card and Stunnel
by domstra＠alice.it 16 Oct '07

16 Oct '07

Hi all, We are using STunnel v.3.x and STunnel v.4.x on different systems (Application Servers and DB Servers, on HP and Sun mainframe hardware). We have noticed that the STunnel load is quite heavy for the CPUs of each Server. So, we are beginning to study and analyze a solution that allows we to use STunnel without generate overhead on the CPUs. A good solution could be using a SSL Accelerator card as "SSL engine", in order to offloading the calls to the card CPU. We have also read the following topic in your mailing-list regarding a solutions similar to ours: List: stunnel-users Subject: SSL Accelerator supporto for Stunnel Can you suggest us a list of "SSL Accelerator card" model (and vendor) to install and configure with STunnel? Anyway, do you suggest us to upgrade the STunnel version to the last stable on each Server? Thanks in advance for the support. Awaiting for your kind feedback and suggestions. Best Regards. Dom *********** Scopri la nuova Alice Mail! <http://registra.rossoalice.alice.it/registra/basic/entratabasic.do?entryPoi…> 1 GB di spazio con antivirus, antispam e fino a 2 GB di allegati. <http://registra.rossoalice.alice.it/registra/basic/entratabasic.do?entryPoi…> Registrati GRATIS <http://registra.rossoalice.alice.it/registra/basic/entratabasic.do?entryPoi…>

4 8

stunnel and pan newsreader configuration
by Kernel Panic 13 Oct '07

13 Oct '07

I am attempting to use stunnel to connect securely to a snntp server using pan 0.132. The stunnel install was successful, but when attempting to connect to the server using pan, I either receive a "connection refused" or "connection reset by peer" in the pan error log. Here is the stunnel.log: 2007.10.13 11:16:43 LOG5[5843:3082667712]: stunnel 4.20 on i686-pc-linux-gnu with OpenSSL 0.9.8e 23 Feb 2007 2007.10.13 11:16:43 LOG5[5843:3082667712]: Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv4 Auth:LIBWRAP 2007.10.13 11:16:43 LOG6[5843:3082667712]: file ulimit = 1024 (can be changed with 'ulimit -n') 2007.10.13 11:16:43 LOG6[5843:3082667712]: poll() used - no FD_SETSIZE limit for file descriptors 2007.10.13 11:16:43 LOG5[5843:3082667712]: 500 clients allowed 2007.10.13 11:16:43 LOG7[5843:3082667712]: FD 4 in non-blocking mode 2007.10.13 11:16:43 LOG7[5843:3082667712]: FD 5 in non-blocking mode 2007.10.13 11:16:43 LOG7[5843:3082667712]: FD 6 in non-blocking mode 2007.10.13 11:16:43 LOG7[5843:3082667712]: SO_REUSEADDR option set on accept socket 2007.10.13 11:16:43 LOG7[5843:3082667712]: NNTP bound to 127.0.0.1:23 2007.10.13 11:16:43 LOG7[5843:3082667712]: Created pid file /home/kpanic/download/stunnel//var/run/stunnel/stunnel.pid 2007.10.13 11:17:00 LOG7[5843:3082667712]: NNTP accepted FD=7 from 127.0.0.1:1085 2007.10.13 11:17:00 LOG7[5843:3085958032]: NNTP started 2007.10.13 11:17:00 LOG7[5843:3085958032]: FD 7 in non-blocking mode 2007.10.13 11:17:00 LOG7[5843:3085958032]: FD 8 in non-blocking mode 2007.10.13 11:17:00 LOG7[5843:3085958032]: FD 9 in non-blocking mode 2007.10.13 11:17:00 LOG7[5843:3082667712]: Cleaning up the signal pipe 2007.10.13 11:17:00 LOG6[5843:3082667712]: Child process 5855 finished with code 0 2007.10.13 11:17:00 LOG7[5843:3085958032]: Connection from 127.0.0.1:1085 permitted by libwrap 2007.10.13 11:17:00 LOG5[5843:3085958032]: NNTP accepted connection from 127.0.0.1:1085 2007.10.13 11:17:00 LOG7[5843:3085958032]: FD 8 in non-blocking mode 2007.10.13 11:17:00 LOG3[5843:3085958032]: bind transparent: Address already in use (98) 2007.10.13 11:17:00 LOG5[5843:3085958032]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2007.10.13 11:17:00 LOG7[5843:3085958032]: NNTP finished (0 left) 2007.10.13 11:17:00 LOG7[5843:3082667712]: NNTP accepted FD=7 from 127.0.0.1:1086 2007.10.13 11:17:00 LOG7[5843:3085958032]: NNTP started 2007.10.13 11:17:00 LOG7[5843:3085958032]: FD 7 in non-blocking mode 2007.10.13 11:17:00 LOG7[5843:3085958032]: FD 8 in non-blocking mode 2007.10.13 11:17:00 LOG7[5843:3085958032]: FD 9 in non-blocking mode 2007.10.13 11:17:00 LOG7[5843:3082667712]: Cleaning up the signal pipe 2007.10.13 11:17:00 LOG7[5843:3085958032]: Connection from 127.0.0.1:1086 permitted by libwrap 2007.10.13 11:17:00 LOG5[5843:3085958032]: NNTP accepted connection from 127.0.0.1:1086 2007.10.13 11:17:00 LOG6[5843:3082667712]: Child process 5857 finished with code 0 2007.10.13 11:17:00 LOG7[5843:3085958032]: FD 8 in non-blocking mode 2007.10.13 11:17:00 LOG3[5843:3085958032]: bind transparent: Address already in use (98) 2007.10.13 11:17:00 LOG5[5843:3085958032]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2007.10.13 11:17:00 LOG7[5843:3085958032]: NNTP finished (0 left) 2007.10.13 11:17:05 LOG7[5843:3082667712]: NNTP accepted FD=7 from 127.0.0.1:1087 2007.10.13 11:17:05 LOG7[5843:3085958032]: NNTP started 2007.10.13 11:17:05 LOG7[5843:3085958032]: FD 7 in non-blocking mode 2007.10.13 11:17:05 LOG7[5843:3085958032]: FD 8 in non-blocking mode 2007.10.13 11:17:05 LOG7[5843:3085958032]: FD 9 in non-blocking mode 2007.10.13 11:17:05 LOG7[5843:3082667712]: Cleaning up the signal pipe 2007.10.13 11:17:05 LOG7[5843:3085958032]: Connection from 127.0.0.1:1087 permitted by libwrap 2007.10.13 11:17:05 LOG5[5843:3085958032]: NNTP accepted connection from 127.0.0.1:1087 2007.10.13 11:17:05 LOG6[5843:3082667712]: Child process 5860 finished with code 0 2007.10.13 11:17:05 LOG7[5843:3085958032]: FD 8 in non-blocking mode 2007.10.13 11:17:05 LOG3[5843:3085958032]: bind transparent: Address already in use (98) 2007.10.13 11:17:05 LOG5[5843:3085958032]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2007.10.13 11:17:05 LOG7[5843:3085958032]: NNTP finished (0 left) 2007.10.13 11:17:10 LOG7[5843:3082667712]: NNTP accepted FD=7 from 127.0.0.1:1088 2007.10.13 11:17:10 LOG7[5843:3085958032]: NNTP started 2007.10.13 11:17:10 LOG7[5843:3085958032]: FD 7 in non-blocking mode 2007.10.13 11:17:10 LOG7[5843:3085958032]: FD 8 in non-blocking mode 2007.10.13 11:17:10 LOG7[5843:3085958032]: FD 9 in non-blocking mode 2007.10.13 11:17:10 LOG7[5843:3082667712]: Cleaning up the signal pipe 2007.10.13 11:17:10 LOG7[5843:3085958032]: Connection from 127.0.0.1:1088 permitted by libwrap 2007.10.13 11:17:10 LOG5[5843:3085958032]: NNTP accepted connection from 127.0.0.1:1088 2007.10.13 11:17:10 LOG6[5843:3082667712]: Child process 5863 finished with code 0 2007.10.13 11:17:10 LOG7[5843:3085958032]: FD 8 in non-blocking mode 2007.10.13 11:17:10 LOG3[5843:3085958032]: bind transparent: Address already in use (98) 2007.10.13 11:17:10 LOG5[5843:3085958032]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2007.10.13 11:17:10 LOG7[5843:3085958032]: NNTP finished (0 left) 2007.10.13 11:17:15 LOG7[5843:3082667712]: NNTP accepted FD=7 from 127.0.0.1:1089 2007.10.13 11:17:15 LOG7[5843:3085958032]: NNTP started 2007.10.13 11:17:15 LOG7[5843:3085958032]: FD 7 in non-blocking mode 2007.10.13 11:17:15 LOG7[5843:3085958032]: FD 8 in non-blocking mode 2007.10.13 11:17:15 LOG7[5843:3085958032]: FD 9 in non-blocking mode 2007.10.13 11:17:15 LOG7[5843:3082667712]: Cleaning up the signal pipe 2007.10.13 11:17:15 LOG7[5843:3085958032]: Connection from 127.0.0.1:1089 permitted by libwrap 2007.10.13 11:17:15 LOG5[5843:3085958032]: NNTP accepted connection from 127.0.0.1:1089 2007.10.13 11:17:15 LOG7[5843:3085958032]: FD 8 in non-blocking mode 2007.10.13 11:17:15 LOG6[5843:3082667712]: Child process 5866 finished with code 0 2007.10.13 11:17:15 LOG3[5843:3085958032]: bind transparent: Address already in use (98) 2007.10.13 11:17:15 LOG5[5843:3085958032]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2007.10.13 11:17:15 LOG7[5843:3085958032]: NNTP finished (0 left) Here is the snnt.conf file: # Debug debug = 7 output = /home/kpanic/download/stunnel/stunnel.log # Use it for client mode client = yes foreground = yes [NNTP] protocol = nntp protocolusername = username protocolpassword = password transparent = yes accept = localhost:23 connect = secure.server.com:563 Here is the pan error log: Sat Oct 13 10:46:50 2007 - Error reading from localhost: Connection reset by peer Sat Oct 13 10:46:55 2007 - Error reading from localhost: Connection reset by peer Sat Oct 13 10:47:00 2007 - Error reading from localhost: Connection reset by peer Sat Oct 13 10:47:05 2007 - Error reading from localhost: Connection reset by peer Sat Oct 13 10:47:10 2007 - Error reading from localhost: Connection reset by peer Changing the server setup in pan to look at 127.0.0.1 Sat Oct 13 10:45:40 2007 - Pan 0.132 started Sat Oct 13 10:45:40 2007 - Loaded data backend in 0.0 seconds Sat Oct 13 10:45:47 2007 - Error reading from 127.0.0.1: Connection reset by peer Sat Oct 13 10:45:50 2007 - Error reading from 127.0.0.1: Connection reset by peer Sat Oct 13 10:45:55 2007 - Error reading from 127.0.0.1: Connection reset by peer Sat Oct 13 10:46:00 2007 - Error reading from 127.0.0.1: Connection reset by peer Pan configuration: Address: localhost Port: 23 Username: username Password: password uname -r 2.6.22.9-0.4-bigsmp suse 10.3 Any assistance would be greatly appreciated. Thanks - Tim --------------------------------- Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games.

1 0

configuration help
by Tom Allison 12 Oct '07

12 Oct '07

I posted an email a couple days ago and noticed that there isn't any traffic on this mailing list. Is this active/current?

1 0

Stunnel Return Codes - How do I see them in a batch file?
by Robert Lambrecht 10 Oct '07

10 Oct '07

I have Stunnel working successfully in a batch file. I would like to write the error codes in case there is an issue. How do you do this? In Windows, I could do something like: "C:\Program Files\stunnel\stunnel.exe" -start -quiet stunnel.conf goto %errorlevel% :0 :: Normal Return - Complete Batch Process goto :EOF :1 :: Errors - Log them Would this work or how do I get the stunnel return codes? Bob

1 0

Wildcard usage
by Knight Tiger 08 Oct '07

08 Oct '07

Hi, I am new to STUNNEL and I find it very useful for what I am doing right now. I would like to know if STUNNEL does support the functionality I require. I shall describe the situation below. I run a SIP messaging server (SIP is a VoIP protocol used to establish voice calls over the Internet). STUNNEL is running on the same machine as the SIP server. The SIP server listens on a specific port say 8000 so I have in the config file [sip-new] accept = 10000 connect = localhost:8000 and it works beautifully as the client sends the message through a SSL connection to port 10000 on the machine. So far so good. Now I need the server to send a message to the client. SIP server -----> STUNNEL ------> client . Here STUNNEL acts as a SSL client and the client acts as the SSL server. (Both the client and STUNNEL support this functionality), so in the config file I have [sip-client] accept = 11000 connect = ?:8000 How can I code in the client IP address (I know the port number where the client's SSL server is listening on) when I dont know the client IP address before hand ? (The client is typically assigned IP address by a DHCP server) and I will have more than one client which would be acting as a server. The SIP server will know the client's IP address when the client sends a request. (SIP server can determine the IP address from the SIP message and not from the IP header) . So now the message from the SIP server will have the client's IP address but STUNNEL does not have a config for that IP address (since it is dynamic and I need to support many clients) and hence STUNNEL will not create a SSL tunnel to the client. Can I have wildcard for the IP address ? something like [sip-client] accept = 11000 connect = *:8000 and have STUNNEL get the destination IP from the message ? I thank you all in advance, Warm Regards Knight

1 0

Stunnel on the same machine
by subrata＠indiatimes.com 05 Oct '07

05 Oct '07

Hi I want to configure to encrypt mysql both client and server on the same machine. Ie the /usr/local/mysql/bin/mysql -u root -p on the same machine where my mysql daemon is located. How to achieve this. regards Subrata -- My life has changed. What about yours? Log on to the new Indiatimes Mail and Live out of the Inbox!

3 3