stunnel-users

3 participants
3308 discussions

Writing "hello" to log window when entering a certain service section?
by Ben Stover 15 Oct '13

15 Oct '13

Assume an (unknown) client on my computer connects through stunnel to a remote server. As soon as this local client connects local stunnel the stunnel should write a user specified string line to the log window (if possible in bold letters). Can I define this with a syntax similar to: [gmail-pop3] client = yes output = "hello outgoing alert gmail port 1109" accept = 127.0.0.1:1109 connect = pop.gmail.com:995 Thank you Peter

2 1

An issue with chroot, mail.pem and OmniOS/illumos (SunOS)
by Olaf Marzocchi 13 Oct '13

13 Oct '13

Dear all, I have been trying to set up stunnel to encrypt a SMTP connection. The config of the encryption should be fine, I used it already on another OS, but I cannot get stunnel to start on my home server, based on OmniOS (kernel illumos), identified as "SunOS". This is my config: ---- chroot = /opt/omni/var/lib/stunnel/ ; Chroot jail can be escaped if setuid option is not used setuid = nobody setgid = nogroup ;pid = /opt/omni/var/lib/stunnel/stunnel.pid ; Certificate/key is needed in server mode and optional in client mode cert = /opt/omni/etc/stunnel/mail.pem ;key = /opt/omni/etc/stunnel/mail.pem [smtp-tls-wrapper] accept = localhost:11125 client = yes connect = ssl0.ovh.net:465 ;delay = yes ---- and the directories mentioned have the following permissions: ---- OmniOS-Xeon:~ $ ls -al /opt/omni/etc/stunnel/ total 28 drwxr-xr-x 2 root bin 5 Sep 24 23:26 . drwxr-xr-x 5 root bin 6 Sep 23 23:53 .. -rw------- 1 root bin 3050 Sep 24 23:25 mail.pem -rw-r--r-- 1 stunnel stunnel 3247 Oct 13 22:56 stunnel.conf -rw-r--r-- 1 root bin 2997 Sep 23 23:53 stunnel.conf-sample OmniOS-Xeon:~ $ ls -al /opt/omni/var/lib/ total 9 drwxr-xr-x 3 root bin 3 Sep 23 23:53 . drwxr-xr-x 4 root bin 4 Sep 23 23:53 .. drwx------ 2 stunnel stunnel 2 Sep 23 23:53 stunnel ---- The service is started from the SMF facility provided by Solaris/OmniOS/... that launches as root/root the following: /opt/omni/bin/stunnel /opt/omni/etc/stunnel/stunnel.conf On execution I get the following error message: … Initializing service section [smtp-tls-wrapper] Certificate: /opt/omni/etc/stunnel/mail.pem Error reading certificate file: /opt/omni/etc/stunnel/mail.pem error queue: 140DC002: error:140DC002:SSL routines:SSL_CTX_use_certificate_chain_file:system lib error queue: 20074002: error:20074002:BIO routines:FILE_CTRL:system lib SSL_CTX_use_certificate_chain_file: 200100D: error:0200100D:system library:fopen:Permission denied str_stats: 9 block(s), 1032 data byte(s), 522 control byte(s) … I must be overlooking something but I cannot see my mistake. Could you please help me? Thank you very much in advance! Olaf Marzocchi

1 0

stunnel behind http proxy server, only working for port 443
by Heng Su 08 Oct '13

08 Oct '13

Hi All, I try to connect to my stunnel server, however, only port 443 is working. For other ports are not working. Does it mean my company's proxy server is blocking SSL communication on all ports except 443? ( I am a newbie, just assuming stunnel always working with SSL even for 80 port, if I am wrong please point me out, thank you) Is there any other way to bypass the proxy server without SSL communication? Or internal proxy server can always detect tunnel actions if there is non-SSL protocol ? below is my configuration file for client side. /etc/stunnel/stunnel.conf ------------------START-------------------------- [https1] accept = 80 protocol = connect protocolAuthentication = basic protocolHost = myvpsserver-ip:80 protocolUsername = myname protocolPassword = p@ssw0rd connect = company-proxyserver:8080 [https2] accept = 443 protocol = connect protocolAuthentication = basic protocolHost = myvpsserver-ip:443 protocolUsername = myname protocolPassword = p@ssw0rd connect = company-proxyserver:8080 ----------------------------END--------------------------------------------- ---------------------------Tunnel PORT 80 ----------------------------- 2013.10.08 14:18:43 LOG7[10601:3078687600]: TCP_NODELAY option set on remote socket 2013.10.08 14:18:43 LOG5[10601:3078687600]: Negotiations for connect (client side) started 2013.10.08 14:18:43 LOG7[10601:3078687600]: -> CONNECT my-remote-server-ip:80 HTTP/1.1 2013.10.08 14:18:43 LOG7[10601:3078687600]: -> Host: my-remote-server-ip:80 2013.10.08 14:18:43 LOG7[10601:3078687600]: -> Proxy-Authorization: basic c3VoZW5nOlBAc3N3MHJk 2013.10.08 14:18:43 LOG7[10601:3078687600]: -> 2013.10.08 14:18:43 LOG7[10601:3078687600]: <- HTTP/1.1 403 Forbidden 2013.10.08 14:18:43 LOG3[10601:3078687600]: CONNECT request rejected 2013.10.08 14:18:43 LOG7[10601:3078687600]: <- Cache-Control: no-cache 2013.10.08 14:18:43 LOG7[10601:3078687600]: <- Pragma: no-cache 2013.10.08 14:18:43 LOG7[10601:3078687600]: <- Content-Type: text/html; charset=utf-8 2013.10.08 14:18:43 LOG7[10601:3078687600]: <- Proxy-Connection: close 2013.10.08 14:18:43 LOG7[10601:3078687600]: <- Connection: close 2013.10.08 14:18:43 LOG7[10601:3078687600]: <- Content-Length: 725 2013.10.08 14:18:43 LOG7[10601:3078687600]: <- 2013.10.08 14:18:43 LOG5[10601:3078687600]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket ---------------------------Tunnel PORT 443 ----------------------------- 2013.10.08 14:42:00 LOG7[10601:3078687600]: TCP_NODELAY option set on remote socket 2013.10.08 14:42:00 LOG5[10601:3078687600]: Negotiations for connect (client side) started 2013.10.08 14:42:00 LOG7[10601:3078687600]: -> CONNECT my-remote-server-ip:443 HTTP/1.1 2013.10.08 14:42:00 LOG7[10601:3078687600]: -> Host: my-remote-server-ip:443 2013.10.08 14:42:00 LOG7[10601:3078687600]: -> Proxy-Authorization: basic c3VoZW5nOlBAc3N3MHJk 2013.10.08 14:42:00 LOG7[10601:3078687600]: -> 2013.10.08 14:42:00 LOG7[10601:3078687600]: <- HTTP/1.1 200 Connection established 2013.10.08 14:42:00 LOG6[10601:3078687600]: CONNECT request accepted 2013.10.08 14:42:00 LOG7[10601:3078687600]: <- 2013.10.08 14:42:00 LOG5[10601:3078687600]: Protocol negotiations succeeded -- Thanks & Best Regards, Su Heng

2 2

Stunnel North American FTP Down?
by Thomas Eifert 06 Oct '13

06 Oct '13

This evening, I'm unable to access the North American Stunnel FTP site. If I go in with Filezilla in passive mode, I can do a directory listing, but the directory is empty. If I use the browser by clicking on the FTP link on the stunnel web page, I get an error 550 Failed to change directory. I was able to access the European site, however. Enjoy the day. -- Attention: This message and all attachments are private and may contain information that is confidential and privileged. If you received this message in error, please notify the sender by reply email and delete the message immediately.

2 2

IP Address on hte Destination
by Stewart Anderson 03 Oct '13

03 Oct '13

Hi, When a source address connects to a remote destination, via stunnel, what IP address is visible to the destination as the source address? The address of the source or the host where stunnel is running? I see some settings for transparency but I just have a plain connect= for my services. My source and stunnel are on different servers. Cheers Stu This message is confidential. It may also contain privileged information. The contents of this e-mail and any attachments are intended for the named addressee only. Unless you are the named addressee or authorised to receive the e-mail of the named addressee you may not disclose, use or copy the contents of the e-mail. If you are not the person for whom the message was intended, please notify the sender immediately at Bradford Teaching Hospitals NHS Foundation Trust and delete the material from your computer. You must not use the message for any other purpose, nor disclose its contents to any person other than the intended recipient. Bradford Teaching Hospitals NHS Foundation Trust does not accept responsibility for this message and any views or opinions contained in this e-mail are solely those of the author unless expressly stated otherwise.

1 0

Issue with TCPmon and Stunnel
by Odays 01 Oct '13

01 Oct '13

Hi all. I need to configure TCPMon+Stunnel to capture the request/response message in the communication with a web services using https. So I download stunnel-4.56-installer.exe and install it. In TCPMon I put that it listen in port 7777 and redirect to port 1234. In Stunnel I put this configuration: client=yes verify=0 [my-https] accept = 127.0.0.1:1234 connect = webservices_server:443 TIMEOUTclose = 0 When i run the scenario I see this log: 2013.09.30 16:12:57 LOG7[8612:6032]: Service [my-https] started 2013.09.30 16:12:57 LOG5[8612:6032]: Service [my-https] accepted connection from 127.0.0.1:51759 2013.09.30 16:12:57 LOG7[8612:6032]: SSL state (accept): before/accept initialization *2013.09.30 16:12:57 LOG3[8612:6032]: SSL_accept: 1407609C: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request* 2013.09.30 16:12:57 LOG5[8612:6032]: Connection reset: 0 byte(s) sent to SSL, 0 byte(s) sent to socket 2013.09.30 16:12:57 LOG7[8612:6032]: Local socket (FD=448) closed 2013.09.30 16:12:57 LOG7[8612:6032]: Service [my-https] finished (0 left) Any idea about this error? Thanks. -- Este mensaje le ha llegado mediante el servicio de correo electronico que ofrece Infomed para respaldar el cumplimiento de las misiones del Sistema Nacional de Salud. La persona que envia este correo asume el compromiso de usar el servicio a tales fines y cumplir con las regulaciones establecidas Infomed: http://www.sld.cu/

3 2

Generic/general mechanism to forward mail servername, login, port from client to stunnel
by Ben Stover 27 Sep '13

27 Sep '13

Refering to my last posting I want to ask a related question: I read in the past somewhere that I can access stunnel from my local email client in more generic way: At first: stunnel always listens AUTOMATICALLY by default on port 127.0.0.1:9999 für incoming request and forwards the prepared/modified request to the outside world. The core parameter are NOT specified in the .conf file but by the User ID which is passed by the local client to local stunnel service. The syntax is as follows: userid=<servername>/<remotes-ssl-tls-port>/<loginname> Example: userid=pop.mail.yahoo.com/995/myname123 So as soon as stunnel receives at 127.0.0.1:9999 an incoming local connect he accepts the following userid string and tokenize it into the three parts. Given these three tokens stunnel is able to connect in the second step the remote mail server WITHOUT any further need of specification in the .conf file. Do I remember this correct? Is this mechanism described somewhere in detail? Thank you Ben

1 0

PATCH: multiple SNI options per slave section
by David Owen 27 Sep '13

27 Sep '13

Hello and thank you for stunnel! After switching from my web-server's built-in SSL support, I now have a much more secure system and SNI, too! In stunnel(8), I read this about the sni option: "sni option can also be specified more than once within a single slave service." However, I couldn't get it to work, and reading the source code verified that only one sni option is tracked per section. So, I present my patch to allow multiple sni options. It enables configurations like these: [https] ... [group1] sni = https:a.example.org sni = https:b.example.org ... [group2] sni = https:c.example.org sni = https:d.example.org ... If you have a naming scheme that doesn't lend itself to the wildcard matching already supported, this can cut your config size quite a bit. DETAILS The sni option for any section was originally tracked in the section->sni member (a string). Now, a linked-list of sni options is added to the section structure, with every sni option being appended to the end. For server setup, each slave section walks over its list, splitting each sni option and adding that slave section to the master's slave list. Splitting options and adding slaves to masters works as before, but now the slave section iterates over a list instead of referencing a single string. For client setup, each slave section checks that it has either no sni options, or exactly one. Multiple sni options results in an error. If exactly one option is found, it is copied to the old sni field of the section struct. The old sni field has been renamed to servername_to_request, as it is now used only in client mode, and this makes its purpose more clear. When no sni option is found, servername_to_request is initialized from the protocolHost or connect options, as before. I hope this patch is useful to others. Please let me know how I can make it acceptable for inclusing in the stunnel distribution. Thanks, David

1 0

Proxy HTTPS via stunnel without any certificates on proxy/stunnel box
by Gary Chodos 25 Sep '13

25 Sep '13

Greetings, We are trying to decide between SNIProxy and stunnel for the following task: - Client browser hits https://foo.bar.org, which resolves to an IP that corresponds to the stunnel machine listening on 443. - stunnel "forwards" (sorry if this is not the correct technical term) the connection to a different machine, specified by a different IP address, which is also configured to believe it is foo.bar.org and actually has a web server listening on 443 and houses the SSL key/cert. - when stunnel hits the end server, the latter sees the stunnel IP address as source, not the original user's (who initiated the web request for https://foo.bar.org). I believe this is default behavior, but just noting it for completeness. Is it possible to accomplish this (stunnel listening on and connecting to https endpoints) without housing any certs/keys on the stunnel machine itself, because we want the second server to deal with all that and we do not have access to those keys anyway. And of course, the users which go to the https://foo.bar.org should not see any cert mismatches as a result of loading https://foo.bar.org which, for the user, will resolve to the stunnel/proxy IP, rather than the end server which actually had a running web server and keys/cert. Sorry if the above detail is insufficient; do let me know. Thanks for your help. Gary

2 2

Port assignment in .conf file for local email client unique?
by Ben Stover 25 Sep '13

25 Sep '13

Assume I want to connect from my local email client to two (!) remote email servers The corresponding instructions in .conf file looks like (my guess): [smtps-firstacct] accept = 127.0.0.1:259 connect = smtps.myisp1.com:465 [smtps-secondacct] accept = 127.0.0.1:259 connect = smtps.myisp2.com:465 Questions: 1.) a configuration like above with the same "accept" port 259 is NOT possible because stunnel does not know to which remote email server he has to connect. To distinguish two different remote email server I always have to select TWO different accept-ports like [smtps-firstacct] accept = 127.0.0.1:259 connect = smtps.myisp1.com:465 [smtps-secondacct] accept = 127.0.0.1:258 connect = smtps.myisp2.com:465 Correct? 2.) Can I use arbitrary accept-ports like 1242 or 23199 or is there a port range from I have to select one? 3.) Moreover assume I want to make the SSL connection transparent can I select an accept-port 25? 4.) I read somewhere that I have always to specify in email client for POP3/SMTP an address 127.0.0.1:9999 and NOT 127.0.0.1:259 in order to connect to local stunnel service. Because local stunnel service is always listening on port 9999. Is this correct? Thank you Ben

2 2

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