stunnel-3.22-5.7.3 and later die silently in when invoked in daemon mode (with the '-d' option). run the following: stunnel -D 7 -d 23 -o stunnell.log -l /usr/sbin/in.telnetd stunnel -D 7 -c -d 446 -o stunnelr.log -r localhost:23 no stunnel processes will be seen in the output of `ps` afterward, and no errors are sent to stdout/stderr. `telnet localhost 446 will return "Connection refused", I expect to a login prompt (and do on other arch-release combinations). here's the logs generateed from the above stunnel commands: # cat stunnell.log 2003.10.10 14:00:10 LOG5[2203:1024]: Using 'in.telnetd' as tcpwrapper service name 2003.10.10 14:00:10 LOG7[2203:1024]: RAND_status claims sufficient entropy for the PRNG 2003.10.10 14:00:10 LOG6[2203:1024]: PRNG seeded successfully 2003.10.10 14:00:10 LOG7[2203:1024]: Certificate: /usr/share/ssl/certs/stunnel.pem 2003.10.10 14:00:10 LOG5[2203:1024]: stunnel 3.22 on ia64-redhat-linux-gnu PTHREAD+LIBWRAP with OpenSSL 0.9.6b [engine] 9 Jul 2001 2003.10.10 14:00:10 LOG3[2204:1024]: Argument to -P (/) is not valid a directory name # cat stunnelr.log 2003.10.10 14:00:21 LOG5[2213:1024]: Using 'localhost.23' as tcpwrapper service name 2003.10.10 14:00:21 LOG7[2213:1024]: RAND_status claims sufficient entropy for the PRNG 2003.10.10 14:00:21 LOG6[2213:1024]: PRNG seeded successfully 2003.10.10 14:00:21 LOG5[2213:1024]: stunnel 3.22 on ia64-redhat-linux-gnu PTHREAD+LIBWRAP with OpenSSL 0.9.6b [engine] 9 Jul 2001 2003.10.10 14:00:21 LOG3[2214:1024]: Argument to -P (/) is not valid a directory name
"Argument to -P (/) is not valid a directory name" is a fatal error. Do you get the same error from 3.26?
seems that it may be fixed in stunnel-3.26-1.7.3.i386.rpm ... still checking.
I note that glibc in 7.2-ia64 had recently had fixes for strncpy applied. Please check if updating glibc (to any more recent version, such as the candidate glibc for RHL 7.3) fixes this problem. I suspect it will, and that would indicate that there were still some fixes needed after 2.2.4-32.
upgrading the system to glibc-2.2.5-43 fixes the problem.
fixed (also verified on 2.1AS). closing bug as fixed in errata.