Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #257508

Re: Starting stunnel with systemd.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

1. stunnel hasn't been in Debian since etch (Debian 4.0).

2. stunnel4 comes with a service file template 
(https://sources.debian.org/src/stunnel4/3%3A5.68-2/debian/stunnel4%40.stunnel.service/), 
which is likely to have been tested to work.

3. Could the warning about protecting your POP3 connection be the cause?


On 23/04/2023 17:41, peter@easthope.ca wrote:
> Hi,
>
> After starting interactively, stunnel works.
>
> To automate, this service file was created.
>
> $ cat /etc/systemd/system/stunnel.service
> [Unit]
> Description=StunnelStarter
> Documentation=man:stunnel(8)
> After=network.target auditd.service
>
> [Service]
> ExecStart=/usr/bin/stunnel /etc/stunnel/stunnel.conf foreground=yes
> Restart=no
> Type=simple
>
> [Install]
> WantedBy=multi-user.target
> Alias=stunnel.service
>
> After booting, no stunnel.
>
> $ ps aux | grep stunnel
> root        1463  0.0  0.0   6244   700 pts/0    S+   09:31   0:00 
> grep stunnel
>
> $ systemctl status stunnel
> * stunnel.service - StunnelStarter
>      Loaded: loaded (/etc/systemd/system/stunnel.service; enabled; 
> vendor preset: enabled)
>      Active: inactive (dead) since Sun 2023-04-23 08:52:52 PDT; 7min ago
>        Docs: man:stunnel(8)
>     Process: 572 ExecStart=/usr/bin/stunnel /etc/stunnel/stunnel.conf 
> foreground=yes (code=exited, status=0/SUCCESS)
>    Main PID: 572 (code=exited, status=0/SUCCESS)
>         CPU: 13ms
>
> Apr 23 08:52:52 imager stunnel[572]: LOG5[ui]: Threading:PTHREAD 
> Sockets:POLL,IPv6,SYSTEMD TLS:ENGINE,FIPS,OCSP,PSK,SNI Auth:LIBWRAP
> Apr 23 08:52:52 imager stunnel[572]: LOG5[ui]: Reading configuration 
> from file /etc/stunnel/stunnel.conf
> Apr 23 08:52:52 imager stunnel[572]: LOG5[ui]: UTF-8 byte order mark 
> not detected
> Apr 23 08:52:52 imager stunnel[572]: LOG5[ui]: FIPS mode disabledApr 
> 23 08:52:52 imager stunnel[572]: LOG4[ui]: Service [pop3] needs 
> authenticati
> on to prevent MITM attacks
> Apr 23 08:52:52 imager stunnel[572]: LOG5[ui]: Configuration successful
> Apr 23 08:52:52 imager stunnel[584]: LOG5[main]: Terminated
> Apr 23 08:52:52 imager stunnel[584]: LOG5[main]: Terminating 1 service 
> thread(s)
> Apr 23 08:52:52 imager stunnel[584]: LOG5[main]: Service threads 
> terminated
> Apr 23 08:52:52 imager systemd[1]: stunnel.service: Succeeded.
>
> Terminated.  Why?
>
> Thanks,               ... P.
>

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Starting stunnel with systemd. peter@easthope.ca - 2023-04-23 19:00 +0200
  Re: Starting stunnel with systemd. Darac Marjal <mailinglist@darac.org.uk> - 2023-04-23 20:30 +0200
    Re: Starting stunnel with systemd. Virgo Pärna <virgo.parna@mail.ee> - 2023-04-27 10:20 +0200
  Re: Starting stunnel with systemd. Jeffrey Walton <noloader@gmail.com> - 2023-04-24 04:10 +0200
  Re: Starting stunnel with systemd. john doe <johndoe65534@mail.com> - 2023-04-24 09:10 +0200
    Re: Starting stunnel with systemd. <tomas@tuxteam.de> - 2023-04-24 09:50 +0200
      Re: Starting stunnel with systemd. Greg Wooledge <greg@wooledge.org> - 2023-04-24 13:50 +0200

csiph-web