- stunnel-users - stunnel.org

"stunnel -version"
by Felix E. Klee 30 Aug '10

30 Aug '10

I installed the official stunnel 4.33 binary on Windows XP/32. And, when I execute "stunnel -version", a popup window appears with the following message: --------------------------- stunnel 4.33 on Win32 (not configured) --------------------------- Stunnel server is down due to an error. You need to exit and correct the problem. Click OK to see the error log window. --------------------------- OK --------------------------- Shouldn't that just work? What may be the cause for the problem? Indeed, I didn't configure stunnel yet. But I also realized that when I change something - for example the log level - in "stunnel.conf", then this is ignored by "stunnel -version". After clicking "OK" to close the popup message, I get some more info, though meaningless to me: stunnel 4.33 on x86-pc-mingw32-gnu with OpenSSL 1.0.0 29 Mar 2010 Threading:WIN32 SSL:ENGINE Sockets:SELECT,IPv6 Global options debug = notice RNDbytes = 64 RNDoverwrite = yes service = stunnel taskbar = yes Service-level options cert = stunnel.pem ciphers = ALL:!aNULL:!eNULL:!SSLv2 session = 300 seconds stack = 65536 bytes sslVersion = SSLv3 for client, all for server TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds verify = none Server is down

2 4

Updated stunnel version in Debian experimental
by Rodrigo Gallardo 28 Aug '10

28 Aug '10

I have just uploaded stunnel 4.33 to Debian experimental. amd64 packages will be available for download as soon as the automated processing is done (6-12 hours). Other architectures will follow as the autobuilders get time in their queues for us. Aside from the updates in stunnel itself, the packaging has been updated somewhat. In particular, the start/stop scripts in /etc/init.d have grown shinny new options to take advantage of configuration file reloading and the log rotation config takes advantage of them to avoid the long standing issue of having to either live with ever-growing logs, or killing long lived connections when rotating. I would be very glad if you would test those new scripts and report any and all bugs. To Debian's BTS, of course, as none of them are at all the fault of our most excellent upstream ;) As much as I'd have liked to upload it to unstable, the distribution is now in freeze in preparation for the upcoming release, and thus uploading a completely new version of stunnel, together with the packaging changes I made would be completely unacceptable. I will upload this version, together with any bug fixes we collect, as soon as the release is over and sid is unfrozen again. Sadly, that means that the next Debian stable will release with 4.29. For that I am sorry, and I promise to make a backport of 4.33 available as soon as possible after the release. -- Rodrigo yes-I-have-been-remise-as-maintainer Gallardo

1 0

Is it possible for stunnel to reject client connections if the server end cannot connect?
by Martin van den Nieuwelaar 27 Aug '10

27 Aug '10

Hi all. I took a look (manually) through the last year of archives, but didn't find anything on this issue. The situation is as follows. Say we have two machines set up, ClientPC and ServerPC. On ClientPC I run stunnel accepting a connection on a local port and connecting to an stunnel port on ServerPC. On ServerPC I run stunnel accepting a connection on the local stunnel port and connecting to the 'encryption unaware' server on another port on the same ServerPC machine. OK, pretty simple stuff so far. The problem is, when I connect to ClientPC with the 'encryption unaware' client app. then I always get a successful connection, even if there is no server running on ServerPC. Of course once the client has a successful connection, it then performs a write(), and that fails with 'Connection reset by peer'. Really, since there is no server running on ServerPC, I want the connect() to stunnel on ClientPC to fail. Is there a way to do this? The alternative (which is a kludge), is to make the client 'stunnel aware' (yuk!), and to tell it whether it's connecting over stunnel on a per connection basis (yuk!). Then it can know whether it needs to look at the connect() or the write() to know whether the server is not running. Yuk! Or am I overlooking something simple? :-) -- R A Ward Ltd. | We take the privacy of our customers seriously. Christchurch | All sensitive E-Mail attachments MUST be encrypted. New Zealand

1 0

Problem with 2048 bits SSL sertificate with stunnel
by Georgi Georgiev 23 Aug '10

23 Aug '10

Hello to all, We get 2048 bits wildcard certificate for our domain *.domain.com .. And we are using thawte as Certificate Authority . So they send as two certificates .. One for SSL web and one intermediate certificate .. The stunnel configuration is : [https1] cert = /etc/stunnel/domain.crt CAfile = /etc/stunnel/domain.intermediate.crt key = /etc/stunnel/domain.key.nopass verify = 0 accept = x.x.x.x:443 connect = x.x.x.x:81 xforwardedfor=yes even I use verify = 0 some of our clients still complains that on some pages ( like blabla.domain.com ) server wants some of their private certificate to be send to the server !! and it's happens only with Internet Explorer 8.0 without verify and CAfile commands IE 8.0 works fine but Mozilla Firefox claim that can find CA be trusted ! wildcard certificate cannot be reissued with 1024 bits key . So is there some mistake in my configuration ? If not what can I do about it ? Thanks in advance .. P.S.: version of stunnel is 4.20 with XForwardedFor patch ..

2 1

stunnel and loading keys from hw devices
by Victor Wagner 20 Aug '10

20 Aug '10

Hello, all I've tried to use stunnel with keys on the hardware device, supported by OpenSSL engine and encountered some minor problems: 1. Under Unix systems stunnel doesn't provide UI_METHOD for ENGINE_load_private_key. It passes NULL there and engine complains that no user interface provided. On Unix in many cases default UI_METHOD provided by OpenSSL would do So, replacing line 302 in the ctx.c (line number are given for release 4.33) from uim=NULL ; to uim=UI_OpenSSL(); would significanly improve stunnel functionality. 2. OpenSSL UI objects have two methods to pass arbitraty pointers along 1. generic ex_data based macros UI_set_app_data/UI_get_app_data 2. UI-specific UI_add_user_data/UI_get0_user_data Unfortunately app-specific pointer is set inside engine and retrieved inside a callback, which belongs to application. So author of an engine and author of an application should somehow agree on which metod to use. All engines shipped with OpenSSL (ones which do provide load_private_key method) use UI_add_user_data to pass data to the callback. stunnel's pin_cb (for Win32 version of stunnel in the gui.c) uses UI_get_app_data to retrieve ui_data. I wonder what engine was used when this code was developed and debugged. And it does no check if any meaningful pointer is obtained. I suggest to add following code after line 602 in gui.c: /* if set_app_Data haven't-return anything */ if (!ui_data) ui_data=UI_get0_user_data(ui); /* if still no avail */ if (!ui_data) { s_log(LOG_ERR,"Engine haven't passed our callback data to callback. Sorry!"); return 0; } Or instead of complaining we can use some structure, local to function pin_cb as fallback UI_DATA - just as password buffer, and check if ui_data->section is not NULL before reading ui_data->section->key in the pass_proc (line 543 of gui.c) Thus it would work even with really broken engines which do not pass userdata from ENGINE_load_private_key to UI callbacks at all. ----- End forwarded message -----

2 1

stunnel and mod_gnutls
by Yclept Nemo 15 Aug '10

15 Aug '10

I run a mod_gnutls (0.5.5)<->apache (2.2.8) webserver which behaves perfectly normally outside of stunnel: GnuTLSEnable on GnuTLSPriorities SECURE256 GnuTLSExportCertificates on .. When a connection is closed and apache signals the mod_gnutls process to quit, the log records: GnuTLS: Handshake Failed (-8) 'A record packet with illegal version was received.' Invalid method in request NS * HTTP/1.0 ::1 - - [15/Aug/2010:03:31:26 -0400] "NS * HTTP/1.0" 501 512 "-" "Apache/2.2.8 (Ubuntu) ... (internal dummy connection)" This lets me easily identify apache2 process turnovers However, when I connect to this server through stunnel, I receive random dropouts. For example, if I were to upload 200 test files to this server, on average 15 transfers would fail. Stunnel logs (excerpt): 2010.08.15 04:11:25 LOG5[29287:3074030448]: Connection reset: 94 bytes sent to SSL, 523 bytes sent to socket 2010.08.15 04:12:21 LOG5[29287:3074448240]: Connection reset: 94 bytes sent to SSL, 523 bytes sent to socket 2010.08.15 04:12:34 LOG5[29287:3074030448]: Connection reset: 94 bytes sent to SSL, 523 bytes sent to socket And my apache2 logs are flooded with: Invalid method in request \x16\x03\x01 # ... over and over and over ... Invalid method in request \x16\x03\x01 # ... this is a tls hello sequence, as though the webserver were not running mod_gnutls ::1 - - [15/Aug/2010:03:31:26 -0400] "NS * HTTP/1.0" 501 512 "-" "Apache/2.2.8 (Ubuntu) ... (internal dummy connection)" The apache logs show new apache2 processes / new ssl connections being created every 2-5 seconds. A normal connections lasts much longer. stunnel configuration debug=7 foreground=yes client=yes syslog=no pid=/absolute/path/to/stunnel.pid libwrap=no [https] accept=127.0.0.1:11111 connect=my.website.net:myport sslVersion=TLSv1 an excerpt from the stunnel log: 2010.08.15 04:11:25 LOG6[29287:3074030448]: SSL connected: previous session reused 2010.08.15 04:11:25 LOG7[29287:3073960816]: Service https started 2010.08.15 04:11:25 LOG7[29287:3073960816]: FD=19 in non-blocking mode 2010.08.15 04:11:25 LOG5[29287:3073960816]: Service https accepted connection from 127.0.0.1:52674 2010.08.15 04:11:25 LOG7[29287:3073960816]: FD=20 in non-blocking mode 2010.08.15 04:11:25 LOG6[29287:3073960816]: connect_blocking: connecting 44.205.51.83:12389 2010.08.15 04:11:25 LOG7[29287:3073960816]: connect_blocking: s_poll_wait 44.205.51.83:12389: waiting 10 seconds 2010.08.15 04:11:25 LOG5[29287:3073960816]: connect_blocking: connected 44.205.51.83:12389 2010.08.15 04:11:25 LOG5[29287:3073960816]: Service https connected remote server from 192.168.1.8:51590 2010.08.15 04:11:25 LOG7[29287:3073960816]: Remote FD=20 initialized 2010.08.15 04:11:25 LOG7[29287:3073960816]: SSL state (connect): before/connect initialization 2010.08.15 04:11:25 LOG7[29287:3073960816]: SSL state (connect): SSLv3 write client hello A 2010.08.15 04:11:25 LOG7[29287:3073960816]: SSL state (connect): SSLv3 read server hello A 2010.08.15 04:11:25 LOG7[29287:3073960816]: SSL state (connect): SSLv3 read finished A 2010.08.15 04:11:25 LOG7[29287:3073960816]: SSL state (connect): SSLv3 write change cipher spec A 2010.08.15 04:11:25 LOG7[29287:3073960816]: SSL state (connect): SSLv3 write finished A 2010.08.15 04:11:25 LOG7[29287:3073960816]: SSL state (connect): SSLv3 flush data 2010.08.15 04:11:25 LOG7[29287:3073960816]: 1 items in the session cache 2010.08.15 04:11:25 LOG7[29287:3073960816]: 42 client connects (SSL_connect()) 2010.08.15 04:11:25 LOG7[29287:3073960816]: 42 client connects that finished 2010.08.15 04:11:25 LOG7[29287:3073960816]: 0 client renegotiations requested 2010.08.15 04:11:25 LOG7[29287:3073960816]: 0 server connects (SSL_accept()) 2010.08.15 04:11:25 LOG7[29287:3073960816]: 0 server connects that finished 2010.08.15 04:11:25 LOG7[29287:3073960816]: 0 server renegotiations requested 2010.08.15 04:11:25 LOG7[29287:3073960816]: 41 session cache hits 2010.08.15 04:11:25 LOG7[29287:3073960816]: 0 external session cache hits 2010.08.15 04:11:25 LOG7[29287:3073960816]: 0 session cache misses 2010.08.15 04:11:25 LOG7[29287:3073960816]: 0 session cache timeouts 2010.08.15 04:11:25 LOG6[29287:3073960816]: SSL connected: previous session reused 2010.08.15 04:11:25 LOG3[29287:3074030448]: SSL socket closed on SSL_read with 7 byte(s) in buffer 2010.08.15 04:11:25 LOG5[29287:3074030448]: Connection reset: 94 bytes sent to SSL, 523 bytes sent to socket 2010.08.15 04:11:25 LOG7[29287:3074030448]: Service https finished (4 left) 2010.08.15 04:11:25 LOG7[29287:3073960816]: SSL socket closed on SSL_read 2010.08.15 04:11:25 LOG7[29287:3073960816]: Socket write shutdown 2010.08.15 04:11:25 LOG5[29287:3073960816]: Connection closed: 94 bytes sent to SSL, 523 bytes sent to socket 2010.08.15 04:11:25 LOG7[29287:3073960816]: Service https finished (3 left) 2010.08.15 04:11:26 LOG7[29287:3074448240]: SSL socket closed on SSL_read 2010.08.15 04:11:26 LOG7[29287:3074448240]: Socket write shutdown 2010.08.15 04:11:26 LOG5[29287:3074448240]: Connection closed: 1110 bytes sent to SSL, 77962 bytes sent to socket 2010.08.15 04:11:26 LOG7[29287:3074517872]: SSL socket closed on SSL_read 2010.08.15 04:11:26 LOG7[29287:3074517872]: Socket write shutdown 2010.08.15 04:11:26 LOG7[29287:3074448240]: Service https finished (2 left) 2010.08.15 04:11:26 LOG5[29287:3074517872]: Connection closed: 575 bytes sent to SSL, 4889 bytes sent to socket 2010.08.15 04:11:26 LOG7[29287:3074517872]: Service https finished (1 left) 2010.08.15 04:11:26 LOG7[29287:3074378608]: SSL socket closed on SSL_read 2010.08.15 04:11:26 LOG7[29287:3074378608]: Socket write shutdown 2010.08.15 04:11:26 LOG5[29287:3074378608]: Connection closed: 573 bytes sent to SSL, 48787 bytes sent to socket 2010.08.15 04:11:26 LOG7[29287:3074378608]: Service https finished (0 left) 2010.08.15 04:11:26 LOG7[29287:3074520768]: Service https accepted FD=11 from 127.0.0.1:52676 2010.08.15 04:11:26 LOG7[29287:3074378608]: Service https started 2010.08.15 04:11:26 LOG7[29287:3074378608]: FD=11 in non-blocking mode 2010.08.15 04:11:26 LOG5[29287:3074378608]: Service https accepted connection from 127.0.0.1:52676 2010.08.15 04:11:26 LOG7[29287:3074378608]: FD=12 in non-blocking mode 2010.08.15 04:11:26 LOG6[29287:3074378608]: connect_blocking: connecting 44.205.51.83:12389 2010.08.15 04:11:26 LOG7[29287:3074378608]: connect_blocking: s_poll_wait 44.205.51.83:12389: waiting 10 seconds 2010.08.15 04:11:26 LOG5[29287:3074378608]: connect_blocking: connected 44.205.51.83:12389 2010.08.15 04:11:26 LOG5[29287:3074378608]: Service https connected remote server from 192.168.1.8:51592 2010.08.15 04:11:26 LOG7[29287:3074378608]: Remote FD=12 initialized 2010.08.15 04:11:26 LOG7[29287:3074378608]: SSL state (connect): before/connect initialization 2010.08.15 04:11:26 LOG7[29287:3074378608]: SSL state (connect): SSLv3 write client hello A 2010.08.15 04:11:26 LOG7[29287:3074378608]: SSL state (connect): SSLv3 read server hello A 2010.08.15 04:11:26 LOG7[29287:3074378608]: SSL state (connect): SSLv3 read finished A 2010.08.15 04:11:26 LOG7[29287:3074378608]: SSL state (connect): SSLv3 write change cipher spec A 2010.08.15 04:11:26 LOG7[29287:3074378608]: SSL state (connect): SSLv3 write finished A 2010.08.15 04:11:26 LOG7[29287:3074378608]: SSL state (connect): SSLv3 flush data My questions are: Why does this happen (why only with stunnel), and how can I prevent/avoid this? Sincerely,

2 2

help - SSL bandwidth overhead with using different ciphers
by Slim Ben Mahmoud 30 Jul '10

30 Jul '10

Dear SSL experts, In order to assess the performances of an adaptive security algorithm using SSL, I need to measure the network overhead induced by the establishment of SSL tunnels. The experiment aims to measure the bandwidth consumptions (or throughputs) when SSL tunnels are established using the different ciphers implemented in Stunnel (AES256-SHA or RC4-SHA for instance). Do you think that I have to expect a different throughput when I use different ciphers for every tunnels or the overhead is the pretty much the same? In fact, the first results show no difference between the throughputs no matter the cipher I use. I know that SSL overhead is traditionally measured in delay or latency because of the handshake phase (the encryption process time is negligible on the new CPUs) but this is not what i want to show. I hope that my request is enough clear, let me know if it is not the case. Best regards. --Slim

2 1

Proxy for content filtering
by Raj 29 Jul '10

29 Jul '10

Hi All I want to build a proxy server, which acts as man in the middle proxy. The main intention of application is to do content filtering, whether it is an http or https request. I want to block some specified URL. Can anybody tell me what is the best approach of doing this Thanks, Raj Rajmohan SK

1 0

Re: [stunnel-users] stunnel-users Digest, Vol 72, Issue 2
by TONY WESTENHOFER 07 Jul '10

07 Jul '10

stunnel-users-request(a)mirt.net wrote: >Send stunnel-users mailing list submissions to > stunnel-users(a)mirt.net > >To subscribe or unsubscribe via the World Wide Web, visit > http://stunnel.mirt.net/mailman/listinfo/stunnel-users >or, via email, send a message with subject or body 'help' to > stunnel-users-request(a)mirt.net > >You can reach the person managing the list at > stunnel-users-owner(a)mirt.net > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of stunnel-users digest..." > > >Today's Topics: > > 1. Re: telnetd and tcp_wrappers (Spence, Thomas Civ 844 CS/SCOX) > 2. change openssl version with configure (Bhavna Jhunjhunwala) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Tue, 6 Jul 2010 08:28:11 -0400 >From: "Spence, Thomas Civ 844 CS/SCOX" <Thomas.Spence(a)pentagon.af.mil> >Subject: Re: [stunnel-users] telnetd and tcp_wrappers >To: "stunnel-users(a)mirt.net" <stunnel-users(a)mirt.net> >Message-ID: > <751B1F405F4AFF4D907BD567538A83FB04FFE0B6DA(a)tequilasunrise.pentagon.ncr.ds.af.mil> > >Content-Type: text/plain; charset="us-ascii" > >2 guys did help me and still no luck... > >Anyone who tried this: > >[tssl] >accept = 992 >exec = /usr/sbin/telnetd > >Let me know... Reason why I am asking you because when I log off the server then stunnel's process stopped running but I want it keep running after logoff. Before I changed 'exec = /usr/sbin/telnetd', it was 'connect = 23' and the stunnel's process ran great and never stop running... Strange. > >I really need your help. Thanks. > >--------------- >Tom Spence >ABIDES SYSTEM SUPPORT >844th CS/SCOX > > > >------------------------------ > >Message: 2 >Date: Tue, 6 Jul 2010 17:41:42 -0400 >From: Bhavna Jhunjhunwala <bhavnaj(a)quantitativebrokers.com> >Subject: [stunnel-users] change openssl version with configure >To: stunnel-users(a)mirt.net >Message-ID: > <AANLkTikGWuO2XbF8-rtOTMyfeHVdeUV8TZGJvmYfKekB(a)mail.gmail.com> >Content-Type: text/plain; charset="iso-8859-1" > >Hi, > >I have stunnel version as below installed on Mac: > >s*tunnel 4.33 on i386-apple-darwin10.2.0 with OpenSSL 0.9.8k 25 Mar 2009* >*Threading:PTHREAD SSL:ENGINE Sockets:SELECT,IPv6 Auth:LIBWRAP* >* * >*Global options* >*debug = daemon.notice* >*pid = /usr/local/var/run/stunnel/stunnel.pid* >*RNDbytes = 64* >*RNDfile = /dev/urandom* >*RNDoverwrite = yes* >* * >*Service-level options* >*cert = /usr/local/etc/stunnel/stunnel.pem* >*ciphers = ALL:!aNULL:!eNULL:!SSLv2* >*session = 300 seconds* >*stack = 65536 bytes* >*sslVersion = SSLv3 for client, all for server* >*TIMEOUTbusy = 300 seconds* >*TIMEOUTclose = 60 seconds* >*TIMEOUTconnect = 10 seconds* >*TIMEOUTidle = 43200 seconds* >*verify = none* > >I would like to upgrade the openssl version to 1.0.0a, so I do >./configure --with-ssl=dir >make >make install > >After make install i get below error: > >*make install* >*Making install in src* >*test -z "/usr/local/bin" || ../auto/install-sh -c -d "/usr/local/bin"* >* /bin/sh ../libtool --mode=install /usr/bin/install -c 'stunnel' >'/usr/local/bin/stunnel'* >*/usr/bin/install -c stunnel /usr/local/bin/stunnel* >*test -z "/usr/local/bin" || ../auto/install-sh -c -d "/usr/local/bin"* >* /usr/bin/install -c 'stunnel3' '/usr/local/bin/stunnel3'* >*test -z "/usr/local/lib/stunnel" || ../auto/install-sh -c -d >"/usr/local/lib/stunnel"* >* /bin/sh ../libtool --mode=install /usr/bin/install -c 'libstunnel.la' >'/usr/local/lib/stunnel/libstunnel.la'* >*/usr/bin/install -c .libs/libstunnel.dylib >/usr/local/lib/stunnel/libstunnel.dylib* >*/usr/bin/install -c .libs/libstunnel.lai /usr/local/lib/stunnel/ >libstunnel.la* >*----------------------------------------------------------------------* >*Libraries have been installed in:* >* /usr/local/lib/stunnel* >* >* >*If you ever happen to want to link against installed libraries* >*in a given directory, LIBDIR, you must either use libtool, and* >*specify the full pathname of the library, or use the `-LLIBDIR'* >*flag during linking and do at least one of the following:* >* - add LIBDIR to the `DYLD_LIBRARY_PATH' environment variable* >* during execution* >* >* >*See any operating system documentation about shared libraries for* >*more information, such as the ld(1) and ld.so(8) manual pages.* >*----------------------------------------------------------------------* >*make[2]: Nothing to be done for `install-data-am'.* >*Making install in doc* >*make[2]: Nothing to be done for `install-exec-am'.* >*test -z "/usr/local/share/doc/stunnel" || ../auto/install-sh -c -d >"/usr/local/share/doc/stunnel"* >* /usr/bin/install -c -m 644 'stunnel.html' >'/usr/local/share/doc/stunnel/stunnel.html'* >* /usr/bin/install -c -m 644 'stunnel.pl.html' >'/usr/local/share/doc/stunnel/stunnel.pl.html'* >* /usr/bin/install -c -m 644 'stunnel.fr.html' >'/usr/local/share/doc/stunnel/stunnel.fr.html'* >*test -z "/usr/local/share/man/man8" || ../auto/install-sh -c -d >"/usr/local/share/man/man8"* >*mkdir: /usr/local/share/man/man8: Permission denied* >*make[2]: *** [install-man8] Error 1* >*make[1]: *** [install-am] Error 2* > > > >and when I check the stunnel version it still uses the old ssl version. >Am I doing something wrong here? > >-- >Thanks, >Bhavna >Quantitative Brokers >646 293 1808 > > >DISCLAIMER: >This e-mail and any attachments are for the confidential use of the >intended recipient. If you are not the intended recipient of this >message you are hereby notified that any review, dissemination, >distribution or copying of this message is strictly prohibited. This >communication is for information purposes only and should not be >regarded as an offer to sell or as a solicitation of an offer to buy >any investment product, an official confirmation of any transaction >or an official statement of Quantitative Brokers, LLC. > >E-mail transmissions cannot be guaranteed to be secure or error-free. >Therefore, we do not represent that this information is complete or >accurate and it should not be relied upon as such. > >All information is subject to change without notice. >Quantitative Brokers may, at its discretion, monitor and review the >content of all e-mail communications. >

1 0

problem with "verify=0"
by wujot＠home.pl 07 Jul '10

07 Jul '10

Hello everybody, The basic SSL negotiation requires the exchange of nine SSL messages. If client authentication is required, server can send additional message "certificate request". But this message is optional. I'm using stunnel ver. 4.27 for Win and 4.28 for Linux. In both cases stunnel, working as server, is sending "certificate request" message to the client, regardless of "verify" state, even with "verify=0". When "verify=0", server doesn't care about client's certificate. So, what for server sends this message? The part of my configuration and log is bellow: [test] accept = 60000 connect = 192.168.3.15:4679 client = no ;verify = 0 verify = none ciphers=DES-CBC3-SHA session = 3600 2010.07.07 12:53:35 LOG7[2412:4280]: SSL state (accept): before/accept initialization 2010.07.07 12:53:35 LOG7[2412:4280]: SSL state (accept): SSLv3 read client hello A 2010.07.07 12:53:35 LOG7[2412:4280]: SSL state (accept): SSLv3 write server hello A 2010.07.07 12:53:35 LOG7[2412:4280]: SSL state (accept): SSLv3 write certificate A 2010.07.07 12:53:35 LOG7[2412:4280]: SSL state (accept): SSLv3 write certificate request A <-------------???!!! 2010.07.07 12:53:35 LOG7[2412:4280]: SSL state (accept): SSLv3 flush data 2010.07.07 12:53:42 LOG6[2412:4280]: VERIFY IGNORE: depth=1, /C= .............. 2010.07.07 12:53:42 LOG5[2412:4280]: CRL: verification passed 2010.07.07 12:53:42 LOG5[2412:4280]: VERIFY OK: depth=1, /C= .......... 2010.07.07 12:53:42 LOG6[2412:4280]: VERIFY IGNORE: depth=0, /C= ................ 2010.07.07 12:53:42 LOG5[2412:4280]: CRL: verification passed 2010.07.07 12:53:42 LOG5[2412:4280]: VERIFY OK: depth=0, /C= .......................... 2010.07.07 12:53:42 LOG7[2412:4280]: SSL state (accept): SSLv3 read client certificate A 2010.07.07 12:53:42 LOG7[2412:4280]: SSL state (accept): SSLv3 read client key exchange a 2010.07.07 12:53:42 LOG7[2412:4280]: SSL state (accept): SSLv3 read certificate verify A 2010.07.07 12:53:42 LOG7[2412:4280]: SSL state (accept): SSLv3 read finished A 2010.07.07 12:53:42 LOG7[2412:4280]: SSL state (accept): SSLv3 write change cipher spec A 2010.07.07 12:53:42 LOG7[2412:4280]: SSL state (accept): SSLv3 write finished A So, my question is: how to remove "certificate request" message from stunnel-as-server negotiation? Regards, Wojtek

1 0