stunnel-users

stunnel-users@stunnel.org

6 participants
3294 discussions

Fwd: Trying to minimize memory usage for a scenario where we have several long-lived HTTPS connections.
by Jeremy Frady 31 Oct '12

31 Oct '12

Hello all, Thanks for taking the time to read this. We're operating on a low spec system that can not be modified at this point. stunnel was introduced at the last minute, without consideration to resource requirements and now consumes enough ram to cause the kernel to issue OOM exceptions. So in short, we are trying to trade increased CPU usage for less memory usage and have tried setting “sessions” to 3600 to reduce memory pressure, but unfortunately it doesn't last. Our current solution is to cron a restart of stunnel on a regular basis, but would prefer to limit number of threads or number of cache entries or something else altogether similarly gentler. Thanks again for your consideration and assistance in this! Regards, Jeremy

1 0

6 processes + out of memory issues on CentOS 6 stunnel (4.29)
by Todd Rinaldo 31 Oct '12

31 Oct '12

I'm experimenting with using the stunnel that comes with CentOS 6 (4.29). I have a config file that is successfully being used on stunnel version 4.15 on the same host without any issues. My issues: 1. starting stunnel creates 6 processes. I assume this has something to do with libwrap, but I'm not finding much discussion about it by doing a search. I'm also assuming that the binaries are forking after load, so it's not a significant memory expense to do this due to COW. Is this correct? 2. I'm getting 't of memory' (no "ou" in the error) messages from syslog when I do more than one request via chrome to port 2087. The process indicated from the message points to the stunnel process that has ownership of the open ports. A single request to this port doesn't seem to spawn the issue. Can anyone suggest what might be causing this? Upgrading to a newer version of stunnel is possible, but I would prefer to keep the version Red Hat provides so they can be on the hook for CVE issues. My config file follows: ----- cert = /var/cpanel/ssl/cpanel/cpanel.pem chroot = /usr/local/cpanel/var/run/stunnel/ # PID is created inside chroot jail pid = /stunnel.pid setuid = cpanel setgid = cpanel # Service-level configuration [cpanelhttps] accept = 2083 connect = 2082 TIMEOUTclose = 0 [whmhttps] accept = 2087 connect = 2086 TIMEOUTclose = 0 [webmailhttps] accept = 2096 connect = 2095 TIMEOUTclose = 0

1 0

Re: [stunnel-users] Using stunnel to add https to a webserver that doesn't have ssl setup
by Michael Avanessian 30 Oct '12

30 Oct '12

Thanks for the quick reply! So... what http code do I use to break out the infinite loop so it loads only once? I think the other 2 circumstances may have something similar happening to them (which are forwarded using the web server instead). If I use the webserver to rewrite the URL, the web browser tries to do something (I can't tell what), then returns the error below: The page isn't redirecting properly Firefox has detected that the server is redirecting the request for this address in a way that will never complete. > Normally, I could do this a few different ways (provided my webserver > had ssl added to it natively in a normal way) 1. webserver URL Rewrite > plugin 2. webserver redirect plugin > 3: > > For whatever reason, I'm having all sorts of weird issues when > trying the three methods above if I use stunnel for ssl instead of > using the webserver's builtin ssl. Please note that traffic coming out of the stunnel looks - and actually *is* - just as port-80-ish to the actual webserver as native HTTP requests do, so unless you take special measures to break the loop, the webserver will try to (re-)redirect *that, too*. Regards, J. Bern --

2 1

Using stunnel to add https to a webserver that doesn't have ssl setup
by Michael Avanessian 30 Oct '12

30 Oct '12

Hi there. I appreciate that you guys are all helping each other out. I am brand new to stunnel. Currently, I'm using stunnel to add https to a webserver that doesn't have ssl setup; which works great. I prefer to do that instead of using the webserver's builtin ssl feature. CONFIGURATION: Stunnel.conf includes (which adds ssl to incoming http traffic on port 443) [https] accept = 443 connect = 80 Also, incoming http:80 traffic can also come in; which would bypass stunnel, and go directly to the webserver as http. OBJECTIVE: I am trying to make it so when someone visits: http://mywebsite.com (it forwards automatically to https://mywebsite.com). Normally, I could do this a few different ways (provided my webserver had ssl added to it natively in a normal way) 1. webserver URL Rewrite plugin 2. webserver redirect plugin 3: <meta http-equiv="refresh" content="0; url=https://mywebsite.com"> For whatever reason, I'm having all sorts of weird issues when trying the three methods above if I use stunnel for ssl instead of using the webserver's builtin ssl. The first two methods result in web browser redirect errors, the third method result in an infinite loop reloading the https website. Can someone please tell me what extra accommodation I need to make considering that using stunnel for https can complicate things. I'm using IIS 7.5 as my webserver. I've tried using the the URL rewrite 2.0 mod using the below rule (which works for normal builtin ssl support in the webserver: <rule name="Redirect to HTTPS" stopProcessing="true"> <match url="(.*)" /> <conditions><add input="{HTTPS}" pattern="^OFF$" /> </conditions> </rule> I have also tried the "http redirect" mod; which I can forward to any website except for the one I'm trying to do. Both take me to the https equivalent and give a redirect error. Could someone please be kind enough to tell me what I'm missing? Thanks!

2 1

How upgrade stunnel?
by magali morales 30 Oct '12

30 Oct '12

Hi!! I have installed the version 4.44 of stunnel, haproxy I am currently using 1.4.22. I need to update stunnel most recent version. How do I update stunnel to the latest version? And I want to know How do I uninstall stunnel? I hope you can help me, I thank you in advance!

7 7

TIMEOUTclose exceeded: closing
by Michael Wittig 25 Oct '12

25 Oct '12

Hi, I am using stunnes 4.54, my config looks like this: chroot = /opt/stunnel/jail/ setuid = stunnel setgid = stunnel pid = /stunnel.pid socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 syslog = yes debug = local1.warning fips = no [http] cert = /opt/stunnel/www.crt key = /opt/stunnel/www.key sslVersion = all options = NO_SSLv2 renegotiation = no accept = 192.168.72.10:443 connect = 192.168.71.10:80 TIMEOUTclose = 0 xforwardedfor = yes My log is full with: Oct 25 14:49:33 www stunnel: LOG3[15114:140668359968512]: transfer: s_poll_wait: TIMEOUTclose exceeded: closing Oct 25 14:49:36 www stunnel: LOG3[15114:140668360591104]: transfer: s_poll_wait: TIMEOUTclose exceeded: closing Oct 25 14:50:08 www stunnel: LOG3[15114:140668360812288]: transfer: s_poll_wait: TIMEOUTclose exceeded: closing Oct 25 14:50:13 www stunnel: LOG3[15114:140668360591104]: transfer: s_poll_wait: TIMEOUTclose exceeded: closing The doc suggests to "set to 0 for buggy MSIE" the mailing list tells me "You requested close timeout of 0 seconds and that's exactly what you get." But i still don't understand why this is an error and what can I do to get rid of it? Or is it okay to don't look for errors in the log? Regards, Michael

2 1

some version issue
by Sergey Pimenov 25 Oct '12

25 Oct '12

Hello, I have a little problem, working with stunnel. The problem is: 25 10:50:53 LOG3[2612:1972]: SSL_connect: 1408F10B: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number and the full log: 25 10:50:32 LOG7[2612:2988]: No limit detected for the number of clients 2012.10.25 10:50:32 LOG5[2612:2988]: stunnel 4.53 on x86-pc-mingw32-gnu platform 2012.10.25 10:50:32 LOG5[2612:2988]: Compiled/running with OpenSSL 0.9.8s-fips 4 Jan 2012 2012.10.25 10:50:32 LOG5[2612:2988]: Threading:WIN32 SSL:+ENGINE+OCSP+FIPS Auth:none Sockets:SELECT+IPv6 2012.10.25 10:50:32 LOG5[2612:2988]: Reading configuration from file stunnel.conf 2012.10.25 10:50:33 LOG5[2612:2988]: FIPS mode is enabled 2012.10.25 10:50:33 LOG7[2612:2988]: Compression not enabled 2012.10.25 10:50:33 LOG7[2612:2988]: PRNG seeded successfully 2012.10.25 10:50:33 LOG6[2612:2988]: Initializing service section [POS] 2012.10.25 10:50:33 LOG7[2612:2988]: Certificate: C:\Arcus2\SSL\pos3135pem.pem 2012.10.25 10:50:33 LOG7[2612:2988]: Certificate loaded 2012.10.25 10:50:33 LOG7[2612:2988]: Key file: C:\Arcus2\SSL\pos3135key.pem 2012.10.25 10:50:33 LOG7[2612:2988]: Private key loaded 2012.10.25 10:50:33 LOG7[2612:2988]: SSL options set: 0x00000004 2012.10.25 10:50:33 LOG5[2612:2988]: Configuration successful 2012.10.25 10:50:33 LOG7[2612:2988]: Service [POS] (FD=180) bound to 127.0.0.1:9021 2012.10.25 10:50:53 LOG7[2612:2988]: Service [POS] accepted (FD=260) from 127.0.0.1:3645 2012.10.25 10:50:53 LOG7[2612:2988]: Creating a new thread 2012.10.25 10:50:53 LOG7[2612:2988]: New thread created 2012.10.25 10:50:53 LOG7[2612:1972]: Service [POS] started 2012.10.25 10:50:53 LOG5[2612:1972]: Service [POS] accepted connection from 127.0.0.1:3645 2012.10.25 10:50:53 LOG6[2612:1972]: connect_blocking: connecting 217.69.205.63:9021 2012.10.25 10:50:53 LOG7[2612:1972]: connect_blocking: s_poll_wait 217.69.205.63:9021: waiting 10 seconds 2012.10.25 10:50:53 LOG5[2612:1972]: connect_blocking: connected 217.69.205.63:9021 2012.10.25 10:50:53 LOG5[2612:1972]: Service [POS] connected remote server from 213.156.128.147:3646 2012.10.25 10:50:53 LOG7[2612:1972]: Remote socket (FD=284) initialized 2012.10.25 10:50:53 LOG3[2612:1972]: SSL_connect: 1408F10B: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number 2012.10.25 10:50:53 LOG5[2612:1972]: Connection reset: 0 byte(s) sent to SSL, 0 byte(s) sent to socket 2012.10.25 10:50:53 LOG7[2612:1972]: Remote socket (FD=284) closed 2012.10.25 10:50:53 LOG7[2612:1972]: Local socket (FD=260) closed 2012.10.25 10:50:53 LOG7[2612:1972]: Service [POS] finished (0 left) my .conf file is: cert = C:\Arcus2\SSL\pos3135pem.pem key = C:\Arcus2\SSL\pos3135key.pem socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 CAfile = C:\Arcus2\SSL\cacert.pem debug = 7 output = stunnel.log [POS] client = yes accept = 127.0.0.1:9021 connect = xxx.xxx.xxx.xxx:9021 if I change conf file, adding sslVersion = all or sslVersion = SSLv3, I have another error Section POS: sslVersion = TLSv1 is required in FIPS mode Thank your for help, Sergey Pimenov

2 1

Stunnel 4.54 manifest
by John A. Wallace 24 Oct '12

24 Oct '12

Hi, Michal. Good news about the update! I noticed that this version, the one for Windows installation, has many more files in it than the last version. It's no problem, but I was just wondering why the change this time? Thanks. John > -----Original Message----- > From: stunnel-announce-bounces(a)stunnel.org [mailto:stunnel-announce- > bounces(a)stunnel.org] On Behalf Of stunnel-announce-request(a)stunnel.org > Sent: Wednesday, October 10, 2012 5:00 AM > To: stunnel-announce(a)stunnel.org > Subject: stunnel-announce Digest, Vol 48, Issue 1 > > Send stunnel-announce mailing list submissions to > stunnel-announce(a)stunnel.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-announce > or, via email, send a message with subject or body 'help' to > stunnel-announce-request(a)stunnel.org > > You can reach the person managing the list at > stunnel-announce-owner(a)stunnel.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of stunnel-announce digest..." > > > Today's Topics: > > 1. stunnel 4.54 released (Michal Trojnara) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 09 Oct 2012 23:37:41 +0200 > From: Michal Trojnara <Michal.Trojnara(a)mirt.net> > To: stunnel-users(a)stunnel.org, stunnel-announce(a)stunnel.org, > openssl-users(a)openssl.org > Subject: [stunnel-announce] stunnel 4.54 released > Message-ID: <50749925.8030905(a)mirt.net> > Content-Type: text/plain; charset="iso-8859-1" > > Dear Users, > > > I have released version 4.54 of stunnel. The ChangeLog entry: > > > Version 4.54, 2012.10.09, urgency: MEDIUM: > * New Win32 features > - FIPS module updated to version 2.0. > - OpenSSL DLLs updated to version 1.0.1c. > - zlib DLL updated to version 1.2.7. > - Engine DLLs added: 4758cca, aep, atalla, capi, chil, cswift, gmp, > gost, nuron, padlock, sureware, ubsec. > * Other new features > - "session" option renamed to more readable "sessionCacheTimeout". > The old name remains accepted for backward compatibility. > - New service-level "sessionCacheSize" option to control session cache > size. > - New service-level option "reset" to control whether TCP RST flag is > used to indicate errors. The default value is "reset = yes". > - New service-level option "renegotiation" to disable SSL > renegotiation. > This feature is based on a public-domain patch by Janusz Dziemidowicz. > - New FreeBSD socket options: IP_FREEBIND, IP_BINDANY, IPV6_BINDANY > (thx to Janusz Dziemidowicz). > - New parameters to configure TLS v1.1/v1.2 with OpenSSL version 1.0.1 > or higher (thx to Henrik Riomar). > * Bugfixes > - Fixed "Application Failed to Initialize Properly (0xc0150002)" error. > - Fixed missing SSL state debug log entries. > - Fixed a race condition in libwrap code resulting in random stalls > (thx to Andrew Skalski). > - Session cache purged at configuration file reload to reduce memory > leak. > Remaining leak of a few kilobytes per section is yet to be fixed. > - Fixed regression bug in "transparent = destination" functionality > (thx to Stefan Lauterbach). This bug was introduced in stunnel 4.51. > - "transparent = destination" is now a valid endpoint in inetd mode. > - "delay = yes" fixed to work even if specified *after* "connect" > option. > - Multiple "connect" targets fixed to also work with delayed resolver. > - The number of resolver retries of EAI_AGAIN error has been limited > to > 3 in order to prevent infinite loops.. > > > Home page: https://www.stunnel.org/ <http://stunnel.mirt.net/> > Download: https://www.stunnel.org/downloads.html > <ftp://stunnel.mirt.net/stunnel/> > > > SHA-256 hash for stunnel-4.54.tar.gz: > > b7e1b9e63569574dbdabee8af90b8ab88db3fe13dcb1268d59a1408c56e6de7b > > > Best regards, > > Mike > > > -------------- next part -------------- A non-text attachment was > scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 196 bytes > Desc: OpenPGP digital signature > URL: <http://www.stunnel.org/pipermail/stunnel- > announce/attachments/20121009/f9eac1e3/attachment-0001.pgp> > > ------------------------------ > > _______________________________________________ > stunnel-announce mailing list > stunnel-announce(a)stunnel.org > https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-announce > > > End of stunnel-announce Digest, Vol 48, Issue 1 > ***********************************************

3 6

Re: [stunnel-users] (no subject)
by John 23 Oct '12

23 Oct '12

wrote in message news:... Path: news.gmane.org!not-for-mail From: Leandro Avila <leandro.avila(a)ymail.com> Newsgroups: gmane.network.stunnel.user Subject: Re: Safest suggested client/server stunnel configurations to prevent MITM attacks Date: Mon, 22 Oct 2012 12:50:07 -0700 (PDT) Lines: 52 Approved: news(a)gmane.org Message-ID: <1350935407.72221.YahooMailNeo(a)web111004.mail.gq1.yahoo.com> References: <4B5D7F24543C2E4DB3172B1F82446E56C8473D31(a)CBMBOX1.cloudblock.com> Reply-To: Leandro Avila <leandro.avila(a)ymail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 X-Trace: ger.gmane.org 1350935423 5511 80.91.229.3 (22 Oct 2012 19:50:23 GMT) X-Complaints-To: usenet(a)ger.gmane.org NNTP-Posting-Date: Mon, 22 Oct 2012 19:50:23 +0000 (UTC) To: "Michael K. Avanessian" <michael(a)mka.net>, "stunnel-users(a)stunnel.org" <stunnel-users(a)stunnel.org> Original-X-From: stunnel-users-bounces(a)stunnel.org Mon Oct 22 21:50:30 2012 Return-path: <stunnel-users-bounces(a)stunnel.org> Envelope-to: gnsu-stunnel-users(a)m.gmane.org Original-Received: from linode.mirt.net ([207.192.69.165]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from <stunnel-users-bounces(a)stunnel.org>) id 1TQO15-0006Lq-PI for gnsu-stunnel-users(a)m.gmane.org; Mon, 22 Oct 2012 21:50:28 +0200 Original-Received: from linode.mirt.net (localhost [127.0.0.1]) by linode.mirt.net (Postfix) with ESMTP id E06E11C115; Mon, 22 Oct 2012 21:50:13 +0200 (CEST) X-Original-To: stunnel-users(a)stunnel.org Delivered-To: stunnel-users(a)stunnel.org Original-Received: from nm7-vm0.bullet.mail.ne1.yahoo.com (nm7-vm0.bullet.mail.ne1.yahoo.com [98.138.91.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by linode.mirt.net (Postfix) with ESMTPS id 2914F1C0F8 for <stunnel-users(a)stunnel.org>; Mon, 22 Oct 2012 21:50:09 +0200 (CEST) Original-Received: from [98.138.90.52] by nm7.bullet.mail.ne1.yahoo.com with NNFMP; 22 Oct 2012 19:50:08 -0000 Original-Received: from [98.138.89.195] by tm5.bullet.mail.ne1.yahoo.com with NNFMP; 22 Oct 2012 19:50:08 -0000 Original-Received: from [127.0.0.1] by omp1053.mail.ne1.yahoo.com with NNFMP; 22 Oct 2012 19:50:08 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 65068.27023.bm(a)omp1053.mail.ne1.yahoo.com Original-Received: (qmail 75038 invoked by uid 60001); 22 Oct 2012 19:50:07 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymail.com; s=s1024; t=1350935407; bh=0Y+VdggsIVZOwOr4EaEYksE57qG+K4Xf7m79PQuMl/4=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=uUP64Hu7MIb0ahLEqKeQ2rUov8flXv6sjA7h5DanB+bxl2m8dRHLsiUrFHiPFhWcsNIUGtevpvfsxYifmZPjIMTiOvHyxZPxQo2uXvlAzOZKwPuaNEvXrYVNiwVO0nZjG00eA+Gpo8dJCS50OObUbvjympoIhG60TioBD4rSw5U= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=ymail.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=wx17KKam+BlR2A3orpl30Y8/UU3T1ZQ5cDajNEkq008Ppz1baFHK10kwWYt35qPShDTswy2xduxRIzGN/JTVdE8Vb9hFmfmWPtOkptIRxMf26YV6r/x53AKs8rACXc8tNyJVeczxzNSAE1/iycwLc4Q5lwdUda4qUe8+09gtNa0=; X-YMail-OSG: b3DSDKgVM1mQHP5ZBTfIr3A5W2ZGXp385_N0YTtfmQmY8Tx PSFpP624fQl9zaJm1NcwnCvuFSUunTJ.Q6u_X6ZqnTdr.J_LYAj5IOqyykQ2 l4Al99RB4Au24agY5aySFUQj2AVKVLlThmnaaZKrM2O6i4lQj42kjXE9SjCN Ko1OE8i8SRI1X8s_OszQhSFqPwpJVxJ6a8XwsT.HHRvnjCN5oawxLfeYhi8I Nc497s5NZ3BjLmS2ddO1rE_aDEXfeZZf5G4FssKYeY.CR5XmhczPnRsqEOO0 nYj_KNi6UlLDyqhpRuMqUJYBD.JQXLJzN9IG3zKYBdvkip2LXSMmutoKPT8Z oEEAd3OEom9Rew5fODminUDtopQjgJUGkRl5fJPz2xthop6HA8XuKHCMTM6B d1YYbS_V1c5QklFH6aN6XbAYJRG36RA9gKBGsO2BVZ_5t36738Y3Bff.0ySt 6iW79amGPEIc__mjy0VELbOmQ3WPpHOPdBiH.GuHKGcmpVqApD5u2dHxOWa0 cJzYLcE0Fdfsdr6YOWGOh9jGD.P.St5QItI4sMxAhQ9WROechXtibFdHjrFO _Md3OgU8mIpgCFwIbK4b2K4cyPAiM5Kl1P_uFLQ5HE9uAg_8I64GtaSYyTGM 1aFaD9IVrniBqWo.oWvM2Lp.7TyGddU7.olqsc6MmSljcf4b.Rx5cRTwDw2R Kqc1fDQWPPxDDd1pMa1Nasg27P2qGUEy1DSofVwCgDn9MSKvSGj8- Original-Received: from [134.161.133.36] by web111004.mail.gq1.yahoo.com via HTTP; Mon, 22 Oct 2012 12:50:07 PDT X-Rocket-MIMEInfo: 001.001, Pl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gRnJvbTogTWljaGFlbCBLLiBBdmFuZXNzaWFuIDxtaWNoYWVsQG1rYS5uZXQ.Cj5UbzogInN0dW5uZWwtdXNlcnNAc3R1bm5lbC5vcmciIDxzdHVubmVsLXVzZXJzQHN0dW5uZWwub3JnPiAKPlNlbnQ6IEZyaWRheSwgT2N0b2JlciAxOSwgMjAxMiAxMDo0MSBQTQo.U3ViamVjdDogW3N0dW5uZWwtdXNlcnNdIFNhZmVzdCBzdWdnZXN0ZWQgY2xpZW50L3NlcnZlciBzdHVubmVsIGNvbmZpZ3VyYXRpb25zIHRvIHByZXZlbnQgTUlUTSBhdHRhY2tzCgoBMAEBAQE- X-Mailer: YahooMailWebService/0.8.123.460 In-Reply-To: <4B5D7F24543C2E4DB3172B1F82446E56C8473D31(a)CBMBOX1.cloudblock.com> X-BeenThere: stunnel-users(a)stunnel.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "public, moderate-volume list - general discussion, problem reports, patches" <stunnel-users.stunnel.org> List-Unsubscribe: <https://www.stunnel.org/cgi-bin/mailman/options/stunnel-users>, <mailto:stunnel-users-request@stunnel.org?subject=unsubscribe> List-Archive: <http://www.stunnel.org/pipermail/stunnel-users> List-Post: <mailto:stunnel-users@stunnel.org> List-Help: <mailto:stunnel-users-request@stunnel.org?subject=help> List-Subscribe: <https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users>, <mailto:stunnel-users-request@stunnel.org?subject=subscribe> Original-Sender: stunnel-users-bounces(a)stunnel.org Errors-To: stunnel-users-bounces(a)stunnel.org Xref: news.gmane.org gmane.network.stunnel.user:5976 Archived-At: <http://permalink.gmane.org/gmane.network.stunnel.user/5976> Pl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gRnJvbTogTWljaGFlbCBLLiBBdmFu ZXNzaWFuIDxtaWNoYWVsQG1rYS5uZXQ+Cj5UbzogInN0dW5uZWwtdXNlcnNAc3R1bm5lbC5vcmci IDxzdHVubmVsLXVzZXJzQHN0dW5uZWwub3JnPiAKPlNlbnQ6IEZyaWRheSwgT2N0b2JlciAxOSwg MjAxMiAxMDo0MSBQTQo+U3ViamVjdDogW3N0dW5uZWwtdXNlcnNdIFNhZmVzdCBzdWdnZXN0ZWQg Y2xpZW50L3NlcnZlciBzdHVubmVsIGNvbmZpZ3VyYXRpb25zIHRvIHByZXZlbnQgTUlUTSBhdHRh Y2tzCgo+SeKAmW0gY3VycmVudGx5IHR1bm5lbGluZyBTU0ggb3ZlciBTU0wgdXNpbmcgc3R1bm5l bC4KPkkgdGhvdWdodCB0aGF0IHN0dW5uZWxlZCBzc2ggZGF0YSB3YXMgc2FmZS7CoCBIb3dldmVy LCByZWNlbnRseSBJ4oCZdmUgcmVhZCB0aGF0IGlmIGdvaW5nIHRocm91Z2ggYSBzb3BoaXN0aWNh dGVkIGh0dHAvaHR0cHMgcHJveHksIGl04oCZcyBwb3NzaWJsZSB0byBiZSBoYWNrZWQgYnkgYSDi gJxsZWdpdGltYXRl4oCdIG1pdG0gYXR0YWNrIHRvIGZvb2wgYW4gU1NMIGNsaWVudC4KClR1bm5l bGVkIGFuZCBub3QtdHVubmVsZWQgU1NIIGRhdGEgX2lzXyBzYWZlLiBUaGUgU1NIIHByb3RvY29s IGlzIHByZXR0eSBzZWN1cmUgYnkgaXRzZWxmLsKgCgpNeSB1bmRlcnN0YW5kaW5nIGlzIHRoYXQg dG8gcHVsbCBvZmYgdGhlIHR5cGUgb2YgU1NML1RMUyBkYXRhIGluc3BlY3Rpb24gdGhhdCB5b3Ug bWVudGlvbgpodHRwOi8vd3d3LnNvdXJjZWZpcmUuY29tL3NlY3VyaXR5LXRlY2hub2xvZ2llcy9u ZXR3b3JrLXNlY3VyaXR5L3NzbC1lbmNyeXB0aW9uLWRlY3J5cHRpb24KCnRoZXJlIGhhcyB0byBi ZSBzb21lIHdvcmsgZG9uZSBvbiB0aGUgY2xpZW50IHNpZGUgb2YgdGhlIGNvbm5lY3Rpb24uIChJ bnN0YWxsIGEgY3VzdG9tCgpDQSBjZXJ0aWZpY2F0ZSBpbiB0aGUgdHJ1c3RlZCBjZXJ0aWZpY2F0 ZSBzdG9yZSBvZiB0aGUgY2xpZW50IG1hY2hpbmUpCgpTbyBldmVuIGlmIHlvdSB3ZXJlIG9uIHN1 Y2ggYSBuZXR3b3JrLCBhcyBsb25nIGFzIHlvdXIgImF0dGFja2VyIiBkb2VzIG5vdCBoYXZlIGNv bnRyb2wKb2YgeW91ciBtYWNoaW5lLiB0aGUgU1NML1RMUyBwcm90b2NvbCB3aWxsIHByb3RlY3Qg eW91IGJlY2F1c2Ugb2YgdGhlIHdheSBrZXlzIChjZXJ0aWZpY2F0ZXMpCmFyZSB2ZXJpZmllZC4g KE5vdGljZSB0aGUga2V5IHdvcmQgaGVyZSBpcyB2ZXJpZmllZCkKCj7CoAo+SXMgaXQgc3RpbGwg cG9zc2libGUgdG8gY29uZmlndXJlIHN0dW5uZWwgc28gdGhhdCBzc2wgY2Fu4oCZdCBiZSBjb21w cm9taXNlZCBiZXR3ZWVuIGJvdGggZW5kcz8KPsKgCj5J4oCZbSBnb2luZyB0byB0YWtlIGEgd2ls ZCBndWVzcyBoZXJlOyB3aGljaCBJ4oCZbSBzdXJlIEnigJltIHByb2JhYmx5IHdyb25nLsKgIEJ1 dCwgY291bGQgSSBqdXN0IGluc3RhbGwgc3R1bm5lbDsgYW5kLCBsZXQgaXQgY3JlYXRlIGF1dG9t YXRpY2FsbHkgYSBzZWxmLXNpZ25lZCAoc3R1bm5lbC5wZW0pIGNlcnRpZmljYXRlIGZpbGXigKYg dGhlbiBqdXN0IGNvcHkgdGhhdCBmaWxlIHRvIHRoZSBzdHVubmVsIGluc3RhbGwgb24gdGhlIG90 aGVyIGVuZD/CoCBUaGF0IHdheSBib3RoIHNpZGVzIGFyZSBhbHJlYWR5IGF3YXJlIG9mIGVhY2gg b3RoZXLigJlzIHB1YmxpYyBrZXlzOyBhbmQsIHdvdWxkbuKAmXQgYmUgdnVsbmVyYWJsZSBkdXJp bmcgdGhlIGluaXRpYWwgdW5lbmNyeXB0ZWQgaGFuZHNoYWtlPwo+wqAKPknigJltIHN1cmUgSeKA mW0gcHJvYmFibHkgd2F5IG9mZjsgYW5kLCB0aGVyZeKAmXMgbW9yZSBJIG5lZWQgdG8gZG8gaW4g c3R1bm5lbOKAmXMgY29uZmlndXJhdGlvbiB0byBmdXJ0aGVyIGVuc3VyZSB0aGUgU1NMIHdvbuKA mXQgYmUgY29tcHJvbWlzZWQuLiBzdWNoIGFzIHRoZSBzdHVubmVsIOKAnHZlcmlmeeKAnSBzZXR0 aW5nLsKgIEnigJltIG5vdCBzdXJlIHdoaWNoIHNldHRpbmcgdG8gaGF2ZSBpdDsgYW5kLCB3aGF0 IGl0IGFjdHVhbGx5IGRvZXMuCj7CoAo+SeKAmW0gaG9waW5nIHNvbWVvbmUgY291bGQgc2hlZCBz b21lIGxpZ2h0IG9uIHRoaXMgd2l0aCBzaW1wbGUgc3VnZ2VzdGVkIGNsaWVudMOgIHNlcnZlciBj b25maWdzIHRoYXQgd291bGQga2VlcCBzc2wgdW5jb21wcm9taXNlZCBhcyBtdWNoIGFzIHBvc3Np YmxlLgo+wqAKPlRoYW5rcyBpbiBhZHZhbmNlIQoKVGhlIGNvbmZpZ3VyYXRpb24geW91IGFyZSBs b29raW5nIGZvciBzdHVubmVsIGludm9sdmVzIHRoZSB2ZXJpZnkgbGV2ZWwgMyBzZXR0aW5nIG9u IHRoZSBjb25maWcKKFZlcmlmeSBwZWVyIHdpdGggbG9jYWxseSBpbnN0YWxsZWQgY2VydGlmaWNh dGUpCgpQbHVzIHRoZSBrZXkgbWFuYWdlbWVudCBpbnZvbHZlZCB0byBzZXQgdGhhdCB1cC4KClRh a2UgYSBsb29rIGEgdGhpcyBkb2N1bWVudC4gSXQgaXMgYSBsaXR0bGUgb3V0IG9mIGRhdGUuIEJV VCB0aGUgcGFydCBhYm91dCBzZXR0aW5nIHVwIHRoZQpjZXJ0aWZpY2F0ZXMgb24gY2xpZW50IGFu ZCBzZXJ2ZXIgc3RpbGwgYXBwbGllcy4gYW5kIGlzIGEgZ29vZCB3YXkgdG8gc3RhcnQKaHR0cDov L3d3dy5zeW1hbnRlYy5jb20vY29ubmVjdC9hcnRpY2xlcy9yZW1vdGUtZGVza3RvcC1tYW5hZ2Vt ZW50LXNvbHV0aW9uLW1pY3Jvc29mdAoKSG9wZSB0aGlzIGhlbHBzCgoKCkxlYW5kcm8gQXZpbGEK LS0tLS0tLS0tLS0tLS0tLQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fXwpzdHVubmVsLXVzZXJzIG1haWxpbmcgbGlzdApzdHVubmVsLXVzZXJzQHN0dW5uZWwu b3JnCmh0dHBzOi8vd3d3LnN0dW5uZWwub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9zdHVu bmVsLXVzZXJzCg== ------------------------ In the above data, I do not see any legible information at all. What am I missing?

2 1

Safest suggested client/server stunnel configurations to prevent MITM attacks
by Michael K. Avanessian 22 Oct '12

22 Oct '12

I'm currently tunneling SSH over SSL using stunnel. I thought that stunneled ssh data was safe. However, recently I've read that if going through a sophisticated http/https proxy, it's possible to be hacked by a "legitimate" mitm attack to fool an SSL client. Is it still possible to configure stunnel so that ssl can't be compromised between both ends? I'm going to take a wild guess here; which I'm sure I'm probably wrong. But, could I just install stunnel; and, let it create automatically a self-signed (stunnel.pem) certificate file... then just copy that file to the stunnel install on the other end? That way both sides are already aware of each other's public keys; and, wouldn't be vulnerable during the initial unencrypted handshake? I'm sure I'm probably way off; and, there's more I need to do in stunnel's configuration to further ensure the SSL won't be compromised.. such as the stunnel "verify" setting. I'm not sure which setting to have it; and, what it actually does. I'm hoping someone could shed some light on this with simple suggested client--> server configs that would keep ssl uncompromised as much as possible. Thanks in advance!

3 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

stunnel-users