stunnel-users June 2006

stunnel-users@stunnel.org

16 participants
33 discussions

Modifying STunnel to use OpenSSL FIPS
by David Gillingham 13 Jun '06

13 Jun '06

As part of an internal project at work, I'm investigating a Windows tunneling solution using STunnel. As a requirement of my work, I am to modify STunnel to use OpenSSL's FIPS APIs. And, with only a couple of speedbumps, I was able to achieve this. However I'd like to make my code a little more robust--to provide some notification to the user if OpenSSL's FIPS mode is active or not. To this point I've not been able to figure out a way to do this. In my copy of the STunnel source, I've modified the routine ssl_init() in ssl.c to make a call to FIPS_mode_set(1) (as demonstrated on page 33 of http://www.openssl.org/docs/fips/UserGuide-1.0.pdf). Below is a copy of my current copy of ssl_init(): void ssl_init(void) { /* to keep CLI structure for verify callback */ #if defined(OPENSSL_FIPS) && defined(USE_FIPS) if (!FIPS_mode_set(1)) { s_log(LOG_CRIT, "Could not set FIPS mdoe!"); } else { s_log(LOG_INFO, "In FIPS mode."); } #endif /* rest of ssl_init() from original source */ } As I've found out, the s_log calls do nothing because the STunnel window has not been displayed yet. Ideally, in the case where the FIPS_mode_set() call fails, I'd like to invoke an error handler to cause the STunnel service to fail to start. But trying to make a call to something like sslerror() caused a program crash. Any ideas on how to make these changes?

2 3

RE: [stunnel-users] socket closed after SSL_write
by Srilalitha Muralidhara(HCL Capital Market Services) 13 Jun '06

13 Jun '06

Thanks Michal. How do I disable the socket from sending TCP RST and instead make it send TCP FIN? It might be a very basic question. Sorry about that. Thanks Sri Srilalitha Muralidhara Rates IT Report Server HCL Capital Market Services ( 91.80.4190.6689 + 33/1,The Senate, Ulsoor Road, Bangalore. India. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. -----Original Message----- From: stunnel-users-bounces(a)mirt.net [mailto:stunnel-users-bounces@mirt.net] On Behalf Of Michal Trojnara Sent: Monday, June 12, 2006 11:08 PM To: stunnel-users(a)mirt.net Subject: Re: [stunnel-users] socket closed after SSL_write On Monday 12 June 2006 12:01, Srilalitha Muralidhara wrote: > 2006.06.12 10:47:45 LOG7[19699:28]: SSL alert (write): warning: close > notify Clean SSL shutdown alert was received. > 2006.06.12 10:47:50 LOG3[19699:28]: SSL_read: Connection reset by peer > (131) ... and then TCP RST! Strange. It looks like your application has set SO_LINGER option on its socket, so it sends TCP RST instead of TCP FIN packet. Best regards, Mike Disclaimer: *********** The contents of this E-mail (including the contents of the enclosure(s) or attachment(s) if any) are privileged and confidential material of HCL Capital Market Services and should not be disclosed to, used by or copied in any manner by anyone other than the intended addressee(s). In case you are not the desired addressee, you should delete this message and/or re-direct it to the sender. The views expressed in this E-mail message (including the enclosure(s) or attachment(s) if any) are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of HCL Capital Market Services. This e-mail message including attachment/(s), if any, is believed to be free of any virus. However, it is the responsibility of the recipient to ensure that it is virus free and HCL Capital Market Services is not responsible for any loss or damage arising in any way from its use.

2 1

CRLPath not working
by Nagasundaram, Sekhar 12 Jun '06

12 Jun '06

All: We download crls everyday from a CRL server using LDAP and a cronjob. These CRLs are stored in the CRLpath directory along with its hash. It appears that the stunnel is not refreshing its cache, and it still shows "Found CRL is expired - revoking all certificates until you get updated CRL" when we try to connect to it even though there is a New and valid CRL in the CRLPath folder. Is there a special option In Stunnel configuration for it to recognize/cache/add the new hash file All help is appreciated. Thanks Sekhar

2 1

Re: [stunnel-users] Comparing with BarracudaDrive and Proxytunnel
by Michal Trojnara 12 Jun '06

12 Jun '06

On 2006-06-11, at 21:39, http s wrote: > I am curious if anyone has made a comparison of Stunnel with the > BarracudaDrive HTTPS tunnel and/or Proxytunnel? > > http://barracudaserver.com/examples/BarracudaDrive/HttpsTunnel/ > index.html 1. BarracudaDrive is *not* a free software (even though its home page claims so). See http://www.gnu.org/philosophy/free-sw.html for details. 2. It only works on Windows, Linux, QNX and Mac OS X. Compare it to the list on http://stunnel.mirt.net/. 3. BarracudaDrive is designed to be used for file transfer, while stunnel is a universal tool for encrypting TCP streams. As the result stunnel is much more flexible, but it won't perform any file transfer by itself. > http://proxytunnel.sourceforge.net 1. It's not really an encryption tool, but rather an extension for OpenSSH client. It has some optional basic SSL code (as for version 1.6.0), but it's currently broken. The code incorrectly assumes that SSL_read() only needs to read from a file descriptor and SSL_write() only needs to wrote to a file descriptor. 2. Proxytunnel supports NTLM authentication that is not currently supported by stunnel. 3. It looks like an interesting addition to stunnel on a Unix platform. The client configuration should be something like: [Proxytunnel] client = yes accept = 12345 exec = /path/to/proxytunnel execargs = proxytunnel -p proxy:8080 -u user -s pass -d mybox.athome.nl:443 4. Optional use of stunnel is recommended in README file of Proxytunnel 1.6.0. 8-) Best regards, Mike

1 0

socket closed after SSL_write
by Srilalitha Muralidhara(HCL Capital Market Services) 12 Jun '06

12 Jun '06

Hi, I work on a client-server application that needs to be supported on both UNIX and windows platforms. Currently, we keep one socket open for all communication from client to server (during which many read-write operations take place) For user authentication and security purposes, we are planning to implement SSL-Stunnel. I have developed a small ssl client (based on sclient.c example) which connects to the Stunnel Server. Upon the first SSL_write, SSL is closing the underlying socket. Hence the contents written by subsequent SSL_write operations are not visible in the server log. I saw lot of posts on the same problem. But couldn't find the solution. Any help is greatly appreciated. Please note that: 1. Due platform independency issues, I use RWSocket (a Roguewave library class) instead of the BSD socket in conjunction with SSL. A potion of stunnel server log 2006.06.12 10:47:43 LOG7[19699:28]: FD 1 in non-blocking mode 2006.06.12 10:47:43 LOG7[19699:28]: rssvr connecting 127.0.0.1:28091 2006.06.12 10:47:43 LOG7[19699:28]: Remote FD=1 initialized 2006.06.12 10:47:43 LOG7[19699:28]: TCP_NODELAY option set on remote socket 2006.06.12 10:47:45 LOG7[19699:28]: Socket closed on read 2006.06.12 10:47:45 LOG7[19699:28]: SSL write shutdown 2006.06.12 10:47:45 LOG7[19699:28]: SSL alert (write): warning: close notify 2006.06.12 10:47:45 LOG7[19699:28]: SSL_shutdown retrying 2006.06.12 10:47:45 LOG7[19699:28]: SSL doesn't need to read or write 2006.06.12 10:47:50 LOG3[19699:28]: SSL_read: Connection reset by peer (131) 2006.06.12 10:47:50 LOG5[19699:28]: Connection reset: 0 bytes sent to SSL, 26 bytes sent to socket 2006.06.12 10:47:50 LOG7[19699:28]: linger (remote): Invalid argument (22) 2006.06.12 10:47:50 LOG7[19699:28]: linger (local): Invalid argument (22) 2006.06.12 10:47:50 LOG7[19699:28]: rssvr finished (0 left) Thanks Sri Srilalitha Muralidhara This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Disclaimer: *********** The contents of this E-mail (including the contents of the enclosure(s) or attachment(s) if any) are privileged and confidential material of HCL Capital Market Services and should not be disclosed to, used by or copied in any manner by anyone other than the intended addressee(s). In case you are not the desired addressee, you should delete this message and/or re-direct it to the sender. The views expressed in this E-mail message (including the enclosure(s) or attachment(s) if any) are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of HCL Capital Market Services. This e-mail message including attachment/(s), if any, is believed to be free of any virus. However, it is the responsibility of the recipient to ensure that it is virus free and HCL Capital Market Services is not responsible for any loss or damage arising in any way from its use.

2 1

Reposting...RE: stunnel-users Digest, Vol 23, Issue 2
by Nagasundaram, Sekhar 09 Jun '06

09 Jun '06

Any one... Is there a way to have Stunnel not stop accepting new connections after CRL expiry? See my questions below.. Any help is appreciated... Much thanks Sekhar ---------------------------------------------------------------------- Message: 1 Date: Tue, 6 Jun 2006 15:41:08 -0700 From: "Nagasundaram, Sekhar" <snagasun(a)visa.com> Subject: [stunnel-users] Processing during CRL expiry and refresh To: <stunnel-users(a)mirt.net> Message-ID: <F64762DF94A15C4EA22D250B28D98BE610093C(a)sw720ex064.visa.com> Content-Type: text/plain; charset="US-ASCII" All: I have 2 questions: 1. Is there a way to have Stunnel continue processing and accepting connections after the CRL expiry? Currently it gives a "revoking all certificates" error and stops accepting new connections. 2. Is there a configurable parameter through which we can have the CRL list refresh itself such that 1 above does not happen? Much Thanks in advance.. Sekhar ------------------------------ _______________________________________________ stunnel-users mailing list stunnel-users(a)mirt.net http://stunnel.mirt.net/mailman/listinfo/stunnel-users End of stunnel-users Digest, Vol 23, Issue 2 ********************************************

1 0

syslog-ng over stunnel does not work for me
by Christoph Pleger 08 Jun '06

08 Jun '06

Hello, I set up a server and a client machine to test the combination of stunnel and syslog-ng. I followed the instructions in the example at http://www.stunnel.org/examples/syslog-ng.html, but the log messages are not sent correcly. The log on the server says: ****: syslog started ****: syslog connected from ###.###.###.###:51646 ****: SSL state (accept): before/accept initialization ****: SSL_accept: 140B544E: error: 140B544E: SSL routines:SSL_GET_NEW_SESSION:ssl session id callback failed ****: syslog finished (-1 left) The log on the client says: ****: syslog started ****: syslog connected from 127.0.0.1:3524 ****: FD 8 in non-blocking mode ****: syslog connecting ###.###.###.###:514 ****: connect_wait: waiting 10 seconds ****: connect_wait: connected ****: Remote FD=8 initialized ****: SSL state (connect): before/accept initialization ****: SSL state (connect): SSLv3 write client hello A ****: SSL_connect: Peer suddenly disconnected ****: syslog finished (0 left) Please help. Regards Christoph

1 1

Connection Reset by Peer
by Srilalitha Muralidhara(HCL Capital Market Services) 08 Jun '06

08 Jun '06

Hi, My stunnel server is unable to send data correctly to my application running the same machine. This happens when the client is run from windows platform. When client is run from UNIX everything works fine. The Stunnel Server log file says: 2006.06.05 11:54:54 LOG7[23141:8]: rssvr connecting 127.0.0.1:28091 2006.06.05 11:54:54 LOG7[23141:8]: Remote FD=1 initialized 2006.06.05 11:54:54 LOG7[23141:8]: TCP_NODELAY option set on remote socket 2006.06.05 11:54:54 LOG3[23141:8]: SSL_read: Connection reset by peer (131) 2006.06.05 11:54:54 LOG5[23141:8]: Connection reset: 0 bytes sent to SSL, 13 bytes sent to socket 2006.06.05 11:54:54 LOG5[23141:8]: linger (local): Invalid argument (22) 2006.06.05 11:54:54 LOG7[23141:8]: rssvr finished (0 left) ------------------------------------------------------------------------ -------------------------------------------------------------------- Does anybody know the cause of the problem? And hopefully the solution? Thanks Sri Disclaimer: *********** The contents of this E-mail (including the contents of the enclosure(s) or attachment(s) if any) are privileged and confidential material of HCL Capital Market Services and should not be disclosed to, used by or copied in any manner by anyone other than the intended addressee(s). In case you are not the desired addressee, you should delete this message and/or re-direct it to the sender. The views expressed in this E-mail message (including the enclosure(s) or attachment(s) if any) are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of HCL Capital Market Services. This e-mail message including attachment/(s), if any, is believed to be free of any virus. However, it is the responsibility of the recipient to ensure that it is virus free and HCL Capital Market Services is not responsible for any loss or damage arising in any way from its use.

1 0

decryption failed or bad record mac
by Trent Townsend 07 Jun '06

07 Jun '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've emailed about this once already, but am just giving a *little* more info. It seems similar problems with SSL proliferate the web. The problem is below (message from the client and server posted). I thought it may be a bug reported with SSL and zlib (which a fix isn't due out until the next version of OpenSSL). However, I can successfully start up a openssl s_server and talk to it with a s_client, so I think that eliminates OpenSSL. Has anyone seen this before (I'm sure this is the case) and figured it out? Client: SSL_connect: 140943FC: error:140943FC:SSL routines:SSL3_READ_BYTES:sslv3 alert bad record mac Server: SSL_accept: 1408F455: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac I'm using stunnel 4.11 (tried 4.15 also) and Openssl 0.9.8a. Thanks. -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.0.6 (Build 6060) iQA/AwUBRIcbw40HAxBKv2yIEQI5XQCg2ylvhIBlZ57euv9/wu8fM5vI40cAoKKk L2bMgFZDc23T6ED6CGJJn8oy =+PA6 -----END PGP SIGNATURE-----

1 0

RE: [stunnel-users] stunnel error
by Nadav, Erez 07 Jun '06

07 Jun '06

Hi, It seems that the problem occur when the client write large buffers (30-40Kbytes) on each write. Any idea how to solve it Thanks Erez ________________________________ From: stunnel-users-bounces(a)mirt.net [mailto:stunnel-users-bounces@mirt.net] On Behalf Of Nadav, Erez Sent: Wednesday, June 07, 2006 6:00 PM To: stunnel-users(a)mirt.net Subject: [stunnel-users] stunnel error Hi, I use stunnel 4.14 and face this error when performing buffer writes from client to remote side SSL_write: 140D5042: error:140D5042:SSL routines:SSL3_CTRL:called a function you should not call Does anybody know how can I overcome this ??? Thanks Erez ________________________________________________________________________ __________________ This electronic message contains information from Verint Systems, which may be privileged and confidential. The information is intended to be for the use of the individual(s)or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by replying to this email (1). __________________________________________________________________________________________ This electronic message contains information from Verint Systems, which may be privileged and confidential. The information is intended to be for the use of the individual(s)or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by replying to this email (1).

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

stunnel-users June 2006