- stunnel-users - stunnel.org

RE: stunnel on Solaris 2.6 or 7?
by Garg, Jai V (Jai) 08 Oct '04

08 Oct '04

I have more informaton on the problem. It is giving the following error when doing pthread_create() in create_client() open(/dev/zero): No such file or directory libthread panic: alloc_chunk (PID: 8605 LWP 1) stacktrace: ef3c9938 ef3c83e8 ef3c8184 ef3cebf0 ef3cbdf8 ef3cfe80 1ad24 1ba28 1bbb8 13e68 0 > -----Original Message----- > From: Garg, Jai V (Jai) > Sent: Friday, October 08, 2004 3:42 PM > To: stunnel-users(a)mirt.net > Subject: stunnel on Solaris 2.6 or 7? > > Hello, > Has anyone successfully used stunnel on Solaris 2.6 or Solaris 7? I would appreciate if you can provide the binary. > I am using gcc (tried both 3.3.2 and 3.4.2) on 2.6. It compiles, but it seems to hang somewhere after accepting a connection. Here's the log: > > 2004.10.08 13:05:20 LOG5[21833:1]: stunnel 4.05 on sparc-sun-solaris2.6 PTHREAD with OpenSSL 0.9.7d 17 Mar 20 > 04 > 2004.10.08 13:05:20 LOG7[21833:1]: RAND_status claims sufficient entropy for the PRNG > 2004.10.08 13:05:20 LOG6[21833:1]: PRNG seeded successfully > 2004.10.08 13:05:20 LOG5[21833:1]: FD_SETSIZE=1024, file ulimit=64 -> 29 clients allowed > 2004.10.08 13:05:20 LOG7[21833:1]: FD 4 in non-blocking mode > 2004.10.08 13:05:20 LOG7[21833:1]: SO_REUSEADDR option set on accept socket > 2004.10.08 13:05:20 LOG7[21833:1]: SeS_SOCKS_NJ bound to 0.0.0.0:1373 > 2004.10.08 13:05:20 LOG7[21833:1]: FD 5 in non-blocking mode > 2004.10.08 13:05:20 LOG7[21833:1]: FD 6 in non-blocking mode > 2004.10.08 13:05:20 LOG7[21834:1]: Created pid file /stunnel-client.pid > 2004.10.08 13:05:25 LOG7[21834:1]: SeS_SOCKS_NJ accepted FD=0 from 155.184.22.17:62844 > 2004.10.08 13:05:25 LOG7[21834:1]: FD 0 in non-blocking mode > > I appreciate all help with this. > > Jai

1 0

stunnel on Solaris 2.6 or 7?
by Garg, Jai V (Jai) 08 Oct '04

08 Oct '04

Hello, Has anyone successfully used stunnel on Solaris 2.6 or Solaris 7? I would appreciate if you can provide the binary. I am using gcc (tried both 3.3.2 and 3.4.2) on 2.6. It compiles, but it seems to hang somewhere after accepting a connection. Here's the log: 2004.10.08 13:05:20 LOG5[21833:1]: stunnel 4.05 on sparc-sun-solaris2.6 PTHREAD with OpenSSL 0.9.7d 17 Mar 20 04 2004.10.08 13:05:20 LOG7[21833:1]: RAND_status claims sufficient entropy for the PRNG 2004.10.08 13:05:20 LOG6[21833:1]: PRNG seeded successfully 2004.10.08 13:05:20 LOG5[21833:1]: FD_SETSIZE=1024, file ulimit=64 -> 29 clients allowed 2004.10.08 13:05:20 LOG7[21833:1]: FD 4 in non-blocking mode 2004.10.08 13:05:20 LOG7[21833:1]: SO_REUSEADDR option set on accept socket 2004.10.08 13:05:20 LOG7[21833:1]: SeS_SOCKS_NJ bound to 0.0.0.0:1373 2004.10.08 13:05:20 LOG7[21833:1]: FD 5 in non-blocking mode 2004.10.08 13:05:20 LOG7[21833:1]: FD 6 in non-blocking mode 2004.10.08 13:05:20 LOG7[21834:1]: Created pid file /stunnel-client.pid 2004.10.08 13:05:25 LOG7[21834:1]: SeS_SOCKS_NJ accepted FD=0 from 155.184.22.17:62844 2004.10.08 13:05:25 LOG7[21834:1]: FD 0 in non-blocking mode I appreciate all help with this. Jai

1 0

Compilation problem of stunnel-4.05 on solaris 9
by Nada Machkova CEI-OI Banska Bystrica 08 Oct '04

08 Oct '04

Hi Didier try to find and set direct path to the ssl/lib before ./configure setenv LD_LIBRARY_PATH /usr/openwin/lib:/usr/dt/lib:/usr/local/lib:/usr/local/ssl/lib ./configure ... Nada

1 0

Stunnel question
by Rick Cone, Secure Payment Systems 06 Oct '04

06 Oct '04

I use Stunnel as a server that connects locally to a port with an application running (called Mlink). The software on that port will only allow 1 connection on the port at a time, not achieving a (true) socket server environment. Does anyone know of a piece of software (like a load balancer) that would accept connections on a specific port (from Stunnel in this case...), and then round-robin connections (or something thereof) to a set of ports? Thanks, Rick Cone Secure Payment Systems 801 8th St. #150-D Greeley, CO 80631 970-352-9434 (office) 970-352-0122 (fax, call office first) rcone(a)securepaymentsystems.com Note: This electronic message and attachments, if any, contain information which is intended solely for the designated recipients. Unauthorized disclosure, copying, distribution, or other use of the contents of this message or attachments, in whole or in part, is prohibited without express authorization of the author of this message.

2 1

Problem running Stunnel
by Robin Martin 06 Oct '04

06 Oct '04

When I run stunnel nothing seems to be happening. The terminal accepts = the command but does nothing. The log file doesn't produce any output = either nor does running stunnel in the foreground. As I understand it, I am trying to wrap my imapd server using stunnel. = Obviously installed imapd, and openssl.=20 In my config file I've got [imaps] accept =3D 993 exec =3D /usr/local/libexec/imapd execargs =3D imapd What is meant to happen when I run stunnel, is there a way that I can = test if it is working. I previously tested imapd using telnet 0 143. I'm = using this=20 http://www.stepwise.com/Articles/Workbench/eart.4.0.html article but its out of date, uses 3.x command line inputs, so I've tried = to convert those to the config file. Thanks, your help is greatly appreciated. Regards, ---- Robin Martin Email: robmar(a)gmail.com

1 0

stunnel dies on win32 - Try again with out HTML
by Richard Whiffen 05 Oct '04

05 Oct '04

We have a problem where stunnel dies on our Win32 boxes when we attempt load tests: stunnel 4.05 on x86-pc-mingw32-gnu WIN32 with OpenSSL 0.9.7d 17 Mar 2004 Global options cert = stunnel.pem ciphers = ALL:!ADH:+RC4:@STRENGTH debug = 5 key = stunnel.pem RNDbytes = 64 RNDoverwrite = yes service = stunnel session = 300 seconds taskbar = yes verify = none Service-level options TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTidle = 43200 seconds When we had one stunnel.cnf for all services it would crash almost imediately (less than a minute after starting the load). When we created separate processes for each target server it lasts longer, 5 to 10 minutes, but still dies. The frustrating part is we get no indications in the log files of what's going on. It dies in seemingly random spots. The last log entry is never the same and there's nothing in the cmd window that launched it to indicate what happened. The conf is fairly simple: #script test conf cert = \stunnel\ohetestisg1.pem Cafile = \stunnel\css-ca-cert.pem CApath = \stunnel\certs output = \stunnel\stunnel-media.log #verify = 3 client = yes debug = 7 [**mediaserver] accept = 127.0.0.3:80 connect = 10.162.130.26:444 TIMEOUTclose = 0 We're connecting to a Cisco Content Server Switch if that helps. So I'm wondering where to go next. Any ideas on how to troubleshoot this? Rich Whiffen _________________________________________________________________ Check out Election 2004 for up-to-date election news, plus voter tools and more! http://special.msn.com/msn/election2004.armx

1 0

stunnel dies on win32
by Richard Whiffen 05 Oct '04

05 Oct '04

1 0

Stunnel.org
by ramesh k 05 Oct '04

05 Oct '04

Hi I have one little problem with stunnel .I saw your source and document very instresting .But I cant able to compile your souce code [Stunnel.org] in windows xp @ vc++ envirnment.and I have downloaded supportive compiler mingw ,openssl & libssl32.dll and libeay32.dll . In that source syslog.h is not supporting for vc++ . So kindly reply with Clear details to compile that source Regds Ramesh.k

1 0

Re: [stunnel-users] Bug or bad configuration ?
by Michal Trojnara 04 Oct '04

04 Oct '04

Dear fwd, > stunnel: md_rand.c:312: ssleay_rand_add: Assertion `md_c[1] == > md_count[1]' > failed. > 2004.10.03 10:14:44 LOG5[30267:1024]: Received signal 15; terminating Your OpenSSL library is not properly compiled: http://lists.freebsd.org/pipermail/freebsd-bugs/2003-April/000362.html > # stunnel -version > stunnel 4.05 on i686-pc-linux-gnu PTHREAD+LIBWRAP with OpenSSL 0.9.7c 30 > Sep > 2003 You use an obsolete version of OpenSSL library. You should upgrade it. http://www.openssl.org/news/secadv_20040317.txt Best regards, Mike

2 1

Stunnel help
by Mohammed Riyaz 30 Sep '04

30 Sep '04

Hi, I have installed stunnel-4.05 along with openssl-0.9.7d. I am not able to run it in either daemon or client mode. I read through the stunnel.org webpage but could find any help. when i run /usr/local/sbin/stunnel -d 7898 -r 631 i get the following output. 2004.09.24 15:10:47 LOG3[4752:1073866848]: -d: No such file or directory (2) Syntax: stunnel [filename] | -fd [n] | -help | -version | -sockets filename - use specified config file instead of /usr/local/etc/stunnel/stunnel.conf -fd n - read the config file from specified file descriptor -help - get config file help -version - display version and defaults -sockets - display default socket options I have copied the sampel config file as /usr/local/etc/stunnel/stunnel.conf. what should i do to avoid this? Is there any good document avalibel explaing step by step installation and configuration of stunnel? Thank you, -Riyaz

2 1

stunnel: command not found
by Robin Martin 24 Sep '04

24 Sep '04

Hi Guys, I am trying to install stunnel-4.05 on Mac 10.2.8. I am following this http://www.stepwise.com/Articles/Workbench/eart.4.0.html article. I am up to Step 8: Testing your setup. The article is old, but I am aware that stunnel 4.* requires a configuration file rather than command line inputs. My config file is [imapd] accept = 993 exec = /usr/local/libexec/imapd execargs = imaps My problem is, when I run (taken from the article) sudo stunnel -c -f -r localhost:993 I get the following, stunnel: command not found Can I use command line arguments here? It seems to be a very non-specific error. While hunting around for an answer I read somewhere else that stunnel likes to die silently? So perhaps I am doing something wrong but getting a vague error message? Is there a log file that I can look at? Thank you for any help, it is appreciated and I hope I've provided sufficient information. Best Regards, Robin _________________________________________________________________ Find love today with ninemsn personals. Click here: http://ninemsn.match.com?referrer=hotmailtagline

2 1

stunnel: command not found
by Robin Martin 24 Sep '04

24 Sep '04

Hi Guys, I am trying to install stunnel-4.05 on Mac 10.2.8. I am following this http://www.stepwise.com/Articles/Workbench/eart.4.0.html article. I am up to Step 8: Testing your setup. The article is old, but I am aware that stunnel 4.* requires a configuration file rather than command line inputs. My config file is [imapd] accept = 993 exec = /usr/local/libexec/imapd execargs = imaps My problem is, when I run (taken from the article) sudo stunnel -c -f -r localhost:993 I get the following, stunnel: command not found Can I use command line arguments here? It seems to be a very non-specific error. While hunting around for an answer I read somewhere else that stunnel likes to die silently? So perhaps I am doing something wrong but getting a vague error message? Is there a log file that I can look at? Thank you for any help, it is appreciated and I hope I've provided sufficient information. Best Regards, Robin

1 0

rsync over stunnel 4
by Steven Timm 23 Sep '04

23 Sep '04

There's an example of rsync over stunnel at http://www.stunnel.org/examples/rsync_mike.html but it appears to be using stunnel 3 syntax. Has anyone successfully made this work using stunnel 4? right now /etc/stunnel.conf is same on client and server, has [rsync] accept = 2222 connect = 873 Steve Timm ------------------------------------------------------------------ Steven C. Timm, Ph.D (630) 840-8525 timm(a)fnal.gov http://home.fnal.gov/~timm/ Fermilab Computing Div/Core Support Services Dept./Scientific Computing Section Assistant Group Leader, Farms and Clustered Systems Group Lead of Computing Farms Team

1 0

performance data
by Michal Trojnara 21 Sep '04

21 Sep '04

Dear Users, I've prepared a table that summarizes my benchmarks. I hope you'll find it useful. http://stunnel.mirt.net/perf.html Best regards, Mike

1 0

Pass phrase dialog
by John Bradley 18 Sep '04

18 Sep '04

When I start stunnel 4.05, I am presented with a dialog that requests that I enter a pass phrase in order to access our private key. Is there anyway to bypass this dialog. I would like to add the pass phrase to the config file, so that the dialog isn't presented. Security isn't an issue. Our config file will be in a secure location. Otherwise, our operations people are going the have to know the pass phrase to start stunnel. Thanks for your help. John ---------------------------------------------- John Bradley Software Development Lava Trading Inc. 95 Morton Street, 4th Floor New York, NY 10014 Tel: 212.609.0162 Fax: 212.609.0101 www.lavatrading.com <http://www.lavatrading.com/> This communication (including attachments) contains information that may be confidential. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, copying or use of this communication or the information in it (including, in any attachments) is strictly prohibited. If you have received this communication in error please notify us by e-mail or by telephone 212-609-0162 and then delete the e-mail and all attachments and any copies thereof.

2 1

unclosed connection issue
by Ken G 15 Sep '04

15 Sep '04

I'm running stunnel 3.xx with thttpd (an embedded http server) on a small embedded machine on a pci card running linux. Establishing ssh, ftp, and http connections and using OpenSSL has all worked fine since they've been installed. I've been experiencing a strange issue. It seems that stunnel fails (somehow) to inform https clients that the connection has been closed. The sequence of events that I'm observing goes like this: T+0.0s: https client initiates request on port 443 (https). T+0.1s: stunnel establishes connection with thttpd on port 80. T+0.4s: thttpd finishes and dies, closing connection with stunnel. T+0.5s: stunnel finishes sending thttpd's output to its client, and then stops, believing that it has finished that connection. If forked, this copy of stunnel dies. The client (internet explorer, firefox, mozilla... doesn't matter) still believes that the connection is active, and waits for additional data. T+10.5s: Roughly 10 seconds later the client decides that the server timed out and displays what has been sent so far, which is the entire page. The only visible symptom is that small webpages seem to take 10 seconds to load. The visible symptom, then, is that webpages below a certain size (where that size is determined by the browser's willingness to refresh its view as data is being sent) take about 10 seconds to load. Is it possible that this behavior is due to stunnel? _______________________________ Do you Yahoo!? Express yourself with Y! Messenger! Free. Download now. http://messenger.yahoo.com

1 0

verify option question
by Alaadin 13 Sep '04

13 Sep '04

hello, i am using stunnel4.x under linux in my server i set verify option level 3 and in my clinet i added stunnel.pem so verify can happen now can my isp knows my key of encrytion and decrypt ? so it is safe to set verify level 3 ? or it shouldnot ? can my isp decrpt my traffic or knows what sites i visted? thanks

1 0

Wish: Option verify service-dependent
by Hans Werner Strube 13 Sep '04

13 Sep '04

With stunnel-4.x, it would be greatly desirable to make the option "verify" (and possibly the related certs) in stunnel.conf service-dependent rather than global. I have not looked at the code sufficiently to determine whether and how this could be possible.

2 1

Re: [stunnel-users] Stunnel-3.26 / OpenSSL 0.9.6m / Solaris / SSL _accept: Peer sudden ly disconnected
by Martin Kneissl 13 Sep '04

13 Sep '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michal Trojnara wrote: | | What about using my stunnel3 script instead? | | BTW: I really would like to know your comments on this script. | Does anyone need stunnel 3.x, now? | Unfortunately we will have to keep stunnel 3.x for some time (probably at least until next summer), due to a large distributed installation. I appreciate to have the wrapper script to migrate the current installations. If this was available when stunnel 4 was released we probably would have it in our installations right now... Anyone to verify my patch for stunnel-3.26? Best regards, Martin. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3-nr1 (Windows XP) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBRU5SnNbgBz1XxU4RAspgAJ9akmjZNTOig+YW69nRUCDX/hfTFwCfSwqL TKb3reUiIdYwVntSZSgQVgg= =wb9x -----END PGP SIGNATURE-----

1 0

Stunnel-3.26 / OpenSSL 0.9.6m / Solaris / SSL_accept: Peer sudden ly disconnected
by "Kneißl, Martin" 10 Sep '04

10 Sep '04

Hello everybody, I recompiled the newest "traditional" versions of OpenSSL and stunnel on Solaris, Linux, and HPUX. None of the defaults were changed except for --prefix and --openssldir/--with-ssl and --install_prefix Simple tests went through without problems on Linux and HPUX. For Solaris I have a big problem. Any help is appreciated, for example a trustworthy Stunnel-3.26 binary statically linked with OpenSSL 0.9.6m for Solaris 2.6 could also help. Summary ======= Stunnel listens on host medusa 12480 for SSL and forwards plain HTTP to apache on another host (sirius). When I try a HTTPS request to medusa:12480 using a browser or wget, the connection is broken immediately. When stunnel runs under the system call tracer truss the same commands succeed most of the time. In the truss output one can see an EAGAIN on the -r socket of stunnel. That might indicate that there is a problem when TCP buffers do not fill quickly receiving on the -r side. Details ======= Client side: (IP is 192.168.50.153) C:\>wget --spider https://medusa:12480 --12:59:18-- https://medusa:12480/ => `index.html' Resolving medusa... 192.168.41.13 Connecting to medusa[192.168.41.13]:12480... connected. Unable to establish SSL connection. Unable to establish SSL connection. Stunnel side: [mkn@medusa] stunnel-3.26 721$ ./stunnel -p ./stunnel.pem -D 7 -d 12480 -r sirius:80 -f -Pnone 2004.09.08 13:06:52 LOG5[29399:1]: Using 'sirius.80' as tcpwrapper service name 2004.09.08 13:06:52 LOG4[29399:1]: Wrong permissions on ./stunnel.pem 2004.09.08 13:06:52 LOG7[29399:1]: Snagged 64 random bytes from /nfss/home/mkn/.rnd 2004.09.08 13:06:53 LOG7[29399:1]: Wrote 1024 new random bytes to /nfss/home/mkn/.rnd 2004.09.08 13:06:53 LOG7[29399:1]: RAND_status claims sufficient entropy for the PRNG 2004.09.08 13:06:53 LOG6[29399:1]: PRNG seeded successfully 2004.09.08 13:06:53 LOG7[29399:1]: Certificate: ./stunnel.pem 2004.09.08 13:06:53 LOG5[29399:1]: stunnel 3.26 on sparc-sun-solaris2.6 PTHREAD+LIBWRAP with OpenSSL 0.9.6m 17 Mar 2004 2004.09.08 13:06:53 LOG7[29399:1]: No pid file being created 2004.09.08 13:06:53 LOG5[29399:1]: FD_SETSIZE=1024, file ulimit=64 -> 28 clients allowed 2004.09.08 13:06:53 LOG7[29399:1]: SO_REUSEADDR option set on accept socket 2004.09.08 13:06:53 LOG7[29399:1]: sirius.80 bound to 0.0.0.0:12480 2004.09.08 13:06:56 LOG7[29399:1]: sirius.80 accepted FD=7 from 192.168.50.153:1937 2004.09.08 13:06:56 LOG7[29399:4]: sirius.80 started 2004.09.08 13:06:56 LOG5[29399:4]: sirius.80 connected from 192.168.50.153:1937 2004.09.08 13:06:56 LOG7[29399:4]: sirius.80 connecting 192.168.41.223:80 2004.09.08 13:06:56 LOG7[29399:4]: Remote FD=9 initialized 2004.09.08 13:06:56 LOG7[29399:4]: Stunnel manual RSA blinding enabled 2004.09.08 13:06:56 LOG7[29399:4]: SSL state (accept): before/accept initialization 2004.09.08 13:06:56 LOG7[29399:4]: SSL state (accept): SSLv3 read client hello A 2004.09.08 13:06:56 LOG7[29399:4]: SSL state (accept): SSLv3 write server hello A 2004.09.08 13:06:56 LOG7[29399:4]: SSL state (accept): SSLv3 write certificate A 2004.09.08 13:06:56 LOG7[29399:4]: SSL state (accept): SSLv3 write server done A 2004.09.08 13:06:56 LOG7[29399:4]: SSL state (accept): SSLv3 flush data 2004.09.08 13:06:56 LOG3[29399:4]: SSL_accept: Peer suddenly disconnected 2004.09.08 13:06:56 LOG7[29399:4]: sirius.80 finished (0 left) [mkn@medusa] stunnel-3.26 722$ ./stunnel -V stunnel 3.26 on sparc-sun-solaris2.6 PTHREAD+LIBWRAP with OpenSSL 0.9.6m 17 Mar 2004 Default behaviour: run in inetd mode (unless -d used) run in background (unless -f used) run in ssl server mode (unless -c used) Compile time defaults: -v level no verify -a directory (none) -A file (none) -S sources 2 -t timeout 300 seconds -B bytes 64 -D level 5 -P pid dir /opt/stunnel/var/stunnel/ -p pemfile in server mode: stunnel.pem in client mode: none Socket option defaults: Option Accept Local Remote OS default SO_DEBUG -- -- -- 0 SO_DONTROUTE -- -- -- 0 SO_KEEPALIVE -- -- -- 0 SO_LINGER -- -- -- 0:0 SO_OOBINLINE -- -- -- 0 SO_RCVBUF -- -- -- 8192 SO_SNDBUF -- -- -- 8192 SO_RCVLOWAT -- -- -- -- SO_SNDLOWAT -- -- -- -- SO_RCVTIMEO -- -- -- -- SO_SNDTIMEO -- -- -- -- SO_REUSEADDR 1 -- -- 0 IP_TOS -- -- -- 0 IP_TTL -- -- -- 255 TCP_NODELAY -- -- -- 0 [mkn@medusa] stunnel-3.26 724$ uname -a SunOS medusa 5.6 Generic_105181-39 sun4u sparc SUNW,Ultra-Enterprise [mkn@medusa] stunnel-3.26 726$ gcc -v Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.6/2.95.2/specs gcc version 2.95.2 19991024 (release) When running the same stunnel under truss, I sometimes have success in retrieving the document, but sometimes I get: (...initialisation omitted...) poll(0xEFFFD4E0, 2, -1) = 1 fcntl(7, F_GETFL, 0x00000000) = 2 fstat64(7, 0xEFFFF3D8) = 0 getsockopt(7, 65535, 8192, 0xEFFFF4DC, 0xEFFFF4D4) = 0 fstat64(7, 0xEFFFF3D8) = 0 getsockopt(7, 65535, 8192, 0xEFFFF4DC, 0xEFFFF4D8) = 0 setsockopt(7, 65535, 8192, 0xEFFFF4DC, 4) = 0 fcntl(7, F_SETFL, 0x00000082) = 0 accept(7, 0xEFFFF5D0, 0xEFFFF548) = 8 fstat64(7, 0xEFFFF3D8) = 0 getsockopt(7, 65535, 8192, 0xEFFFF4DC, 0xEFFFF4D8) = 0 setsockopt(7, 65535, 8192, 0xEFFFF4DC, 4) = 0 fcntl(7, F_SETFL, 0x00000002) = 0 time() = 1094642471 getpid() = 2339 [2337] write(4, 0x000E763C, 83) = 83 2 0 0 4 . 0 9 . 0 8 1 3 : 2 1 : 1 1 L O G 7 [ 2 3 3 9 : 1 ] : s i r i u s . 8 0 a c c e p t e d F D = 8 f r o m 1 9 2 . 1 6 8 . 5 0 . 1 5 3 : 2 7 6 3\n fcntl(8, F_SETFD, 0x00000001) = 0 lwp_cond_signal(0xEF66B278) = 0 lwp_cond_wait(0xEF66B278, 0xEF66B288, 0xEF565C48) = 0 lwp_self() = 3 time() = 1094642471 getpid() = 2339 [2337] write(4, 0x000E763C, 52) = 52 2 0 0 4 . 0 9 . 0 8 1 3 : 2 1 : 1 1 L O G 7 [ 2 3 3 9 : 4 ] : s i r i u s . 8 0 s t a r t e d\n brk(0x000F73A8) = 0 brk(0x000FF3A8) = 0 getpeername(8, 0x000F56C4, 0xEF20BC78) = 0 getpid() = 2339 [2337] getpeername(8, 0x000DF2E0, 0xEF20B44C) = 0 getsockname(8, 0x000DF2F0, 0xEF20B44C) = 0 open("/etc/hosts.allow", O_RDONLY) Err#2 ENOENT getpid() = 2339 [2337] open("/proc/2339/psinfo", O_RDONLY) = 9 read(9, "\f\0 F H\0\0\005\0\0\t #".., 336) = 336 close(9) = 0 fstat(-1, 0xEF209E40) Err#9 EBADF open("/dev/conslog", O_WRONLY) = 9 fcntl(9, F_SETFD, 0x00000001) = 0 fstat(9, 0xEF209E40) = 0 fstat(9, 0xEF20A8A0) = 0 time() = 1094642471 getpid() = 2339 [2337] putmsg(9, 0xEF209F58, 0xEF209F4C, 0) = 0 open("/etc/.syslog_door", O_RDONLY) = 10 door_info(10, 0xEF209E90) = 0 getpid() = 2339 [2337] door_call(10, 0xEF209E78) = 0 close(10) = 0 open("/etc/hosts.deny", O_RDONLY) Err#2 ENOENT fstat(9, 0xEF20A8A0) = 0 time() = 1094642471 getpid() = 2339 [2337] putmsg(9, 0xEF209F58, 0xEF209F4C, 0) = 0 open("/etc/.syslog_door", O_RDONLY) = 10 door_info(10, 0xEF209E90) = 0 getpid() = 2339 [2337] door_call(10, 0xEF209E78) = 0 close(10) = 0 time() = 1094642471 getpid() = 2339 [2337] write(4, 0x000E763C, 79) = 79 2 0 0 4 . 0 9 . 0 8 1 3 : 2 1 : 1 1 L O G 5 [ 2 3 3 9 : 4 ] : s i r i u s . 8 0 c o n n e c t e d f r o m 1 9 2 . 1 6 8 . 5 0 . 1 5 3 : 2 7 6 3\n so_socket(2, 2, 0, "", 1) = 10 time() = 1094642471 getpid() = 2339 [2337] write(4, 0x000E763C, 73) = 73 2 0 0 4 . 0 9 . 0 8 1 3 : 2 1 : 1 1 L O G 7 [ 2 3 3 9 : 4 ] : s i r i u s . 8 0 c o n n e c t i n g 1 9 2 . 1 6 8 . 4 1 . 2 2 3 : 8 0\n connect(10, 0xEF20BC00, 16) = 0 time() = 1094642471 getpid() = 2339 [2337] write(4, 0x000E763C, 59) = 59 2 0 0 4 . 0 9 . 0 8 1 3 : 2 1 : 1 1 L O G 7 [ 2 3 3 9 : 4 ] : R e m o t e F D = 1 0 i n i t i a l i z e d\n time() = 1094642471 getpid() = 2339 [2337] time() = 1094642471 getpid() = 2339 [2337] write(4, 0x000E763C, 70) = 70 2 0 0 4 . 0 9 . 0 8 1 3 : 2 1 : 1 1 L O G 7 [ 2 3 3 9 : 4 ] : S t u n n e l m a n u a l R S A b l i n d i n g e n a b l e d\n time() = 1094642471 brk(0x000FF3A8) = 0 brk(0x001033A8) = 0 time() = 1094642471 getpid() = 2339 [2337] write(4, 0x000E763C, 83) = 83 2 0 0 4 . 0 9 . 0 8 1 3 : 2 1 : 1 1 L O G 7 [ 2 3 3 9 : 4 ] : S S L s t a t e ( a c c e p t ) : b e f o r e / a c c e p t i n i t i a l i z a t i o n\n brk(0x001033A8) = 0 brk(0x001093A8) = 0 brk(0x001093A8) = 0 brk(0x0010D3A8) = 0 read(8, 0x00102C78, 11) Err#11 EAGAIN time() = 1094642471 getpid() = 2339 [2337] write(4, 0x000E763C, 73) = 73 2 0 0 4 . 0 9 . 0 8 1 3 : 2 1 : 1 1 L O G 3 [ 2 3 3 9 : 4 ] : S S L _ a c c e p t : P e e r s u d d e n l y d i s c o n n e c t e d\n setsockopt(10, 65535, 128, 0xEF20BC78, 8) = 0 close(10) = 0 setsockopt(8, 65535, 128, 0xEF20BC78, 8) = 0 close(8) = 0 time() = 1094642471 getpid() = 2339 [2337] write(4, 0x000E763C, 62) = 62 2 0 0 4 . 0 9 . 0 8 1 3 : 2 1 : 1 1 L O G 7 [ 2 3 3 9 : 4 ] : s i r i u s . 8 0 f i n i s h e d ( 0 l e f t )\n lwp_cond_signal(0xEF66B278) = 0 lwp_cond_wait(0xEF66B278, 0xEF66B288, 0xEF543CA0) = 0 lwp_mutex_unlock(0xEF66B288) = 0 lwp_mutex_lock(0xEF66B288) = 0 time() = 1094642471 lwp_mutex_lock(0xEF66B288) = 0 lwp_cond_broadcast(0xEF670F50) = 0 poll(0xEFFFD4E0, 2, -1) (sleeping...) With kind regards, Martin Kneissl _________________________ Atos Worldline GmbH CRM and Telco Pascalstrasse 19 52076 Aachen Germany Phone: +49 (0) 2408 148 173 Fax: +49 (0) 2408 148 204 mailto:[email protected] www.atosworldline.de

2 1

Unable to open "/dev/cryptonet"
by alaadin＠alaadin.org 09 Sep '04

09 Sep '04

hello, when i run stunnel4.x under linux it gaves statment Unable to open "/dev/cryptonet" but it run normal .. what this error mean ? does it means stunnel is running but not encrypting ? and is there any problem running stunnel without "/dev/cryptonet ? secand question i have stunnel4.x running with verify 3 option can my isp read data between me and the other host .. if i am transmiting data through stunnel ? thanks.

2 1

Stunnel-3.26 / OpenSSL 0.9.6m / Solaris / SSL_accept: Peer sudden ly disconnected
by "Kneißl, Martin" 08 Sep '04

08 Sep '04

Correcting my previous post, > ... one can see an EAGAIN on the -r socket of stunnel. That's not true, the EAGAIN is on the accepted file descriptor. The problem is not solved, though ... Martin.

2 1

ssl - excessive message size
by Olivier Rademakers 06 Sep '04

06 Sep '04

Hi All, I am having trouble with a secure connection that used to work until now. I am using an stunnel connection to transfer data from an ldap server(127.0.0.1) to Win Active Directory server (machineB.domain.com) in order to update AD with updated ldap data. I have run stunnel in high verbosity manually so I could extract a log of a connection attempt. Here it is below: # stunnel -c -f -D 7 -P /var/ldapad/ -d 127.0.0.1:6360 -r machineB.domain.com:636 LOG5[9318:1]: Using 'machineB.domain.com.636' as tcpwrapper service name LOG7[9318:1]: RAND_status claims sufficient entropy for the PRNG LOG6[9318:1]: PRNG seeded successfully LOG5[9318:1]: stunnel 3.14 on sparc-sun-solaris2.7 PTHREAD LOG7[9318:1]: Created pid file /var/ldapad/stunnel.machineB.domain.com.636.pid LOG7[9318:1]: machineB.domain.com.636 bound to 127.0.0.1:6360 LOG7[9318:4]: machineB.domain.com.636 started LOG5[9318:4]: machineB.domain.com.636 connected from 127.0.0.1:55001 LOG7[9318:4]: machineB.domain.com.636 connecting 172.27.24.4:636 LOG7[9318:4]: Remote host connected LOG7[9318:4]: before/connect initialization LOG7[9318:4]: before/connect initialization LOG7[9318:4]: SSLv3 write client hello A LOG7[9318:4]: SSLv3 read server hello A LOG7[9318:4]: SSLv3 read server certificate A LOG7[9318:4]: SSLv3 read server key exchange A LOG7[9318:4]: SSLv3 read server key exchange A LOG3[9318:4]: SSL_connect: error:1408E098:SSL routines:SSL3_GET_MESSAGE:excessive message size LOG7[9318:4]: machineB.domain.com.636 finished (0 left) I have searched for this error but to no avail and am wondering if any of you have already come across such, and if so would have the beginning of a solution, and why not The Solution ;-) NB: When running stunnel with the "-c" operand (client mode), it is said the certificates are optional. I have captured the dialogue between the two machines, and apparently, the problem would be coming from the AD server as the DN (Distinguished Name) in the cert is ~8000 bytes long. The capture reveals other errors, checksum and more, so if needed I could append those to the problem stated here. Again, unix-ldap side has not changed to my knowledge. The script has always been the same, and it worked until now. The ldap server is SUN Solaris 2.8 with ssl 0.9.7b Version of stunnel: stunnel 3.21 on sparc-sun-solaris2.8 PTHREAD The AD server is a Windows 2000 machine. Please enlighten me, Olivier

1 1

win32 stunnel - quiet service install
by Michael Brown 03 Sep '04

03 Sep '04

Greetings, It would be great if while installing as a service on win32, there was an option to install quietly - i.e. only pop up a dialog box to the user if there's a problem. Any chance of somebody nice compiling me a binary that does this? :) M. -- Michael Brown {0x527670C0} | `One of the main causes of the fall of Systems Administrator | the Roman Empire was that, lacking zero, +1 519 888 7111 x2339 | they had no way to indicate successful michaelb(a)opentext.com | termination of their C programs.' - Firth

1 0

stunnel.conf
by Bob Williams 02 Sep '04

02 Sep '04

I'm totally new to Stunnel, which I'm running on a Windows XP platform. Where can I find a newbie's tutorial, e.g. to tell me what stunnel expects to find in stunnel.conf? Many thanks for your help. -- Bob

1 0

FTP site
by Michal Trojnara 02 Sep '04

02 Sep '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Users, My ftp site is back online. Thanks to Brian Hatch for reporting the problem. Best regards, Mike -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBN0vB/NU+nXTHMtERAqQ4AJ95KWL5PUpLZOMqQ4xOJYKqeVwgxgCfVIcc yMYncLDroE5wwHxJj5QtjGI= =Tryt -----END PGP SIGNATURE-----

1 0

stunnel3
by Michal Trojnara 01 Sep '04

01 Sep '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Users, I've written a perl script to emulate stunnel 3.x command line with stunnel versions 4.05 and later. I hope you'll like it. It's ready for download here: ftp://stunnel.mirt.net/stunnel/stunnel3 Best regards, Mike -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBNkEq/NU+nXTHMtERAvVGAJ4yuDLNrCOFTLfuuFRIzwShDkd/lwCfcVLa bLhgSAs2gXuzca8ZkJmCb9Q= =SInU -----END PGP SIGNATURE-----

1 0

Samba and stunnel
by Charles A. Monteiro 01 Sep '04

01 Sep '04

just wondering if anybody has had any difficulties with wrapping samba with stunnel, Sambo 3.0 apparently has dropped the support for ssl and therefore we are now also considering using stunnel to wrap Samba. thanks -Charles -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

1 0

Marketing Stunnel
by Charles A. Monteiro 01 Sep '04

01 Sep '04

So I now need to sell stunnel to those that make decisions. It would be helpful to get an understanding of how widely deployed it is. It also would be useful to have a number of company names that I could drop, especially if said companies were major corporations and especially if they were players in the finance/banking industry. thanks in advance, -Charles -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

4 4

re: [stunnel-users] client auth saga
by markzero＠logik.ath.cx 30 Aug '04

30 Aug '04

On Monday 30 of August 2004 20:38, markzero at logik.ath.cx wrote: > To be honest, I'm just generally paranoid. I'd rather have a prospective > attacker have to crack two passwords (the root and one wheel group) than > one. I thought I'd write the above just so I didn't get a big lecture, > hehe. :) > You're not paranoid enough. You still use passwords! 8-) I'm currently in the process of moving everything over to keypairs. I'm not blessed with security conscious users, and it's hard to get them to understand that a keypair is actually more convenient (especially if you use an agent). :) > > I recommend to use CAfile instead of CApath for simple configurations. > > It doesn't need a hashed directory and is not relative to chroot jail. > > So something like: > > CApath = /var/stunnel/certs > No! > CAfile = /var/stunnel/certs/your_cert.pem Oops, yeah I see what you mean. > I'm paranoid that someone has been at my testing configs now. :) I > previously had a working setup, which worries me even further as I *did* > use a symlink. Yes, you can use symlinks, but instead of: ln -s /a/b/c/x /a/b/c/y use: cd /a/b/c ln -s x y Please notice (ls -l) the results are not the same! That must have been it. > Best regards, > Mike > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (GNU/Linux) > > iD8DBQFBM3dd/NU+nXTHMtERApCuAKDe+RWT1S0MQJ4Fr+FSyk8qyqwgpwCg4XED > zBBeDZ6AU+LPU+iejancYGI= > =8uvI > -----END PGP SIGNATURE-----

1 0

client auth saga
by markzero＠logik.ath.cx 30 Aug '04

30 Aug '04

Frustration doesn't begin to express it! SEC Productions presents: * THE CLIENT AND SERVER AUTH SAGA * lets get on with it: complete walkthrough of ssl cert creation ----------------------------------------- By the way, please don't lecture me on ssh'ing into machines as root, they are located on an isolated network and of course, all logging in as root is disabled when they are put into production. :) There now follows a step by step account of everything so far... command prompt key: ca# = certificate authority machine (or my isolated desktop, whichever you prefer). records# = log server dns# = my dns server (the logging client) (obvious output of scripts snipped) ----------------------------------------- ca# cd /etc/ssl/misc ca# ./CA.sh -newca <snip> ca# ./CA.sh -newreq <snip> Request (and private key) is in newreq.pem ca# ./CA.sh -sign Signed certificate is in newcert.pem ca# cat newreq.pem newcert.pem > log_server.pem Then I realised that I needed it to be passwordless. ca# openssl rsa -in newreq.pem -out decryptedcert.pem ca# cat decryptedcert.pem newcert.pem > log_server_np.pem (log_server_np.pem is now passwordless) ca# scp log_server_np.pem records:/etc/ssl/stunnel_cert/ ca# scp demoCA/cacert.pem dns:/var/stunnel/cert/cacert.pem we'll just try with server side auth at the moment, on the loghost: records# cat /etc/stunnel/stunnel.conf cert = /etc/ssl/stunnel_cert/log_server_np.pem chroot = /var/stunnel pid = /var/run/stunnel.pid CApath = /certs CRLpath = /crls #verify = 2 debug = 7 output = stunnel.log setuid = _stunnel setgid = _stunnel [syslogngs] accept = 192.168.1.9:5514 connect = 127.0.0.1:5515 on the client: dns# cat /etc/stunnel/stunnel.conf #cert = /etc/stunnel/cert/clientkeycert.pem chroot = /var/stunnel pid = /var/run/stunnel.pid CAfile = /certs/cacert.pem CRLpath = /crls debug = 7 output = stunnel.log client = yes setuid = _stunnel setgid = _stunnel [syslogngs] accept = 127.0.0.1:5515 connect = 192.168.1.9:5514 looks good... dns# telnet localhost 5515 (in the interests of patience and readability, the output of stunnel.log isn't posted here, suffice to say the connection is successful and works) now to step up to client and server authentication. ca# openssl req -x509 -newkey rsa:2048 -keyout clientkey.pem -out \ clientcert -days 365 (forgot to use -nodes) ca# openssl rsa -in clientkey.pem -out client_decrypted_key.pem ca# cat clientkey.pem clientcert.pem > clientkeycert.pem ca# ./c_hash clientkeycert.pem 4410a4d9.0 => clientkeycert.pem ca# scp clientkeycert.pem dns:/etc/stunnel/cert ca# scp clientcert.pem records:/var/stunnel/certs on the server: records# ln -s /var/stunnel/certs/clientcert.pem \ /var/stunnel/certs/4410a4d9.0 adjust the stunnel.conf on both hosts accordingly: records# cat /etc/stunnel/stunnel.conf cert = /etc/ssl/stunnel_cert/log_server_np.pem chroot = /var/stunnel pid = /var/run/stunnel.pid CApath = /certs CRLpath = /crls verify = 3 debug = 7 output = stunnel.log setuid = _stunnel setgid = _stunnel [syslogngs] accept = 192.168.1.9:5514 connect = 127.0.0.1:5515 dns# cat /etc/stunnel/stunnel.conf cert = /etc/stunnel/cert/clientkeycert.pem chroot = /var/stunnel pid = /var/run/stunnel.pid CAfile = /certs/cacert.pem CRLpath = /crls debug = 7 output = stunnel.log client = yes setuid = _stunnel setgid = _stunnel [syslogngs] accept = 127.0.0.1:5515 connect = 192.168.1.9:5514 and just to show the permissions: records# ls -al /etc/ssl/ drwx------ 2 _stunnel _stunnel 512 Aug 30 12:19 stunnel_cert records# ls -al /etc/ssl/stunnel_cert -rw------- 1 _stunnel _stunnel 4320 Aug 30 12:19 log_server_np.pem records# ls -al /var/stunnel/certs/ lrwxr-xr-x 1 root _stunnel 33 Aug 30 14:33 4410a4d9.0 -> /var/stunnel/certs/clientcert.pem -rw------- 1 _stunnel _stunnel 1489 Aug 30 14:32 clientcert.pem dns# ls -al /etc/stunnel/dns# ls -al /etc/stunnel/ drwx------ 3 _stunnel _stunnel 512 Aug 29 21:50 . drwx------ 2 _stunnel _stunnel 512 Aug 30 14:18 cert -rw------- 1 _stunnel _stunnel 301 Aug 30 14:22 stunnel.conf -rw------- 1 _stunnel _stunnel 13401 Aug 29 22:21 stunnel.log dns# ls -al /etc/stunnel/cert/ -rw------- 1 _stunnel _stunnel 3168 Aug 30 14:18 clientkeycert.pem dns# ls -al /var/stunnel/ drwx------ 5 _stunnel _stunnel 512 Aug 29 21:28 . drwx------ 2 _stunnel _stunnel 512 Aug 30 13:59 cert drwx------ 2 _stunnel _stunnel 512 Aug 29 21:16 crl drwx------ 3 _stunnel _stunnel 512 Aug 29 21:28 var dns# ls -al /var/stunnel/cert/ drwx------ 2 _stunnel _stunnel 512 Aug 30 13:59 . -rw------- 1 _stunnel _stunnel 1115 Aug 30 13:59 cacert.pem now, to test. records# /usr/local/sbin/stunnel /etc/stunnel/stunnel.conf dns# /usr/local/sbin/stunnel /etc/stunnel/stunnel.conf the log files on both show no errors, lets try a connection from dns to records... dns# telnet localhost 5515 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Connection closed by foreign host. urgh! what went wrong? records# cat stunnel.log 2004.08.30 14:46:43 LOG5[27205:1006690304]: stunnel 4.05 on i386-unknown-openbsd3.5 PTHREAD with OpenSSL 0.9.7c 30 Sep 2003 2004.08.30 14:46:43 LOG7[27205:1006690304]: Snagged 64 random bytes from /dev/arandom 2004.08.30 14:46:43 LOG7[27205:1006690304]: RAND_status claims sufficient entropy for the PRNG 2004.08.30 14:46:43 LOG6[27205:1006690304]: PRNG seeded successfully 2004.08.30 14:46:43 LOG7[27205:1006690304]: Certificate: /etc/ssl/stunnel_cert/log_server_np.pem 2004.08.30 14:46:43 LOG7[27205:1006690304]: Key file: /etc/ssl/stunnel_cert/log_server_np.pem 2004.08.30 14:46:43 LOG7[27205:1006690304]: Verify directory set to /certs 2004.08.30 14:46:43 LOG7[27205:1006690304]: CRL directory set to /crls 2004.08.30 14:46:43 LOG5[27205:1006690304]: Peer certificate location /certs 2004.08.30 14:46:43 LOG5[27205:1006690304]: FD_SETSIZE=1024, file ulimit=128 -> 61 clients allowed 2004.08.30 14:46:43 LOG7[27205:1006690304]: FD 10 in non-blocking mode 2004.08.30 14:46:43 LOG7[27205:1006690304]: SO_REUSEADDR option set on accept socket 2004.08.30 14:46:43 LOG7[27205:1006690304]: syslogngs bound to 192.168.1.9:5514 2004.08.30 14:46:43 LOG7[27205:1006690304]: FD 11 in non-blocking mode 2004.08.30 14:46:43 LOG7[27205:1006690304]: FD 12 in non-blocking mode 2004.08.30 14:46:43 LOG7[20297:1006690304]: Created pid file /var/run/stunnel.pid 2004.08.30 14:46:51 LOG7[20297:1006690304]: syslogngs accepted FD=13 from 192.168.1.6:7109 2004.08.30 14:46:51 LOG7[20297:1006690304]: FD 13 in non-blocking mode 2004.08.30 14:46:51 LOG7[20297:1006693376]: syslogngs started 2004.08.30 14:46:51 LOG5[20297:1006693376]: syslogngs connected from 192.168.1.6:7109 2004.08.30 14:46:51 LOG7[20297:1006693376]: SSL state (accept): before/accept initialization 2004.08.30 14:46:51 LOG7[20297:1006693376]: SSL state (accept): SSLv3 read client hello A 2004.08.30 14:46:51 LOG7[20297:1006693376]: SSL state (accept): SSLv3 write server hello A 2004.08.30 14:46:51 LOG7[20297:1006693376]: SSL state (accept): SSLv3 write certificate A 2004.08.30 14:46:51 LOG7[20297:1006693376]: SSL state (accept): SSLv3 write certificate request A 2004.08.30 14:46:51 LOG7[20297:1006693376]: SSL state (accept): SSLv3 flush data 2004.08.30 14:46:51 LOG7[20297:1006693376]: waitforsocket: FD=13, DIR=read 2004.08.30 14:46:52 LOG7[20297:1006693376]: waitforsocket: ok 2004.08.30 14:46:52 LOG4[20297:1006693376]: VERIFY ERROR: depth=0, error=self signed certificate: /C=UK/L=London/O=SI/OU=SEC/CN=LogClient/emailAddress=root@localhost 2004.08.30 14:46:52 LOG7[20297:1006693376]: SSL alert (write): fatal: bad certificate 2004.08.30 14:46:52 LOG3[20297:1006693376]: SSL_accept: 140890B2: error:140890B2:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:no certificate returned 2004.08.30 14:46:52 LOG7[20297:1006693376]: syslogngs finished (0 left) --- dns# cat stunnel.log 2004.08.30 14:33:24 LOG5[10920:1006690304]: stunnel 4.05 on i386-unknown-openbsd3.5 PTHREAD with OpenSSL 0.9.7c 30 Sep 2003 2004.08.30 14:33:24 LOG7[10920:1006690304]: Snagged 64 random bytes from /dev/arandom 2004.08.30 14:33:24 LOG7[10920:1006690304]: RAND_status claims sufficient entropy for the PRNG 2004.08.30 14:33:24 LOG6[10920:1006690304]: PRNG seeded successfully 2004.08.30 14:33:24 LOG7[10920:1006690304]: Certificate: /etc/stunnel/cert/clientkeycert.pem 2004.08.30 14:33:24 LOG7[10920:1006690304]: Key file: /etc/stunnel/cert/clientkeycert.pem 2004.08.30 14:33:24 LOG5[10920:1006690304]: FD_SETSIZE=1024, file ulimit=128 -> 61 clients allowed 2004.08.30 14:33:24 LOG7[10920:1006690304]: FD 10 in non-blocking mode 2004.08.30 14:33:24 LOG7[10920:1006690304]: SO_REUSEADDR option set on accept socket 2004.08.30 14:33:24 LOG7[10920:1006690304]: syslogngs bound to 127.0.0.1:5515 2004.08.30 14:33:24 LOG7[10920:1006690304]: FD 11 in non-blocking mode 2004.08.30 14:33:24 LOG7[10920:1006690304]: FD 12 in non-blocking mode 2004.08.30 14:33:24 LOG7[11717:1006690304]: Created pid file /var/run/stunnel.pid 2004.08.30 14:33:30 LOG7[11717:1006690304]: syslogngs accepted FD=13 from 127.0.0.1:20109 2004.08.30 14:33:30 LOG7[11717:1006690304]: FD 13 in non-blocking mode 2004.08.30 14:33:30 LOG7[11717:1006693376]: syslogngs started 2004.08.30 14:33:30 LOG5[11717:1006693376]: syslogngs connected from 127.0.0.1:20109 2004.08.30 14:33:30 LOG7[11717:1006693376]: FD 14 in non-blocking mode 2004.08.30 14:33:30 LOG7[11717:1006693376]: syslogngs connecting 192.168.1.9:5514 2004.08.30 14:33:30 LOG7[11717:1006693376]: remote connect #1: EINPROGRESS: retrying 2004.08.30 14:33:30 LOG7[11717:1006693376]: waitforsocket: FD=14, DIR=write 2004.08.30 14:33:30 LOG7[11717:1006693376]: waitforsocket: ok 2004.08.30 14:33:30 LOG7[11717:1006693376]: Remote FD=14 initialized 2004.08.30 14:33:30 LOG7[11717:1006693376]: SSL state (connect): before/connect initialization 2004.08.30 14:33:30 LOG7[11717:1006693376]: SSL state (connect): SSLv3 write client hello A 2004.08.30 14:33:30 LOG7[11717:1006693376]: waitforsocket: FD=14, DIR=read 2004.08.30 14:33:30 LOG7[11717:1006693376]: waitforsocket: ok 2004.08.30 14:33:30 LOG7[11717:1006693376]: SSL state (connect): SSLv3 read server hello A 2004.08.30 14:33:30 LOG7[11717:1006693376]: SSL state (connect): SSLv3 read server certificate A 2004.08.30 14:33:30 LOG7[11717:1006693376]: SSL state (connect): SSLv3 read server certificate request A 2004.08.30 14:33:30 LOG7[11717:1006693376]: SSL state (connect): SSLv3 read server done A 2004.08.30 14:33:30 LOG7[11717:1006693376]: SSL state (connect): SSLv3 write client certificate A 2004.08.30 14:33:30 LOG7[11717:1006693376]: SSL state (connect): SSLv3 write client key exchange A 2004.08.30 14:33:30 LOG7[11717:1006693376]: SSL state (connect): SSLv3 write certificate verify A 2004.08.30 14:33:30 LOG7[11717:1006693376]: SSL state (connect): SSLv3 write change cipher spec A 2004.08.30 14:33:30 LOG7[11717:1006693376]: SSL state (connect): SSLv3 write finished A 2004.08.30 14:33:30 LOG7[11717:1006693376]: SSL state (connect): SSLv3 flush data 2004.08.30 14:33:30 LOG7[11717:1006693376]: waitforsocket: FD=14, DIR=read 2004.08.30 14:33:30 LOG7[11717:1006693376]: waitforsocket: ok 2004.08.30 14:33:30 LOG7[11717:1006693376]: SSL alert (read): fatal: bad certificate 2004.08.30 14:33:30 LOG3[11717:1006693376]: SSL_connect: 14094412: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate 2004.08.30 14:33:30 LOG7[11717:1006693376]: syslogngs finished (0 left) (sorry about the unwrapped lines) I've also tried using ktrace, but the ktrace.out drops off before the connection (making it useless). I don't understand what can be wrong, I've retraced my steps over and over. I did actually have it working before, but due to testing, reinstalled the OS and now it doesn't work. I'm loathe to install the developement tools, as there are so many it would be a nightmare to remove them after (prompting a reinstall, and look what happened last time). Any ideas? Anything I've done blindingly obviously wrong? Why did it work before and not now? ARGH! cheers mark

2 3

Stunnel 4.05 on AIX
by Baker Nelson 27 Aug '04

27 Aug '04

Hello all, Still having trouble getting stunnel 4.05 to run on my AIX 5.2 box. Wanted to pass along the following warning that showed up running the configure script. Could a problem with PTHEADS be causing the failure? Thanks baker checking for sys/select.h... yes checking tcpd.h usability... no checking tcpd.h presence... no checking for tcpd.h... no checking pthread.h usability... no checking pthread.h presence... yes configure: WARNING: pthread.h: present but cannot be compiled configure: WARNING: pthread.h: check for missing prerequisite headers? configure: WARNING: pthread.h: proceeding with the preprocessor's result configure: WARNING: ## ------------------------------------ ## configure: WARNING: ## Report this to bug-autoconf(a)gnu.org. ## configure: WARNING: ## ------------------------------------ ## checking for pthread.h... yes

1 0

Compilation problem of stunnel-4.05 on solaris 9
by PEYROL Didier 27 Aug '04

27 Aug '04

hi , I get this error when i try to do ./configure on stunnel-4.05 on solaris9 config.log in attachement. Some people could help me??? ./configure checking for a BSD-compatible install... auto/install-sh -c checking whether build environment is sane... yes checking whether make sets $(MAKE)... no checking for working aclocal... missing checking for working autoconf... missing checking for working automake... missing checking for working autoheader... missing checking for working makeinfo... missing checking build system type... sparc-sun-solaris2.9 checking host system type... sparc-sun-solaris2.9 checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for a BSD-compatible install... auto/install-sh -c checking whether make sets $(MAKE)... (cached) no checking for ld used by GCC... /usr/ccs/bin/ld checking if the linker (/usr/ccs/bin/ld) is GNU ld... no checking for /usr/ccs/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/ccs/bin/nm -p checking for a sed that does not truncate output... /usr/bin/sed checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking command to parse /usr/ccs/bin/nm -p output... ok checking how to run the C preprocessor... gcc -E checking for egrep... egrep checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... no checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for ranlib... : checking for strip... : checking for objdir... .libs checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.lo... yes checking if gcc supports -fno-rtti -fno-exceptions... yes checking whether the linker (/usr/ccs/bin/ld) supports shared libraries... yes checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... no checking dynamic linker characteristics... solaris2.9 ld.so checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no creating libtool checking for SSL directory... /usr/local/ssl checking for "/dev/urandom"... yes checking whether to disable RSA support... no checking whether to enable DH support... no checking for dlopen in -ldl... yes checking for shl_load in -ldld... no checking for gethostbyname in -lnsl... yes checking for socket in -lsocket... yes checking for pthread_create in -lpthread... yes checking for pthread_create in -lc_r... no checking for openpty in -lutil... no checking whether to use the libwrap (TCP wrappers) library... (default) checking for hosts_access in -lwrap... no checking for RSAref library... no checking for "/dev/ptmx"... yes checking for "/dev/ptc"... no checking grp.h usability... yes checking grp.h presence... yes checking for grp.h... yes checking for unistd.h... (cached) yes checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking tcpd.h usability... no checking tcpd.h presence... no checking for tcpd.h... no checking pthread.h usability... yes checking pthread.h presence... yes checking for pthread.h... yes checking sys/ioctl.h usability... yes checking sys/ioctl.h presence... yes checking for sys/ioctl.h... yes checking util.h usability... no checking util.h presence... no checking for util.h... no checking pty.h usability... no checking pty.h presence... no checking for pty.h... no checking stropts.h usability... yes checking stropts.h presence... yes checking for stropts.h... yes checking sys/filio.h usability... yes checking sys/filio.h presence... yes checking for sys/filio.h... yes checking sys/resource.h usability... yes checking sys/resource.h presence... yes checking for sys/resource.h... yes checking for snprintf... yes checking for vsnprintf... yes checking for openpty... no checking for _getpty... no checking for daemon... no checking for waitpid... yes checking for wait4... yes checking for sysconf... yes checking for getrlimit... yes checking for pthread_sigmask... yes checking for setgroups... yes checking for localtime_r... yes checking for chroot... yes checking for endhostent... yes checking for setsid... yes checking for unsigned char... yes checking size of unsigned char... configure: error: cannot compute sizeof (unsigned char), 77 See `config.log' for more details. BR Didier

1 0

MySQL client through stunnel on win32
by Rumi Szabolcs 26 Aug '04

26 Aug '04

Hello! I have tried the following setup: server: MySQL 4.0.20 with native OpenSSL 0.9.7d support on Linux client: MySQL 4.0.20 without SSL support, through stunnel 4.0.5 on WinXP As it can be suspected from the above, I was trying to use the mysqld with ssl support directly as the server side of the connection, without stunnel. I saw a pseudo-https client solution in the stunnel docs where this approach seemed to work. The client stunnel.conf: cert = client-test.crt key = client-test.key client = yes debug = debug [mysqlclient] accept = 3306 connect = server.host.fqdn:3306 The mysql client reported the following error, right after asking for the password: ERROR 2013: Lost connection to MySQL server during query Here is the log from the client stunnel: 2004.08.26 17:19:43 LOG5[2396:1256]: stunnel 4.05 on x86-pc-mingw32-gnu WIN32 with OpenSSL 0.9.7d 17 Mar 2004 2004.08.26 17:19:43 LOG7[2396:1908]: RAND_status claims sufficient entropy for the PRNG 2004.08.26 17:19:43 LOG6[2396:1908]: PRNG seeded successfully 2004.08.26 17:19:43 LOG7[2396:1908]: Certificate: client-test.crt 2004.08.26 17:19:43 LOG7[2396:1908]: Key file: client-test.key 2004.08.26 17:19:43 LOG5[2396:1908]: WIN32 platform: 30000 clients allowed 2004.08.26 17:19:43 LOG7[2396:1908]: FD 1828 in non-blocking mode 2004.08.26 17:19:43 LOG7[2396:1908]: SO_REUSEADDR option set on accept socket 2004.08.26 17:19:43 LOG7[2396:1908]: mysqlclient bound to 0.0.0.0:3306 2004.08.26 17:19:52 LOG7[2396:1908]: mysqlclient accepted FD=1836 from 127.0.0.1:3269 2004.08.26 17:19:52 LOG7[2396:1908]: FD 1836 in non-blocking mode 2004.08.26 17:19:52 LOG7[2396:1908]: Creating a new thread 2004.08.26 17:19:52 LOG7[2396:1908]: New thread created 2004.08.26 17:19:52 LOG7[2396:1816]: mysqlclient started 2004.08.26 17:19:52 LOG5[2396:1816]: mysqlclient connected from 127.0.0.1:3269 2004.08.26 17:19:52 LOG7[2396:1816]: FD 1816 in non-blocking mode 2004.08.26 17:19:52 LOG7[2396:1816]: mysqlclient connecting xx.xx.xx.xx:3306 2004.08.26 17:19:52 LOG7[2396:1816]: remote connect #1: EWOULDBLOCK: retrying 2004.08.26 17:19:52 LOG7[2396:1816]: waitforsocket: FD=1816, DIR=write 2004.08.26 17:19:52 LOG7[2396:1816]: waitforsocket: ok 2004.08.26 17:19:52 LOG7[2396:1816]: remote connect #2: EINVAL: ok 2004.08.26 17:19:52 LOG7[2396:1816]: Remote FD=1816 initialized 2004.08.26 17:19:52 LOG7[2396:1816]: SSL state (connect): before/connect initialization 2004.08.26 17:19:52 LOG7[2396:1816]: SSL state (connect): SSLv3 write client hello A 2004.08.26 17:19:52 LOG7[2396:1816]: SSL alert (write): fatal: handshake failure 2004.08.26 17:19:52 LOG3[2396:1816]: SSL_connect: 1408F10B: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number 2004.08.26 17:19:52 LOG7[2396:1816]: mysqlclient finished (0 left) What is wrong here? Thank you! Regards, Szabolcs Rumi

1 0

RE: [stunnel-users] Problem running Stunnel 4.05 on AIX 5.2
by Baker Nelson 25 Aug '04

25 Aug '04

HAH! Got it. Thanks for the help getting my debug info set up. Here is the backtrace from gdb: adev>#gdb /usr/local/sbin/stunnel /usr/local/ssl/core GNU gdb 5.0-aix51-020209 Copyright 2000 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "powerpc-ibm-aix5.2.0.0"... Core was generated by `stunnel'. Program terminated with signal 11, Segmentation fault. #0 0xd01199e8 in _sigsetmask () (gdb) backtrace #0 0xd01199e8 in _sigsetmask () #1 0xffffffff in ?? () from (unknown load module) (some reminders: I was trying to run stunnel 4.05 on AIX 5.2 with Openssl and keep get segmentation fault. Config sent previously) Thanks. Baker -----Original Message----- From: Michal Trojnara [mailto:[email protected]] Sent: Monday, August 23, 2004 5:05 PM To: Baker Nelson Subject: Re: [stunnel-users] Problem running Stunnel 4.05 on AIX 5.2 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 23 of August 2004 17:57, Baker Nelson wrote: > Finally got a new core dump to come out, was fooling with the client.c code > last week and wanted to start all from scratch. But, I can not get gdb to > work, does not find it. Is it an optional install for the gcc compiler? Just another useful GNU programming tool. Just like binutils, make or gcc. What about: http://www-1.ibm.com/servers/aix/products/aixos/linux/download.html ? Mike -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBKlwX/NU+nXTHMtERAveDAJ0XYkD35Iq7n9rjBzp+1IDu9nFQRwCgjjpG CmXLUwMJT9aygtsuQPWl5aY= =4qkl -----END PGP SIGNATURE-----

2 1

waitforsocket takes over 1 minute :-((
by Hartmut Gehrke-Tschudi 25 Aug '04

25 Aug '04

hi, I run stunnel 4.04 on i586-suse-linux-gnu PTHREAD with OpenSSL 0.9.6i [engine]. When I open up connection to my Mailserver for fetchmail to get mails I regularily have to wait for 1 1/2 minutes before it starts fetching here is part of stunnel.log (mark: 11:27:22 and 11:28:43) 2004.08.25 11:27:22 LOG7[16627:49154]: SSL state (connect): before/connect initialization 2004.08.25 11:27:22 LOG7[16627:49154]: SSL state (connect): SSLv3 write client hello A 2004.08.25 11:27:22 LOG7[16627:49154]: waitforsocket: FD=11, DIR=read 2004.08.25 11:28:43 LOG7[16627:49154]: waitforsocket: ok 2004.08.25 11:28:43 LOG7[16627:49154]: SSL state (connect): SSLv3 read server hello A 2004.08.25 11:28:43 LOG7[16627:49154]: waitforsocket: FD=11, DIR=read 2004.08.25 11:28:44 LOG7[16627:49154]: waitforsocket: ok What is the reason and can I change that. Thanks for any advice Hartmut -- Hartmut Gehrke-Tschudi * +++++++++++++++++++++++++++++++++++++++++ hgtschudi(a)free.de > * ++++ on croit mourir pour la patrie++++++ Bochum * ++++ on meurt pour des industriels ++++++ BRD * +++++++ Anatol France +++++++++ * +++++++++++++++++++++++++++++++++++++++++

1 0

Going from 3.x command line to 4.x .conf file
by Thomas Gagné 25 Aug '04

25 Aug '04

I'm having a problem connecting with sourcehost using stunnel w/ configuration files. The command line version from 3.x works. Here's the command line for 3.x ./stunnel -c -p client.pem -d localhost:2401 -r repository.sourcehosting.net:2402 -P none -f -v 3 -A cacert.pem and the conf file from 4.x # Some debugging stuff debug = 7 output = stunnel.log # Use it for client mode client = yes foreground = yes verify = 3 key = client.pem cert = cacert.pem # Service-level configuration [cvs] accept = 2401 connect = repository.sourcehosting.net:2402 When I run the older version it starts: ./stunnel -c -p client.pem -d localhost:2401 -r repository.sourcehosting.net:2402 -P none -f -v 3 -A cacert.pem 2004.08.24 21:30:18 LOG5[2221:16384]: Using 'repository.sourcehosting.net.2402' as tcpwrapper service name Enter PEM pass phrase: 2004.08.24 21:30:24 LOG5[2221:16384]: Peer certificate location 2004.08.24 21:30:24 LOG5[2221:16384]: stunnel 3.26 on i686-pc-linux-gnu PTHREAD with OpenSSL 0.9.7d 17 Mar 20042004.08.24 21:30:24 LOG5[2221:16384]: FD_SETSIZE=1024, file ulimit=1024 -> 500 clients allowed But when I run the newer version (with .conf) I get: 2004.08.24 21:31:43 LOG5[2236:4144017536]: stunnel 4.05 on i386-redhat-linux-gnu PTHREAD+LIBWRAP with OpenSSL 0.9.7a Feb 19 2003 2004.08.24 21:31:43 LOG7[2236:4144017536]: Snagged 64 random bytes from /home/tgagne/.rnd 2004.08.24 21:31:43 LOG7[2236:4144017536]: Wrote 1024 new random bytes to /home/tgagne/.rnd 2004.08.24 21:31:43 LOG7[2236:4144017536]: RAND_status claims sufficient entropy for the PRNG 2004.08.24 21:31:43 LOG6[2236:4144017536]: PRNG seeded successfully 2004.08.24 21:31:43 LOG7[2236:4144017536]: Certificate: cacert.pem 2004.08.24 21:31:43 LOG7[2236:4144017536]: Key file: client.pem 2004.08.24 21:31:47 LOG3[2236:4144017536]: SSL_CTX_use_RSAPrivateKey_file: B080074: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch I'm using the same cacert.pem and client.pem for both, as well as the same passphrase.

2 1

Problem running Stunnel 4.05 on AIX 5.2
by Baker Nelson 23 Aug '04

23 Aug '04

Hi all, I am trying to run Stunnel 4.05 on AIX 5.2 to secure our homegrown webserver. I have been searching archives all over the place, and have yet to find the answer, but have found many comments here and there that seem to indicate a problem with Stunnel on AIX. The problem, in a nutshell, is that I get an error on SSL_read in the stunnel log and it shuts down with a segmentation fault after the first connection, no matter what I do. Configuration info attached below. Any help anyone can give would be greatly appreciatted. Thanks Baker stunnel 4.05 on powerpc-ibm-aix5.2.0.0 FORK with OpenSSL 0.9.7d 17 Mar 2004 Global options cert = /usr/local/etc/stunnel/stunnel.pem ciphers = ALL:!ADH:+RC4:@STRENGTH debug = 5 key = /usr/local/etc/stunnel/stunnel.pem pid = /usr/local/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 TIMEOUTidle = 43200 seconds OpenSSL 0.9.7d 17 Mar 2004 conf-file: cert = /usr/local/ssl/stunnel.pem #chroot = /usr/local/var/run/stunnel/ pid = /usr/local/etc/stunnel/stunnel.pid setuid = HTTPD setgid = rrms #options = DONT_INSERT_EMPTY_FRAGMENTS # Some debugging stuff debug = 7 output = stunnel.log # Use it for client mode #client = yes foreground = yes # Service-level configuration [https] accept = 443 connect = 80 TIMEOUTclose = 0 stunnel - log (from running openssl s_client command to test setup): 2004.08.19 15:22:29 LOG5[16718:0]: stunnel 4.05 on powerpc-ibm-aix5.2.0.0 FORK w ith OpenSSL 0.9.7d 17 Mar 2004 2004.08.19 15:22:29 LOG4[16718:0]: Wrong permissions on /usr/local/ssl/stunnel.p em 2004.08.19 15:22:29 LOG7[16718:0]: Snagged 64 random bytes from //.rnd 2004.08.19 15:22:29 LOG7[16718:0]: Wrote 1024 new random bytes to //.rnd 2004.08.19 15:22:29 LOG7[16718:0]: RAND_status claims sufficient entropy for the PRNG 2004.08.19 15:22:29 LOG6[16718:0]: PRNG seeded successfully 2004.08.19 15:22:29 LOG7[16718:0]: Certificate: /usr/local/ssl/stunnel.pem 2004.08.19 15:22:29 LOG7[16718:0]: Key file: /usr/local/ssl/stunnel.pem 2004.08.19 15:22:29 LOG5[16718:0]: FD_SETSIZE=65534, file ulimit=65534 -> 31999 clients allowed 2004.08.19 15:22:29 LOG7[16718:0]: FD 4 in non-blocking mode 2004.08.19 15:22:29 LOG7[16718:0]: SO_REUSEADDR option set on accept socket 2004.08.19 15:22:29 LOG7[16718:0]: https bound to 0.0.0.0:443 2004.08.19 15:22:29 LOG7[16718:0]: FD 5 in non-blocking mode 2004.08.19 15:22:29 LOG7[16718:0]: FD 6 in non-blocking mode 2004.08.19 15:22:29 LOG7[16718:0]: Created pid file /usr/local/etc/stunnel/stunn el.pid 2004.08.19 15:22:30 LOG7[16718:0]: https accepted FD=7 from **ip**:33519 2004.08.19 15:22:30 LOG7[16718:0]: FD 7 in non-blocking mode 2004.08.19 15:22:30 LOG7[21344:0]: https started 2004.08.19 15:22:30 LOG5[21344:0]: https connected from **ip**:33519 2004.08.19 15:22:30 LOG7[21344:0]: SSL state (accept): before/accept initializat ion 2004.08.19 15:22:30 LOG7[21344:0]: SSL state (accept): SSLv3 read client hello A 2004.08.19 15:22:30 LOG7[21344:0]: SSL state (accept): SSLv3 write server hello A 2004.08.19 15:22:30 LOG7[21344:0]: SSL state (accept): SSLv3 write certificate A 2004.08.19 15:22:30 LOG7[21344:0]: SSL state (accept): SSLv3 write server done A 2004.08.19 15:22:30 LOG7[21344:0]: SSL state (accept): SSLv3 flush data 2004.08.19 15:22:30 LOG7[21344:0]: waitforsocket: FD=7, DIR=read 2004.08.19 15:22:30 LOG7[21344:0]: waitforsocket: ok 2004.08.19 15:22:30 LOG7[21344:0]: SSL state (accept): SSLv3 read client key exc hange A 2004.08.19 15:22:30 LOG7[21344:0]: SSL state (accept): SSLv3 read finished A 2004.08.19 15:22:30 LOG7[21344:0]: SSL state (accept): SSLv3 write change cipher spec A 2004.08.19 15:22:30 LOG7[21344:0]: SSL state (accept): SSLv3 write finished A 2004.08.19 15:22:30 LOG7[21344:0]: SSL state (accept): SSLv3 flush data 2004.08.19 15:22:30 LOG7[21344:0]: 1 items in the session cache 2004.08.19 15:22:30 LOG7[21344:0]: 0 client connects (SSL_connect()) 2004.08.19 15:22:30 LOG7[21344:0]: 0 client connects that finished 2004.08.19 15:22:30 LOG7[21344:0]: 0 client renegotiatations requested 2004.08.19 15:22:30 LOG7[21344:0]: 1 server connects (SSL_accept()) 2004.08.19 15:22:30 LOG7[21344:0]: 1 server connects that finished 2004.08.19 15:22:30 LOG7[21344:0]: 0 server renegotiatiations requested 2004.08.19 15:22:30 LOG7[21344:0]: 0 session cache hits 2004.08.19 15:22:30 LOG7[21344:0]: 0 session cache misses 2004.08.19 15:22:30 LOG7[21344:0]: 0 session cache timeouts 2004.08.19 15:22:30 LOG6[21344:0]: Negotiated ciphers: AES256-SHA S SLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 2004.08.19 15:22:30 LOG7[21344:0]: FD 4 in non-blocking mode 2004.08.19 15:22:30 LOG7[21344:0]: https connecting 127.0.0.1:80 2004.08.19 15:22:30 LOG7[21344:0]: Remote FD=4 initialized 2004.08.19 15:22:32 LOG7[21344:0]: Socket closed on read 2004.08.19 15:22:32 LOG7[21344:0]: SSL write shutdown (output buffer empty) 2004.08.19 15:22:32 LOG7[21344:0]: SSL alert (write): warning: close notify 2004.08.19 15:22:32 LOG7[21344:0]: SSL_shutdown retrying 2004.08.19 15:22:32 LOG7[21344:0]: select timeout waiting for SSL close_notify 2004.08.19 15:22:32 LOG5[21344:0]: Connection closed: 311 bytes sent to SSL, 9 b ytes sent to socket 2004.08.19 15:22:32 LOG7[21344:0]: removing pid file /usr/local/etc/stunnel/stun nel.pid

2 3

Stunnel to the rescue
by Steven Sporen 23 Aug '04

23 Aug '04

Hi, Is it possible to configure STUNNEL to provide support for STARTTLS with IMAP (Microsoft Exchange Server doesn't support this) Have a look at RFC2595 http://www.faqs.org/rfcs/rfc2595.html The reason is - Symbian cell phones only allow secure IMAP via this method they can't connect to SIMAP. Please help Thanks

2 1

RE: [stunnel-users] Newbie: Keep getting connection closed
by david-e.hansen＠ubs.com 17 Aug '04

17 Aug '04

Charles, Check to see if you are being bitten by the "Eudora" problem -- add the following line to the top of your stunnel.conf file, and see if it magically starts working: options = DONT_INSERT_EMPTY_FRAGMENTS You can also see a related set of mails from myself, describing the problem we had. Regards, David Hansen -----Original Message----- From: stunnel-users-admin(a)mirt.net [mailto:[email protected]]On Behalf Of Charles A. Monteiro Sent: Dienstag, 17. August 2004 18:31 To: stunnel-users(a)mirt.net Subject: [stunnel-users] Newbie: Keep getting connection closed We are using a proprietary protocol over tcp/ip which works fine and has for a number of years. I have tested it without stunnel and it checks fine as well. I keep getting the connection closed when I run through stunnel. I don't understand if something bad has actually happened i.e. from the error warnings. Is an "alert" a bad thing i.e. does it indicate that something is broken? Does stunnel normally close the connection after every message exchange? I have included the logs for both the stunnel client and server as well as the respective conf files. thanks in advance, -Charles --------------------------------------- client log: 2004.08.17 11:13:27 LOG7[1824:1544]: 55555 accepted FD=536 from 127.0.0.1:1085 2004.08.17 11:13:27 LOG7[1824:1544]: FD 536 in non-blocking mode 2004.08.17 11:13:27 LOG7[1824:1544]: Creating a new thread 2004.08.17 11:13:27 LOG7[1824:1544]: New thread created 2004.08.17 11:13:27 LOG7[1824:1040]: 55555 started 2004.08.17 11:13:27 LOG5[1824:1040]: 55555 connected from 127.0.0.1:1085 2004.08.17 11:13:27 LOG7[1824:1040]: FD 564 in non-blocking mode 2004.08.17 11:13:27 LOG7[1824:1040]: 55555 connecting 192.168.20.76:55555 2004.08.17 11:13:27 LOG7[1824:1040]: remote connect #1: EWOULDBLOCK: retrying 2004.08.17 11:13:27 LOG7[1824:1040]: waitforsocket: FD=564, DIR=write 2004.08.17 11:13:27 LOG7[1824:1040]: waitforsocket: ok 2004.08.17 11:13:27 LOG7[1824:1040]: Remote FD=564 initialized 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): before/connect initialization 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 write client hello A 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 read server hello A 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 read server certificate A 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 read server done A 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 write client key exchange A 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 write change cipher spec A 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 write finished A 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 flush data 2004.08.17 11:13:27 LOG7[1824:1040]: waitforsocket: FD=564, DIR=read 2004.08.17 11:13:27 LOG7[1824:1040]: waitforsocket: ok 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 read finished A 2004.08.17 11:13:27 LOG7[1824:1040]: 6 items in the session cache 2004.08.17 11:13:27 LOG7[1824:1040]: 7 client connects (SSL_connect()) 2004.08.17 11:13:27 LOG7[1824:1040]: 7 client connects that finished 2004.08.17 11:13:27 LOG7[1824:1040]: 0 client renegotiatations requested 2004.08.17 11:13:27 LOG7[1824:1040]: 0 server connects (SSL_accept()) 2004.08.17 11:13:27 LOG7[1824:1040]: 0 server connects that finished 2004.08.17 11:13:27 LOG7[1824:1040]: 0 server renegotiatiations requested 2004.08.17 11:13:27 LOG7[1824:1040]: 1 session cache hits 2004.08.17 11:13:27 LOG7[1824:1040]: 0 session cache misses 2004.08.17 11:13:27 LOG7[1824:1040]: 0 session cache timeouts 2004.08.17 11:13:27 LOG6[1824:1040]: Negotiated ciphers: AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 2004.08.17 11:13:27 LOG7[1824:1040]: Socket closed on read 2004.08.17 11:13:27 LOG7[1824:1040]: SSL write shutdown (output buffer empty) 2004.08.17 11:13:27 LOG7[1824:1040]: SSL alert (write): warning: close notify 2004.08.17 11:13:27 LOG7[1824:1040]: SSL_shutdown retrying 2004.08.17 11:13:27 LOG7[1824:1040]: SSL alert (read): warning: close notify 2004.08.17 11:13:27 LOG7[1824:1040]: SSL closed on SSL_read 2004.08.17 11:13:27 LOG7[1824:1040]: Socket write shutdown (output buffer empty) 2004.08.17 11:13:27 LOG5[1824:1040]: Connection closed: 110 bytes sent to SSL, 13 bytes sent to socket 2004.08.17 11:13:27 LOG7[1824:1040]: 55555 finished (0 left) ------------------------------------------------------------- server log: 2004.08.17 11:03:12 LOG7[28177:3073021920]: 55555 accepted FD=7 from 192.168.20.77:1086 2004.08.17 11:03:12 LOG7[28177:3073021920]: FD 7 in non-blocking mode 2004.08.17 11:03:12 LOG7[28177:3062528944]: 55555 started 2004.08.17 11:03:12 LOG5[28177:3062528944]: 55555 connected from 192.168.20.77:1086 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): before/accept initialization 2004.08.17 11:03:12 LOG7[28177:3062528944]: waitforsocket: FD=7, DIR=read 2004.08.17 11:03:12 LOG7[28177:3062528944]: waitforsocket: ok 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 read client hello A 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 write server hello A 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 write certificate A 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 write server done A 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 flush data 2004.08.17 11:03:12 LOG7[28177:3062528944]: waitforsocket: FD=7, DIR=read 2004.08.17 11:03:12 LOG7[28177:3062528944]: waitforsocket: ok 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 read client key exchange A 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 read finished A 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 write change cipher spec A 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 write finished A 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 flush data 2004.08.17 11:03:12 LOG7[28177:3062528944]: 2 items in the session cache 2004.08.17 11:03:12 LOG7[28177:3062528944]: 0 client connects (SSL_connect()) 2004.08.17 11:03:12 LOG7[28177:3062528944]: 0 client connects that finished 2004.08.17 11:03:12 LOG7[28177:3062528944]: 0 client renegotiatations requested 2004.08.17 11:03:12 LOG7[28177:3062528944]: 18 server connects (SSL_accept()) 2004.08.17 11:03:12 LOG7[28177:3062528944]: 10 server connects that finished 2004.08.17 11:03:12 LOG7[28177:3062528944]: 0 server renegotiatiations requested 2004.08.17 11:03:12 LOG7[28177:3062528944]: 2 session cache hits 2004.08.17 11:03:12 LOG7[28177:3062528944]: 0 session cache misses 2004.08.17 11:03:12 LOG7[28177:3062528944]: 6 session cache timeouts 2004.08.17 11:03:12 LOG6[28177:3062528944]: Negotiated ciphers: AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 2004.08.17 11:03:12 LOG7[28177:3062528944]: FD 8 in non-blocking mode 2004.08.17 11:03:12 LOG7[28177:3062528944]: 55555 connecting 192.168.20.76:4242 2004.08.17 11:03:12 LOG7[28177:3062528944]: remote connect #1: EINPROGRESS: retrying 2004.08.17 11:03:12 LOG7[28177:3062528944]: waitforsocket: FD=8, DIR=write 2004.08.17 11:03:12 LOG7[28177:3062528944]: waitforsocket: ok 2004.08.17 11:03:12 LOG7[28177:3062528944]: Remote FD=8 initialized 2004.08.17 11:03:12 LOG7[28177:3062528944]: Socket closed on read 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL alert (write): warning: close notify 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL write shutdown (output buffer empty) 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL alert (read): warning: close notify 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL closed on SSL_read 2004.08.17 11:03:12 LOG7[28177:3062528944]: Socket write shutdown (output buffer empty) 2004.08.17 11:03:12 LOG5[28177:3062528944]: Connection closed: 13 bytes sent to SSL, 110 bytes sent to socket 2004.08.17 11:03:12 LOG7[28177:3062528944]: 55555 finished (0 left) ------------------------------------------------------------------------------------------------------------------- My client stunnel.conf: cert=stunnel.pem client=yes debug=7 [55555] accept=localhost:55555 connect=192.168.20.76:55555 - eof - My server stunnel.conf: cert=stunnel.pem debug=7 output=stunnel.err [55555] accept=192.168.20.76:55555 connect=192.168.20.76:4242 - eof - -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/ _______________________________________________ stunnel-users mailing list stunnel-users(a)mirt.net http://stunnel.mirt.net/mailman/listinfo/stunnel-users Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.

2 1

Re: chrooting 4.05 - can't get UID for user _stunnel
by Brian Hatch 17 Aug '04

17 Aug '04

> Amazing how none of the OpenBSD packages ever actually seem to work. :) Whoa - them's fighting words. ;-) (Happily a Debian Linux user. My packages may be two years old, but they work, dammit.) -- Brian Hatch Anarchy: it's not the law, Systems and it's just a good idea. Security Engineer http://www.ifokr.org/bri/ Every message PGP signed

1 0

Newbie: Keep getting connection closed
by Charles A. Monteiro 17 Aug '04

17 Aug '04

We are using a proprietary protocol over tcp/ip which works fine and has for a number of years. I have tested it without stunnel and it checks fine as well. I keep getting the connection closed when I run through stunnel. I don't understand if something bad has actually happened i.e. from the error warnings. Is an "alert" a bad thing i.e. does it indicate that something is broken? Does stunnel normally close the connection after every message exchange? I have included the logs for both the stunnel client and server as well as the respective conf files. thanks in advance, -Charles --------------------------------------- client log: 2004.08.17 11:13:27 LOG7[1824:1544]: 55555 accepted FD=536 from 127.0.0.1:1085 2004.08.17 11:13:27 LOG7[1824:1544]: FD 536 in non-blocking mode 2004.08.17 11:13:27 LOG7[1824:1544]: Creating a new thread 2004.08.17 11:13:27 LOG7[1824:1544]: New thread created 2004.08.17 11:13:27 LOG7[1824:1040]: 55555 started 2004.08.17 11:13:27 LOG5[1824:1040]: 55555 connected from 127.0.0.1:1085 2004.08.17 11:13:27 LOG7[1824:1040]: FD 564 in non-blocking mode 2004.08.17 11:13:27 LOG7[1824:1040]: 55555 connecting 192.168.20.76:55555 2004.08.17 11:13:27 LOG7[1824:1040]: remote connect #1: EWOULDBLOCK: retrying 2004.08.17 11:13:27 LOG7[1824:1040]: waitforsocket: FD=564, DIR=write 2004.08.17 11:13:27 LOG7[1824:1040]: waitforsocket: ok 2004.08.17 11:13:27 LOG7[1824:1040]: Remote FD=564 initialized 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): before/connect initialization 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 write client hello A 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 read server hello A 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 read server certificate A 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 read server done A 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 write client key exchange A 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 write change cipher spec A 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 write finished A 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 flush data 2004.08.17 11:13:27 LOG7[1824:1040]: waitforsocket: FD=564, DIR=read 2004.08.17 11:13:27 LOG7[1824:1040]: waitforsocket: ok 2004.08.17 11:13:27 LOG7[1824:1040]: SSL state (connect): SSLv3 read finished A 2004.08.17 11:13:27 LOG7[1824:1040]: 6 items in the session cache 2004.08.17 11:13:27 LOG7[1824:1040]: 7 client connects (SSL_connect()) 2004.08.17 11:13:27 LOG7[1824:1040]: 7 client connects that finished 2004.08.17 11:13:27 LOG7[1824:1040]: 0 client renegotiatations requested 2004.08.17 11:13:27 LOG7[1824:1040]: 0 server connects (SSL_accept()) 2004.08.17 11:13:27 LOG7[1824:1040]: 0 server connects that finished 2004.08.17 11:13:27 LOG7[1824:1040]: 0 server renegotiatiations requested 2004.08.17 11:13:27 LOG7[1824:1040]: 1 session cache hits 2004.08.17 11:13:27 LOG7[1824:1040]: 0 session cache misses 2004.08.17 11:13:27 LOG7[1824:1040]: 0 session cache timeouts 2004.08.17 11:13:27 LOG6[1824:1040]: Negotiated ciphers: AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 2004.08.17 11:13:27 LOG7[1824:1040]: Socket closed on read 2004.08.17 11:13:27 LOG7[1824:1040]: SSL write shutdown (output buffer empty) 2004.08.17 11:13:27 LOG7[1824:1040]: SSL alert (write): warning: close notify 2004.08.17 11:13:27 LOG7[1824:1040]: SSL_shutdown retrying 2004.08.17 11:13:27 LOG7[1824:1040]: SSL alert (read): warning: close notify 2004.08.17 11:13:27 LOG7[1824:1040]: SSL closed on SSL_read 2004.08.17 11:13:27 LOG7[1824:1040]: Socket write shutdown (output buffer empty) 2004.08.17 11:13:27 LOG5[1824:1040]: Connection closed: 110 bytes sent to SSL, 13 bytes sent to socket 2004.08.17 11:13:27 LOG7[1824:1040]: 55555 finished (0 left) ------------------------------------------------------------- server log: 2004.08.17 11:03:12 LOG7[28177:3073021920]: 55555 accepted FD=7 from 192.168.20.77:1086 2004.08.17 11:03:12 LOG7[28177:3073021920]: FD 7 in non-blocking mode 2004.08.17 11:03:12 LOG7[28177:3062528944]: 55555 started 2004.08.17 11:03:12 LOG5[28177:3062528944]: 55555 connected from 192.168.20.77:1086 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): before/accept initialization 2004.08.17 11:03:12 LOG7[28177:3062528944]: waitforsocket: FD=7, DIR=read 2004.08.17 11:03:12 LOG7[28177:3062528944]: waitforsocket: ok 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 read client hello A 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 write server hello A 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 write certificate A 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 write server done A 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 flush data 2004.08.17 11:03:12 LOG7[28177:3062528944]: waitforsocket: FD=7, DIR=read 2004.08.17 11:03:12 LOG7[28177:3062528944]: waitforsocket: ok 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 read client key exchange A 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 read finished A 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 write change cipher spec A 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 write finished A 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL state (accept): SSLv3 flush data 2004.08.17 11:03:12 LOG7[28177:3062528944]: 2 items in the session cache 2004.08.17 11:03:12 LOG7[28177:3062528944]: 0 client connects (SSL_connect()) 2004.08.17 11:03:12 LOG7[28177:3062528944]: 0 client connects that finished 2004.08.17 11:03:12 LOG7[28177:3062528944]: 0 client renegotiatations requested 2004.08.17 11:03:12 LOG7[28177:3062528944]: 18 server connects (SSL_accept()) 2004.08.17 11:03:12 LOG7[28177:3062528944]: 10 server connects that finished 2004.08.17 11:03:12 LOG7[28177:3062528944]: 0 server renegotiatiations requested 2004.08.17 11:03:12 LOG7[28177:3062528944]: 2 session cache hits 2004.08.17 11:03:12 LOG7[28177:3062528944]: 0 session cache misses 2004.08.17 11:03:12 LOG7[28177:3062528944]: 6 session cache timeouts 2004.08.17 11:03:12 LOG6[28177:3062528944]: Negotiated ciphers: AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 2004.08.17 11:03:12 LOG7[28177:3062528944]: FD 8 in non-blocking mode 2004.08.17 11:03:12 LOG7[28177:3062528944]: 55555 connecting 192.168.20.76:4242 2004.08.17 11:03:12 LOG7[28177:3062528944]: remote connect #1: EINPROGRESS: retrying 2004.08.17 11:03:12 LOG7[28177:3062528944]: waitforsocket: FD=8, DIR=write 2004.08.17 11:03:12 LOG7[28177:3062528944]: waitforsocket: ok 2004.08.17 11:03:12 LOG7[28177:3062528944]: Remote FD=8 initialized 2004.08.17 11:03:12 LOG7[28177:3062528944]: Socket closed on read 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL alert (write): warning: close notify 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL write shutdown (output buffer empty) 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL alert (read): warning: close notify 2004.08.17 11:03:12 LOG7[28177:3062528944]: SSL closed on SSL_read 2004.08.17 11:03:12 LOG7[28177:3062528944]: Socket write shutdown (output buffer empty) 2004.08.17 11:03:12 LOG5[28177:3062528944]: Connection closed: 13 bytes sent to SSL, 110 bytes sent to socket 2004.08.17 11:03:12 LOG7[28177:3062528944]: 55555 finished (0 left) ------------------------------------------------------------------------------------------------------------------- My client stunnel.conf: cert=stunnel.pem client=yes debug=7 [55555] accept=localhost:55555 connect=192.168.20.76:55555 - eof - My server stunnel.conf: cert=stunnel.pem debug=7 output=stunnel.err [55555] accept=192.168.20.76:55555 connect=192.168.20.76:4242 - eof - -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

1 0

SSL Handshake problems
by markzero＠logik.ath.cx 16 Aug '04

16 Aug '04

I have a tunnel that forwards connections from syslog-ng on localhost to my loghost. Or rather, I don't. In the stunnel logs, I repeatedly get: 2004.08.16 21:28:30 LOG5[23452:1006768128]: syslogngs connected from 127.0.0.1:32479 2004.08.16 21:28:30 LOG7[23452:1006768128]: SSL state (accept): before/accept initialization 2004.08.16 21:28:30 LOG3[23452:1006768128]: SSL_accept: 140760FC: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol 2004.08.16 21:28:30 LOG7[23452:1006768128]: syslogngs finished (2 left) 2004.08.16 21:28:31 LOG7[23452:1006693376]: SSL socket closed on SSL_read 2004.08.16 21:28:31 LOG5[23452:1006693376]: Connection closed: 0 bytes sent to SSL, 0 bytes sent to socket 2004.08.16 21:28:31 LOG7[23452:1006693376]: syslogngs finished (1 left) 2004.08.16 21:30:01 LOG7[23452:1006763008]: waitforsocket: ok 2004.08.16 21:30:01 LOG3[23452:1006763008]: SSL_accept: 140760FC: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol 2004.08.16 21:30:01 LOG7[23452:1006763008]: syslogngs finished (0 left) ..yet connecting using: $ openssl s_client -connect localhost:5515 successfully connects to my loghost and prints the certificate details. Why on earth will s_client connect and not syslog-ng? Specific details: 192.168.1.6 syslog-ng -> localhost:5515 | stunnel <----------| | stunnel ----------> loghost:5514 loghost: 192.168.1.7 (hosts) ---> stunnel (192.168.1.7:5514) | syslog-ng (localhost:5515) I have now been trying to implement encrypted logging for a record time of three months now and so far every attempt has failed in some way or another. Can somebody please put an end to this adminstrative misery? (more verbose program output on request) mark

1 1

_GET_CLIENT_HELLO:unknown protocol
by markzero＠logik.ath.cx 16 Aug '04

16 Aug '04

Hi. I'm so close to having a working loghost, with stunnel encrypted connections. Not close enough however. I have syslog-ng setup to log to 127.0.0.1:5515 on all clients. The client config: [syslogngs] accept = 127.0.0.1:5515 connect = 192.168.1.7:5514 On the loghost, stunnel listens on *.5514 and forwards to connection to 127.0.0.1:5515 (which syslog-ng is listening on). (server config): [syslogngs] accept = 192.168.1.7:5514 connect = 127.0.0.1:5515 I'm making an assumption that the certificates are working, as I'm using (or attempting to use) both client and server authentication. Watching the stream with a packet sniffer shows absolutely no connections between the client and the loghost. Strings such as this appear in the stunnel.log repeatedly: 2004.08.16 20:42:26 LOG7[7690:1006693376]: syslogngs started 2004.08.16 20:42:26 LOG5[7690:1006693376]: syslogngs connected from 127.0.0.1:2956 2004.08.16 20:42:26 LOG7[7690:1006693376]: SSL state (accept): before/accept initialization 2004.08.16 20:42:26 LOG7[7690:1006693376]: waitforsocket: FD=13, DIR=read 2004.08.16 20:42:26 LOG7[7690:1006690304]: syslogngs accepted FD=14 from 127.0.0.1:24856 2004.08.16 20:42:26 LOG7[7690:1006690304]: FD 14 in non-blocking mode 2004.08.16 20:42:26 LOG7[7690:1006763008]: syslogngs started 2004.08.16 20:42:26 LOG5[7690:1006763008]: syslogngs connected from 127.0.0.1:24856 2004.08.16 20:42:26 LOG7[7690:1006763008]: SSL state (accept): before/accept initialization 2004.08.16 20:42:26 LOG7[7690:1006763008]: waitforsocket: FD=14, DIR=read 2004.08.16 20:42:26 LOG7[7690:1006763008]: waitforsocket: ok 2004.08.16 20:42:26 LOG3[7690:1006763008]: SSL_accept: 140760FC: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol 2004.08.16 20:42:26 LOG7[7690:1006763008]: syslogngs finished (1 left) 2004.08.16 20:47:26 LOG7[7690:1006693376]: waitforsocket: timeout 2004.08.16 20:47:26 LOG7[7690:1006693376]: syslogngs finished (0 left) Have I made some glaring error that I'm not aware of? thanks mark

1 0