- stunnel-users - stunnel.org

Problems with Powerposter?
by Roger Stevens 10 Jan '07

10 Jan '07

I'm curious if anyone else has tried Stunnel with Powerposter on the Giganews Usenet network. I (and many other users) have reported problems whereby the post does not complete and just hangs. Per Giganews, this is a software problem and not their servers. Non-SSL posting in Powerposter works fine. but hangs when Stunnel is used usually after a couple of files are successfully uploaded. Any else run into this? TIA! Roger

1 0

re: Problem with certificates using smtp/pop
by David Chase 10 Jan '07

10 Jan '07

I tried sending directly to you, I must have looked like a spammer. I am ever so slightly pleased to see that I have some company in my frustration with this software. I'll try to help, since the experts seem to be too busy. I've only used it twice, and it was painful both times. Have you gotten it to work at all? That is, what do you see? Do you get a running stunnel process? Do you have (with permissions) ls -l /usr/local/etc/stunnel/mail.pem -rw------- 1 root staff 2233 Jan 5 17:25 /usr/local/etc/stunnel/ mail.pem I created it by running this command in that directory: sudo openssl req -new -out mail.pem -keyout mail.pem -nodes -x509 - days 365 I created a stupid certificate, because at some point it looked like it was asking me for my name (David Chase) when what they wanted was my fully qualified domain name (dr2chase.org) so that part of the certificate is wrong. The certificate creation in the makefile asked for this in a slightly more sensible way, using the abbreviation "FQDN", though you have to wonder how busy the authors of some of this security software are, that they cannot take the time to type in "Fully qualified domain name", and instead expect us to figure it out. It can be whiny about permissions, in a non-specific way (as if the software ran a one-way-hash on the permissions, didn't get a match, and expected you to just guess till it worked.) sudo chmod 600 /usr/local/etc/stunnel/mail.pem sudo chmod 755 /usr/local/etc/stunnel/ sudo chown root /usr/local/etc/stunnel/stunnel.conf You'll need to copy the sample stunnel.conf file into the real one: sudo cp /usr/local/etc/stunnel/stunnel.conf-sample /usr/local/etc/ stunnel/stunnel.conf You might want to look it over, though I don't recall changing much in mine. You might want to turn on debug logging there; mine seemed to spew in the invoking terminal, instead of any file that I could find, but that was good enough for a start: debug = 7 output = stunnel.log Some part of stunnel created its chroot directory with incorrect (for MacOS, at least) permissions: % ls -ld /usr/local/var/lib/stunnel/ 948 drwxrwx--T 2 root wheel 68 Jan 5 16:55 /usr/local/var/lib/ stunnel/ That's the one that didn't work, and clearly someone thought carefully about giving it the wrong permissions -- that "T" didn't get there accidentally. This caused silent failure for me. What worked, but might not be secure, is drwxrwxrwx 2 root wheel 68 Jan 6 00:16 /usr/local/var/lib/stunnel/ My guess is that it would be better if it were owned by nobody/nogroup, but this is clearly something that trained experts should GET RIGHT, instead of leaving it busted for novices to tinker with. What mail reader are you using? For example, Apple Mail's "connection doctor" will treat an unofficial certificate as a connection failure; only when you actually try to receive or send mail, will you get a chance to trust the certificate. Perhaps my sarcastic remarks will cause someone to actually fix something. Who knows. yours, David Chase

1 0

STunnel not creating connections.
by Paul Morrison 09 Jan '07

09 Jan '07

I have a problem perhaps someone can help me with. I have setup Stunnel and OpenSSL on a Windows 2003 server. It is configured to accept data on TCP port 2000, decrypt it, then pass it on to TCP port 8014. I have placed the certificates provided for this in a directory and I have told STunnel where these certificates are. The problem I am having is I can see the connection from port 2000 coming in to the system, but STunnel then does nothing before finally dropping the connection. The version of STunnel and OpenSSL are (stunnel 4.15 on x86-pc-mingw32-gnu with OpenSSL 0.9.7i 14 Oct 2005) I have the same setup at a different site on a different server and it works fine. In the debug.log the following is output: 2007.01.09 13:41:02 LOG7[684:352]: MATSU_GPRS started 2007.01.09 13:41:02 LOG7[684:352]: FD 196 in non-blocking mode 2007.01.09 13:41:02 LOG5[684:352]: MATSU_GPRS connected from 212.183.136.192:57511 2007.01.09 13:41:02 LOG7[684:352]: SSL state (accept): before/accept initialization 2007.01.09 13:41:22 LOG3[684:352]: SSL_accept: Peer suddenly disconnected 2007.01.09 13:41:22 LOG5[684:352]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket 2007.01.09 13:41:22 LOG7[684:352]: MATSU_GPRS finished (0 left) I would normally expect to see details of the SSL connection and the certificates being checked after the line 2007.01.09 13:41:02 LOG7[684:352]: SSL state (accept): before/accept initialization, but as you can see it does nothing before dropping the connection after 20 seconds. Does anyone know why this installation of STunnel does not seem to be attempting to use the certificates provided? I would be very grateful for any advice. P.S. Do I need to have a Certifcate Authority server setup at the site in order for STunnel to work? Paul Morrison IT Support Specialist TS3 Services Ltd Castle Court, Carnegie Campus Dunfermline KY11 8PB TEL: 01383 629900 Mob: 07918078864 EMAIL: Paul.Morrison(a)ts3services.co.uk <BLOCKED::mailto:Paul.Morrison@ts3services.co.uk>

1 0

Problem with certificates using smtp /pop
by Klaas 09 Jan '07

09 Jan '07

Isn't there no one who knows how do deal with certificate? > Is there no one who can tell me exactly which part of the > certificate I have to place where and how I must configure > stunnel.conf for the certificate >> I have installed stunnel 4.20 on Windows2003 server and have >> created my private key as follow: >> openssl req -new -days 365 -nodes -config stunnel.cnf -out >> certreq.pem -keyout stunnel.pem >> >> After that I have send certreq.pem to my own CA and have >> received a certnew.cer file. But what I have to do next because >> I still receive the message that the CN-name of the certificate >> is not the same with the given name. >> >> I append this certificate (certnew.cer) to my stunnel.pem file like: >> -----BEGIN RSA PRIVATE KEY----- >> data here >> -----END RSA PRIVATE KEY----- >> -----BEGIN CERTIFICATE----- >> data here >> -----END CERTIFICATE----- >> >> But this doesn't work. Still receive the message that I also read >> on the stunnel.conf must I config something here? >> cert = stunnel.pem >> key = stunnel.pem >> >> ; Authentication stuff >> ;verify = 2 >> ; Don't forget to c_rehash CApath >> ;CApath = certs >> ; It's often easier to use CAfile >> ;CAfile = certs.pem >> ; Don't forget to c_rehash CRLpath >> ;CRLpath = crls >> ; Alternatively you can use CRLfile >> ;CRLfile = crls.pem >> >> Can anyone tell me please what certificate I place where and how config >> the stunnel.conf so I get this working?

1 0

RE: [stunnel-users] URL changes in browser to http from https
by Casey Rayman 08 Jan '07

08 Jan '07

I figured it out. The webserver was redirecting me to the index.html page so that is where the protocol was getting changed. So now the question changes. Is there a function in stunnel for URL rewriting? In otherwords the webserver sends back "redirect yourself to http:// but stunnel intercepts that before it gets back to your browser to keep the connection secure? Thanks, Casey -----Original Message----- From: stunnel-users-bounces(a)mirt.net [mailto:stunnel-users-bounces@mirt.net] On Behalf Of Casey Rayman Sent: Monday, January 08, 2007 10:10 AM To: stunnel-users(a)mirt.net Subject: [stunnel-users] URL changes in browser to http from https I am just starting to experiment with stunnel on Debian Linux, using the standard debian packages. I've got it working so far accepting requests on the local port 443 and connecting on 80, but when the page loads the URL changes back to a non-secure address. To illustrate: https://192.168.1.10 loads a simple static web page and you get the normal warning for the certificate, but after the page loads the URL changes to http://192/168.1.10 . I thought this might just be IE or something but Firefox does it too. Could I be missing a setting in stunnel? Any ideas? Thank you, Casey _______________________________________________ stunnel-users mailing list stunnel-users(a)mirt.net http://stunnel.mirt.net/mailman/listinfo/stunnel-users

2 1

URL changes in browser to http from https
by Casey Rayman 08 Jan '07

08 Jan '07

I am just starting to experiment with stunnel on Debian Linux, using the standard debian packages. I've got it working so far accepting requests on the local port 443 and connecting on 80, but when the page loads the URL changes back to a non-secure address. To illustrate: https://192.168.1.10 loads a simple static web page and you get the normal warning for the certificate, but after the page loads the URL changes to http://192/168.1.10 . I thought this might just be IE or something but Firefox does it too. Could I be missing a setting in stunnel? Any ideas? Thank you, Casey

1 0

Problem with certificates using smtp /pop
by Klaas 08 Jan '07

08 Jan '07

Is there no one who can tell me exactly which part of the certificate I have to place where and how I must configure stunnel.conf for the certificate

1 0

patch: round robin load balancing
by Luke Deller 08 Jan '07

08 Jan '07

Hi, I noticed that stunnel already does round-robin load balancing of connections when the DNS name specified by the "connect" option resolves to multiple IP addresses. Here is a simple patch which allows the "connect" option to accept a comma separated list of names instead of just a single name. This can be used to load balance tunnelled connections across several servers. For example, to load balance HTTPS connections across 3 HTTP servers (localhost:80, anotherhost:8080 and anotherhost:8081), we could specify: [https] accept = 443 connect = 80,anotherhost:8080,anotherhost:8081 Regards, Luke. ********************************************************************************************** Important Note This email (including any attachments) contains information which is confidential and may be subject to legal privilege. If you are not the intended recipient you must not use, distribute or copy this email. If you have received this email in error please notify the sender immediately and delete this email. Any views expressed in this email are not necessarily the views of XPlan Technology. It is the duty of the recipient to virus scan and otherwise test the information provided before loading onto any computer system. Xplan Technology does not warrant that the information is free of a virus or any other defect or error. **********************************************************************************************

1 0

re: I am clearly doing something wrong
by David Chase 06 Jan '07

06 Jan '07

Foolishly, I trusted it to create /usr/local/var/lib/stunnel/ with the correct permissions. The directory that appeared had these permissions: ls -ld /usr/local/var/lib/stunnel/ drwxrwx--T 2 root wheel 68 Jan 5 16:55 /usr/local/var/lib/stunnel/ When I replaced it with this directory ls -ld /usr/local/var/lib/stunnel/ drwxrwxrwx 3 root wheel 102 Jan 5 20:43 /usr/local/var/lib/stunnel/ Suddenly, when I ran stunnel, it continued to run. I'd call this a bug. Still not doing quite what I want, (not connecting to elsewhere.com like I expect) but I'm closer. David Chase

1 0

I am clearly doing something wrong
by David Chase 06 Jan '07

06 Jan '07

But I think the documentation has some serious gaps in it, too. I compiled stunnel, installed it, created certificates, and even turned on debugging in the configuration file. Now, all I want to do is forward port 443 locally to port 80 elsewhere. Says my config file: cert = /usr/local/etc/stunnel/mail.pem ;key = /usr/local/etc/stunnel/mail.pem ; Protocol version (all, SSLv2, SSLv3, TLSv1) sslVersion = SSLv3 ; Some security enhancements for UNIX systems - comment them out on Win32 chroot = /usr/local/var/lib/stunnel/ setuid = nobody setgid = nogroup ; PID is created inside chroot jail pid = /stunnel.pid ; Some performance tunings socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 ; Some debugging stuff useful for troubleshooting debug = 7 output = stunnel.log ; Use it for client mode ; client = yes ; Service-level configuration [pop3s] accept = 995 connect = 110 [imaps] accept = 993 connect = 143 [ssmtp] accept = 465 connect = 25 [https] accept = 443 connect = elsewhere.com:80 TIMEOUTclose = 0 and when I run it, it says: sudo /usr/local/sbin/stunnel Password: 2007.01.05 18:51:01 LOG7[13470:2684415368]: Snagged 64 random bytes from /Users/chase/.rnd 2007.01.05 18:51:01 LOG7[13470:2684415368]: Wrote 1024 new random bytes to /Users/chase/.rnd 2007.01.05 18:51:01 LOG7[13470:2684415368]: RAND_status claims sufficient entropy for the PRNG 2007.01.05 18:51:01 LOG7[13470:2684415368]: PRNG seeded successfully 2007.01.05 18:51:01 LOG7[13470:2684415368]: Certificate: /usr/local/ etc/stunnel/mail.pem 2007.01.05 18:51:01 LOG7[13470:2684415368]: Certificate loaded 2007.01.05 18:51:01 LOG7[13470:2684415368]: Key file: /usr/local/etc/ stunnel/mail.pem 2007.01.05 18:51:01 LOG7[13470:2684415368]: Private key loaded 2007.01.05 18:51:01 LOG7[13470:2684415368]: SSL context initialized for service pop3s 2007.01.05 18:51:01 LOG7[13470:2684415368]: Certificate: /usr/local/ etc/stunnel/mail.pem 2007.01.05 18:51:01 LOG7[13470:2684415368]: Certificate loaded 2007.01.05 18:51:01 LOG7[13470:2684415368]: Key file: /usr/local/etc/ stunnel/mail.pem 2007.01.05 18:51:01 LOG7[13470:2684415368]: Private key loaded 2007.01.05 18:51:01 LOG7[13470:2684415368]: SSL context initialized for service imaps 2007.01.05 18:51:01 LOG7[13470:2684415368]: Certificate: /usr/local/ etc/stunnel/mail.pem 2007.01.05 18:51:01 LOG7[13470:2684415368]: Certificate loaded 2007.01.05 18:51:01 LOG7[13470:2684415368]: Key file: /usr/local/etc/ stunnel/mail.pem 2007.01.05 18:51:01 LOG7[13470:2684415368]: Private key loaded 2007.01.05 18:51:01 LOG7[13470:2684415368]: SSL context initialized for service ssmtp 2007.01.05 18:51:01 LOG7[13470:2684415368]: Certificate: /usr/local/ etc/stunnel/mail.pem 2007.01.05 18:51:01 LOG7[13470:2684415368]: Certificate loaded 2007.01.05 18:51:01 LOG7[13470:2684415368]: Key file: /usr/local/etc/ stunnel/mail.pem 2007.01.05 18:51:01 LOG7[13470:2684415368]: Private key loaded 2007.01.05 18:51:01 LOG7[13470:2684415368]: SSL context initialized for service https I see nothing that looks like a complaint, but when I go looking for a stunnel process, there is not one, nor is anyone listening on port 443 at localhost. I cannot be the first person who wanted to do this, but I found both the FAQ and the documentation to be uninformative. How do I keep stunnel running and listening for connections on 443? I tried client=yes, that didn't seem to help. I am running Stunnel 4.20 on MacOS 10.4.8 David Chase

1 0