Stunnel 3.24 and earlier (as well as 4.0x x<4) does not properly handle SIGCHLD signals safely. Stunnel 3.25 is now available and fixes this problem. This bug can lead to a DoS attack. Since 4.04 in portage is masked and 3.24 the newest stable, this problem still exists.
Not much point in me creating an attachment - the 3.24 ebuild works fine for me when renamed to 3.26.
*** Bug 26717 has been marked as a duplicate of this bug. ***
3.26 is now in portage and stable ...
thanks SpanKY I'm changing resolution to FIXED
No really I'm changing the resolution this time.