A single stunnel instance could be used to provide both client and server functionalities for different services at the same time. While at the time of writing, spawning different instances of stunnel for each conf file it is still supported, it appears that in most cases it might not be necessary. You should use a single file called nf and add include = /stunnel/conf.d in that instead. stunnel can be run as a non-root user (assuming that it doesn’t try to write anything to privileged places 2, or open some privileged ports), but there is a better way to do it:Īccording to the stunnel author, with the planned introduction of a control interface (conceptually similar to apache2ctl), running separate processes for each *.conf will become obsolete.
Note that in this example, we are running stunnel as root. Stunnel can be manually called with the config file as its argument and it will work.įor example, assuming the file is located at /etc/stunnel/nf, the following command would run it: 1 sudo stunnel /etc/stunnel/nf
Moreover, couple of scripts are included in the package to deal with the ppp connections (to handle ppp status changes gracefully by restarting the stunnel process). The installation process also comes with its own stunnel4 user, init script, and logrotate config (which we’ll take advantage of soon).
Stunnel degub install#
We’ll be using Ubuntu’s own repository: sudo sh -c 'apt-get update & apt-get install stunnel4' Please share your results with me so I can update this post. There is a good chance however that the same procedure (maybe with slight adjustments), could work on other Ubuntu versions (or even other distros) as well.
Stunnel degub how to#
This post is dedicated to show you how to properly install and configure this magnificent piece of software on Ubuntu.įor this, I’ll be using Ubuntu 18.04 Server. Set up with a shell script that's running stunnel,Īnd the shell script includes "set -x".We all know how awesome stunnel is, but setting it up properly on Ubuntu (and on most other distros, really), can be a little tricky. The "+stunnel" response looks like the server is Protocol has been negotiated and both sides areĮncrypting the data will you see the greeting message Theįirst data you should see is binary data that's part Getting an SSL connection to the mail server. Telnet will only make a plain text connection, You're seeing any kind of plain text, something is If you're using telnet to connect on port 465, and I think you need to talk to the server administrator. : Connection resetI have no idea, what a stunnel is, but it is causing the problem, I think.ĭoes anybody have any ideas what can be wrong? Or does anyone know how to check the server setting? Or what properties can I try to set? (I've tried all possible options of the properties I am already setting in the code).
Stunnel degub code#
+ stunnelDEBUG SMTP: connected to host "host name of the server", port: 465ĭEBUG SMTP: bad server response: + stunnelĭEBUG SMTP: got response code 220, with response: 220 Go aheadĭEBUG SMTP: exception reading response: : Connection reset Transport transport = session.getTransport() ĭEBUG: getProvider() returning ĭEBUG SMTP: trying to connect to host "host name of the server", port 465, isSSL falseĢ20 "host name of the server" ESMTP Sendmail 8.13.1/8.13.1 Fri, 18:10:49 +0100 Session session = Session.getDefaultInstance(props) I was told, that is uses SSL, but when I use SMTPSSLTransport, it says the "Unrecognized SSL, plaintext connection?". I've identified, that the server uses some kind of strange "secure" connection.
I've looked around the web, I've searched the forums, but found no solution. But I need to send mail through port 465. The server works fine, when using port 25. I need to send message through a STMP server I don't know much about.
0 kommentar(er)
