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). 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.
#OPENVPN STUNNEL 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.
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.
0 kommentar(er)
