This bug was fixed in the package stunnel4 - 3:5.56+dfsg-10
---
stunnel4 (3:5.56+dfsg-10) unstable; urgency=medium
* Allocate a new memory buffer for the pidfile path in
the 04-restore-pidfile-default patch, since it may be freed when
stunnel is reconfigured, e.g. on a
I hit this bug. The analysis here appears correct to me. PIDFILE is a
static string (via a preprocessor define). The suggested fix of calling
str_dup() sounds correct.
Adding this to the top of a stunnel config file is a work-around:
pid = /var/run/stunnel4.pid
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: stunnel4 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901784
Title:
