stunnel-users

5 participants
3312 discussions

How to configure Stunnel for ICMP packets?
by Rutger Thomschitz 08 Nov '04

08 Nov '04

Dear group, I have just started using Stunnel 4.04 with OpenSSL. This may seem a bit strange, but, I would like to configure Stunnel such that it will encrypt all my Ping packets. The reason in a nut shell is that I would like to use Ping to determine the network overhead added by SSL, as part of my research. How can I set up stunnel (i.e. stunnel.conf) to tunnel all ICMP (i.e. Ping) packets? Thank you very much in advance. I look forward to any replies. Sincerely, Rutger olds76(a)email.com -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm

2 1

(no subject)
by isidore11 07 Nov '04

07 Nov '04

1 0

RE: [stunnel-users] UDP End-points
by Les Niles 06 Nov '04

06 Nov '04

Pardon my ignorance, but why not run PPP over stunnel and then UDP over that? No new encapsulation to invent. Performance would be lousy, so it would be stupid to use for some streaming media protocol, but for low-bandwidth UDP-based protocols like NTP, DNS, RADIUS, etc. it might well be useful. -les -----Original Message----- From: stunnel-users-bounces(a)mirt.net On Behalf Of Michal Trojnara Subject: Re: [stunnel-users] UDP End-points Leigh, > Perhaps I wasn't quite as clear as I intended.. :) > I'm not suggesting that SSL over UDP should be done.. I'm suggesting > that stunnel could potentially act as a UDP-over-encrypted-TCP > gateway. Okay. Now I understand your idea (I hope). I would have to design a propriatary datagram-over-byte-stream (DOBS) protocol (at least length of UDP packets has to be encoded aside from the content), and then tunnel UDP over DOBS over SSL over TCP. This is why I don't like it: 1. Such tunneling is not very effective. There's a *huge* protocol overhead. 2. It's not standard. One of the main ideas behind stunnel is its interoperability. 3. I think it's much easier to write such encrypting UDP forwarder from scratch using IPSec-style datagram protocol, than to modify stunnel. 4. It breaks my KISS principle. 8-) In fact I would really like to find a time (or a sponsor) to develop such UDP encrypting forwarder. BTW: Maybe it's better to use IPSec or VTUN instead of a proxy? Best regards, Mike

2 1

Stunnel not working with Qmail
by Paul Swainson 06 Nov '04

06 Nov '04

Hi to all list members, I will try to as descriptive as possible about the problem. I have a qmail install and I had used courier for imap, imapssl & pop3dssl. I wanted to implement smtp ssl. I have gone through the stuff at stunnel.org but I don't think its my qmail config that's the problem. This is the first time I have used stunnel, I compiled no probs and before doing so I installed open ssl 0.9.7e I have created a conf for stunnel and here it is: Cat /usr/local/etc/stunnel/smtpsd.conf cert = /usr/local/etc/stunnel/stunnel.pem exec = /var/qmail/bin/qmail-smtpd #******** execargs = /var/qmail/bin/qmail-smtpd mydomain.com /home/vpopmail/bin/vchkpw /usr/bin/true 2>&1 #******** client = yes foreground = yes in the qmail run (smtpsd) script I have amended it to read #!/bin/sh QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue.pl" export QMAILQUEUE QMAILDUID=`id -u vpopmail` NOFILESGID=`id -g vpopmail` MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` LOCAL=`head -1 /var/qmail/control/me` if [ -z "$QMAILDUID" -o -z "$NOFILESGID" -o -z "$MAXSMTPD" -o -z "$LOCAL" ]; then echo QMAILDUID, NOFILESGID, MAXSMTPD, or LOCAL is unset in echo /var/qmail/supervise/qmail-smtpd/run exit 1 fi if [ ! -f /var/qmail/control/rcpthosts ]; then echo "No /var/qmail/control/rcpthosts!" echo "Refusing to start SMTP listener because it'll create an open relay" exit 1 fi exec /usr/local/bin/softlimit -m 40000000 \ /usr/local/bin/tcpserver -v -R -l "$LOCAL" -x /etc/tcp.smtp.cdb -c "$MAXSMTPD" \ -u "$QMAILDUID" -g "$NOFILESGID" 0 465 \ #********* /usr/local/sbin/stunnel /usr/local/etc/stunnel/smtpsd.conf #********* Execargs has in the stunnel conf is the line from smtpd run script, when it runs I don't have any output to the log so I can only assume stunnel is dying before it starts the session. Has anyone got this working? I know that it can but a lot of examples are for pop3ds. If I type stunnel /usr/local/etc/stunnel/smtpsd.conf I get the following error: Unable to open "/dev/cryptonet" Any help on this would be much appreciated, Thanks Regards Paul Swainson

2 1

compressed stunnel?
by jonathan.wilson 06 Nov '04

06 Nov '04

Hi all, I found some references to compression options in openssl.org - specifically to the SSL_COMP_add_compression_method() routine. Is there any way to invoke/use this from stunnel? Thanks, Jonathan Wilson

2 1

Re: stunnel consumes 99% cpu at HPUX
by Gavin Ho 06 Nov '04

06 Nov '04

Mike, thanks for your information. Each of our HPUX machines has 2 CPUs. Actually, before post my problem on this mailing list, I tried to search on Google but can't find any hints to solve the problem. Then I tried to browse the stunnel 4.0.5 source code and can't find any hints too. But I noticed that someone said on some historical newsgroup postings the problem may be related to openssl. Do you think thats true? I will wait for the version 4.0.6 and hope it can solve my problem. Cheers, Gavin -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm

2 1

stunnel consumes 99% cpu at HPUX
by gykho＠ogcio.gov.hk 04 Nov '04

04 Nov '04

Hi All, We set up stunnel from two linux machines located at DMZ to a HPUX cluster located at Private Zone. There is firewall in between. We use stunnel to encrypt Tomcat AJP traffic from apache web servers on linux machines to JBoss app server a HPUX cluster. The stunnel run at HPUX cluster was started as deamon mode and listened on a cluster failover IP instead of host IP. We found that the stunnel process at HPUX cluster consumed 99% CPU after run for a few days (started at Oct 26 10:26 and it was reported 99% CPU at Oct 29 23:00, under a very low traffic. Can anyone help? The debug log at HPUX is also attached, as shown in the log there was no requeset on Oct29 but the CPU still shot up to 99%. Cheers, Gavin Output of "stunnel -version" from Linux side ================================== stunnel 4.04 on i386-redhat-linux-gnu PTHREAD+LIBWRAP with OpenSSL 0.9.7a Feb 19 2003 Global options cert = /etc/stunnel/stunnel.pem ciphers = ALL:!ADH:+RC4:@STRENGTH debug = 5 key = /etc/stunnel/stunnel.pem pid = /var/run/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes session = 300 seconds verify = none Service-level options TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTidle = 43200 seconds Output of "uanme -a" from Linux side =========================== Linux www12-id.spica.hksarg 2.4.21-15.ELsmp #1 SMP Thu Apr 22 00:18:24 EDT 2004 i686 i686 i386 GNU/Linux Output of "gcc -v" from Linux side ======================== Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-39) Output of "openssl version" from Linux side =============================== OpenSSL 0.9.7a Feb 19 2003 "stunnel conf" at Linux side ================== chroot = /u01/var/run/stunnel # PID is created inside chroot jail pid = /deptstunnel.pid setuid = nobody setgid = nobody socket=r:SO_KEEPALIVE=1 # Some debugging stuff debug = 7 output = /u01/var/stunnel/deptstunnel.log foreground = no # Use it for client mode client = yes # Service-level configuration [App] accept = localhost:8111 connect = hpux-service-ip:8111 Output of "stunnel -version" from HPUX side ================================ stunnel 4.05 on hppa2.0w-hp-hpux11.11 PTHREAD+LIBWRAP with OpenSSL 0.9.7d 17 Mar 2004 Global options cert = /opt/iexpress/stunnel/etc/stunnel/stunnel.pem ciphers = ALL:!ADH:+RC4:@STRENGTH debug = 5 EGD = /var/run/egd-pool key = /opt/iexpress/stunnel/etc/stunnel/stunnel.pem pid = /opt/iexpress/stunnel/var/run/stunnel.pid RNDbytes = 64 RNDoverwrite = yes session = 300 seconds verify = none Service-level options TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTidle = 43200 seconds Output of "uname -a" from HPUX side =========================== HP-UX dptshr1 B.11.11 U 9000/800 2640250230 unlimited-user license Output of "openssl version" from HPUX side =============================== OpenSSL 0.9.7d 17 Mar 2004 "stunnel conf" at HPUX side ================== cert = /u01/etc/stunnel/deptstunnel.cer key = /u01/etc/stunnel/deptstunnel.key chroot = /u01/var/run/stunnel/ # PID is created inside chroot jail pid = /deptstunnel.pid setuid = stunnel setgid = stunnel # Some debugging stuff debug = 7 output = /u01/var/stunnel/deptstunnel.log foreground = no # Use it for client mode #client = yes # Service-level configuration [App] accept = hpux-service-ip:8111 connect = localhost:9111 === ENDS ===

2 1

UDP End-points
by Red Phoenix 03 Nov '04

03 Nov '04

Michal Trojnara mentioned: > On 2004-11-02, at 02:02, Red Phoenix wrote: > > Establishing a SSL connection over UDP would be pretty tough, but has > > anyone thought about the possibility of allowing the 'listen' and > > 'destination' points to be UDP ports, with the main comms routed over > > TCP? This would effectively accomplish what most UDP requestors need. > It's not as easy as you think. SSL requires a stream of data as a > transport. It's much more than a simple UDP forwarder. Perhaps I wasn't quite as clear as I intended.. :) I'm not suggesting that SSL over UDP should be done.. I'm suggesting that stunnel could potentially act as a UDP-over-encrypted-TCP gateway. For example: (For the moment, lets focus on syslog data): Pre-stunnel: Server 1 Sends syslog messages to UDP port 514 on Server 2. Server1 and Server2 both then install stunnel: Server1: Syslog messages are redirected to localhost UDP port 514 (rather than Server2 UDP port 514). Server1: Stunnel listens on UDP port 514, and sends encrypted data to Server2 on TCP port 12345 Server2: Stunnel listens on TCP port 12345, decrypts the data, and sends to localhost UDP port 514. This way, stunnel acts as the UDP to TCP (encrypted) to UDP gateway - in a similar way that it can currently act as a pure TCP -> TCP (encrypted) -> TCP gateway. Regards, Leigh.

3 3

Remove Me
by Lauren Hillquist 03 Nov '04

03 Nov '04

How do I get off this mailing list? Lauren

2 1

OpenSSL 0.9.7e WIN32 binaries
by Michal Trojnara 02 Nov '04

02 Nov '04

Dear Users, I've built WIN32 binaries of the latest OpenSSL library. They're available for download on my ftp site: ftp://stunnel.mirt.net/openssl/binary-0.9.7e-zlib/ Best regards, Mike

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

stunnel-users