stunnel4 (3:5.72-3) unstable; urgency=medium

  For Debian installations running systemd, please take note that
  the single `stunnel4.service` unit autogenerated from the SysV
  init script definition is DEPRECATED and will be removed in
  a future version of the package.

  The stunnel@ service template introduced in version 3:5.56+dfsg-7
  is the preferred method of controlling the start and stop of
  the stunnel instances.

 -- Peter Pentchev <roam@debian.org>  Thu, 11 Apr 2024 12:51:38 +0300

stunnel4 (3:5.68-1) unstable; urgency=medium

  The stunnel program will no longer create a process ID file by default.
  The "pid" option needs to be specified explicitly in the stunnel
  configuration file if such behavior is desired.

 -- Peter Pentchev <roam@debian.org>  Sat, 11 Feb 2023 22:20:39 +0200

stunnel4 (3:5.56+dfsg-7) unstable; urgency=medium

  For Debian installations running systemd, it is now possible to
  enable and start stunnel instances controlled by individual
  configuration files in the /etc/stunnel directory. The stunnel@
  service template, when instantiated, will start an stunnel process
  and look for an /etc/stunnel/<instance>.conf file.

  User services are also available under systemd: if started via
  `systemctl --user start stunnel@instance.service`, stunnel will
  look for a ~/.config/stunnel/<instance>.conf file.

  Please note that in both cases, the service files use the "simple"
  systemd service type, so the configuration must include
  a "foreground = yes" setting.

  To prevent confusion with the `stunnel4` systemd service that is
  automatically generated for the /etc/init.d/stunnel4 file,
  the SystemV stunnel4 service is NO LONGER automatically enabled.
  This means that new installations on Debian systems that use
  the SysV init package will need to enable the stunnel4 service.

 -- Peter Pentchev <roam@debian.org>  Fri, 12 Feb 2021 00:28:35 +0200
