Ok, I tried this out and I have run into a little problem....
I have 2 computers, say nodeA and nodeB.
On nodeB, I have an SSL server running using the "openssl s_server ... " listening on port 14001.
On nodeA, I have stunnel running listening (accepting) on port 8050 and connection to nodeB port 14001. Everything seems to work fine when transferring small amounts of data. I can use telnet and everything I send into port 8050 comes out from my openssl server on nodeB.
Now the problem, I created a test stub that connects to port 8050 and writes large amounts of data. My stub sends 7000 bytes worth of data X number of times back to back. It looks like when X gets to about 15, I start seeing problems...I think it is stunnel that stops reading the data on port 8050. When I do a netstat, it looks like there are a bunch of bytes waiting on the receive queue. Any ideas what is happening here?
The version of stunnel I'm running is (stunnel -version):
"stunnel 4.05 on ia64-redhat-linux-gnu PTHREAD-LIBWRAP with openssl 0.9.7a Feb 19 2003"
Thanks for you help.
Jeff
-----Brian Hatch <bri@stunnel.org> wrote: -----
To: Jeffrey Buck <Jeffrey.Buck@raytheon.com>
From: Brian Hatch <bri@stunnel.org>
Date: 06/02/2008 01:38PM
cc: stunnel-users@mirt.net
Subject: Re: [stunnel-users] stunnel compatibility question
At almost 2008-05-30 14:43 -0400, Jeffrey Buck asserted:
> This should make my life easier...I have to interface with another system that
> implemented it's SSL ports using JAVA (I think I originally stated C++, but I
> was wrong). I'm assuming I shouldn't have any problem with JAVA implemented
> SSL either right???
You shouldn't have any problem with standards-compliant SSL
servers or clients.
Whether the particular port you're working with is compliant or not
I can't say without seeing it. Hopefully it's just using OpenSSL
under the hood.
--
Brian Hatch "I've built up a tolerance
Systems and to conscious thought."
Security Engineer -Jon McCoy
http://www.ifokr.org/bri/
Every message PGP signed