Regression #16785
closed
STunnel Core Dumps when started
100%
Description
In 26.03 the STunnel binary fails to start and core dumps:
Apr 11 00:38:35 kernel pid 46912 (stunnel), jid 0, uid 0: exited on signal 10 (core dumped)
This happens in amd64 and aarch64.
Updated by Steve Wheeler 22 days ago
- Status changed from New to In Progress
This looks to be fixed in the current upstream port version, 5.78.
Fixed a startup crash when both global (default) and service-level lists of values are configured for an option.
Updated by Kris Phillips 16 days ago
Is there a particular way to cause this to coredump? I tested sTunnel on 26.03 on an amd64 system and it started without issue.
Seems this could be fixed in 26.03, given that the package can simply be rebuilt for previous releases, as it's not a core component.
Updated by Steve Wheeler 16 days ago
Specifically required is using a custom server cert. Without that it uses only the default cert and starts as expected.
Updated by Mateusz Guzik 11 days ago
- Status changed from In Progress to Feedback
this was fixed in a newer stunnel version
Updated by S Premeau 8 days ago
For the benefit of others that encounter this bug.
I was able to work around this issue by reconfiguring stunnel back to use the default certificate, and then replace
/usr/local/etc/stunnel/stunnel.pemwith a symbolic link to the (properly formatted PEM file) of certificate I really wanted to use.
(In my case, the file I needed is created by the acme certificates package, with the "write certificates to /conf.." option enabled.)
Updated by