Re: [UPDATE] security/stunnel to 5.62

2022-03-03 Thread Gleydson Soares
> I think that may be an upstream bug, OpenSSL can return NULL for > RAND_get_rand_method too. > > 351 NOEXPORT int prng_init(GLOBAL_OPTIONS *global) { > 352 int totbytes=0; > 353 char filename[256]; > 354 const RAND_METHOD *meth=RAND_get_rand_method(); > 355 > 356 /* skip PRNG

Re: [UPDATE] security/stunnel to 5.62

2022-03-03 Thread Stuart Henderson
On 2022/03/02 22:19, Gleydson Soares wrote: > Hello, > > I have managed to make stunnel build against libressl. > > While working on it, i've triggered a segfault: > > openbsd-arm64$ stunnel > Segmentation fault (core dumped) > openbsd-arm64$ > > ... > So looked at the coredump to find clues:

Re: [UPDATE] security/stunnel to 5.62

2022-03-02 Thread Gleydson Soares
Hello, I have managed to make stunnel build against libressl. While working on it, i've triggered a segfault: openbsd-arm64$ stunnel Segmentation fault (core dumped) openbsd-arm64$ ... So looked at the coredump to find clues: Program received signal SIGSEGV, Segmentation fault. prng_init

Re: [UPDATE] security/stunnel to 5.62

2022-02-28 Thread Gleydson Soares
> Updates security/stunnel to 5.62 > > Lots of changes, some of which are marked with urgency 'HIGH' and which > might affect OpenBSD users as well: https://www.stunnel.org/NEWS.html > > Upstream seems to be opposed to having stunnel linked with LibreSSL, and the > changes between 5.44