On Wed, Feb 25, 2026 at 03:42:10PM +0100, Michał Trojnara via stunnel-users wrote:
Hi Guys,
As a side note, I immensely dislike the way Debian modifies stunnel to make it incompatible with upstream. A good example is how Debian duplicates the functionality of the “include” configuration file option I added over 10 years ago by automagically scanning for *.conf files and starting a separate stunnel daemon for each one.
That is only what the SysV init script does, and it does that largely for backwards-compatibility reasons. The per-config-file systemd service only starts stunnel with the specified config file. This year, I intend to finally do something I have been putting off for years and years and years because of the complexity of handling backwards compatibility, but it has become much more of a maintenance burden (and much more of a support burden for you, for which I do apologize): I intend to rename the stunnel4 package to, well, stunnel :) This will involve a partial incompatibility anyway, so I will try to smuggle a couple of other changes along with it - like e.g. dropping the SysV init script at all[1]. G'luck, Peter [1] I *know* there are people who will object to that. -- Peter Pentchev roam@ringlet.net roam@debian.org peter@morpheusly.com PGP key: https://www.ringlet.net/roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13