[stunnel-users] stunnel 5.20 released

Wed Jul 15 16:35:57 CEST 2015

Yes I compile with fork.

We have been using that for a very long time. In the 7-8 years range if not
a few years more. In the past we decided to use fork to sidestep leaks. We
process astronomical numbers of transactions each year on a 24/7 basis and
never had any problems.

Can you expand a bit on why it is a bad idea?

Thanks.

2015-07-15 10:27 GMT-04:00 Michal Trojnara <Michal.Trojnara at mirt.net>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 14.07.2015 16:24, Philippe Anctil wrote:
> > I am unable to compile stunnel 5.20 against openssl 1.0.2d (or
> > even 1.0.2c). There a compilation error at some point.
> >
> > cron.c:151: warning: conflicting types for 'cron_dh_param'
>
> Did you configure stunnel with "--with-threads=fork"?
> It is broken in stunnel 5.20.  It is also a bad idea in general.
>
> Otherwise, please send me your config.log.
>
> Mike
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQIcBAEBAgAGBQJVpm3YAAoJEC78f/DUFuAUQUAQALbaxWCvvEK8tCygX8YvVudb
> hNYYcMdpVPdH3sfZWt6+wd/0ylskCUpY4+kfpdvoq5yeZA0xCAF+84nk3zqfbyAO
> 1lR9/3bppcLdsnEsTqUApHp1lePECdorW94VRIO7XhTAVjn9pbbEgjdqCqEYPwQ/
> XshreQpeNs2w5cMHiMQqmuIquZF0K4OR33GK6XwmwBHYuNUJXRmCyXas76xrJyd5
> 8q2Q+kIv+tO1sf+FcG/YhPKh1Mq13Q5PFO1DEJBraj7GNCgZkXVNGD+FjlzWRW+K
> rvV1iZLgXV2jcb/2+UsqGx3lN+RYlOvwni6rKjniX8bJalDlD0I3UFotVIqaQsFe
> /Bq2YyQYZhddadJ1TsOhWzc/MWiuwFR7IVWBC8RFVbuyWbdcFT/eHqijXixLNwjl
> KvwIaNe9ba4dUKWDuH0TfmeyoJ3aDd3ROzH6sNmwIJR0bFThY/Fvih0i0sv83vX+
> D1hmHt/9+4MT59C9xHkC2HJQpPJ9wnwvFIWoDHwC+PzhC7kh5NQ42ZIURrsZjVcF
> XRiiPVVjHiWUHfPpsgbpF7Ti4KvkGrGzPcmTZDUEonlnbh87WbkXiAGT2wUWM8G9
> bgrX2vJI8SBL+UI3KawlgiaDfIl2gv5Lo9kySZe311P3VYoLM2pA9aTSf1RG8ZqU
> 9CQd5LBA8bqgjyr5Il3L
> =+hCd
> -----END PGP SIGNATURE-----
> _______________________________________________
> stunnel-users mailing list
> stunnel-users at stunnel.org
> https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users
>

-- 
Philippe Anctil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.stunnel.org/pipermail/stunnel-users/attachments/20150715/d948d958/attachment.html>