Hi,
I work for a company which has a custom embedded Linux platform, and have
been working with stunnel for some time but have never seen this problem. I
have seen it with stunnel 4.04 and 4.07, which is compiled on a Redhat
7.2ish platform, but newer SSL libraries. (below my sig is the stunnel
info).
Basically I use a config file, but when debug= and output= is commented out,
stunnel seems to cause a problem which resets the embedded unit. If I
uncomment them both and use output=/var/log/stunnel.log ( or /dev/null )
everything works fine. Not sure where to look for the problem that is
causing this since I can't even get a core dump. I looged in s_log() but
nothing stuck out as being wrong.
Thanks for any help you can lend,
-Brian
[root@JBMgateway-v63 /]# stunnel -version
stunnel 4.07 on i486-pc-linux-gnu PTHREAD+POLL+IPv4+LIBWRAP with OpenSSL
0.9.7d 17 Mar 2004
Global options
cert = /etc/stunnel/stunnel.pem
ciphers = ALL:!ADH:+RC4:@STRENGTH
debug = 5
key = /etc/stunnel/stunnel.pem
pid = /var/run/stunnel.pid
RNDbytes = 64
RNDfile = /dev/urandom
RNDoverwrite = yes
session = 300 seconds
verify = none
Service-level options
TIMEOUTbusy = 300 seconds
TIMEOUTclose = 60 seconds
TIMEOUTconnect = 10 seconds
TIMEOUTidle = 43200 seconds
[root@JBMgateway-v63 /]# uname -a
Linux JBMgateway-v63 2.4.20 #1729 Wed Jan 26 17:38:15 CST 2005 i486 unknown
[root@JBMgateway-v63 /]# ls -al /lib/libssl.so.*
-rwxr-xr-x 1 root root 210452 Jan 26 18:47 /lib/libssl.so.0.9.7
lrwxrwxrwx 1 root root 20 Jan 26 18:47 /lib/libssl.so.2 ->
/lib/libssl.so.0.9.7
[root@JBMgateway-v63 /]# cat /etc/stunnel/stunnel.conf
# Some debugging stuff
debug = 6
output = /var/log/stunnel.log
#output = /dev/null
foreground = yes
# Use it for client mode
client = yes
[SampleGroup]
accept = 443
connect = x.x.x.x:6660