Re: BIND update gone bad

2018-11-14 Thread Mathieu Arnold
On Wed, Nov 14, 2018 at 10:44:49AM +0100, Andrea Venturoli wrote: > On 11/14/18 7:35 AM, Matthias Fechner wrote: > > > maybe an OPTION problem. > > Make sure you disable the GOST option (in bind and openssl), I faced a > > similar problem, but I thing this option was removed, but I think it is >

Re: BIND update gone bad

2018-11-14 Thread Andrea Venturoli
On 11/14/18 7:35 AM, Matthias Fechner wrote: maybe an OPTION problem. Make sure you disable the GOST option (in bind and openssl), I faced a similar problem, but I thing this option was removed, but I think it is a try worth. Hello. Just to say I've been hit by the same problem: fortunately

Re: BIND update gone bad

2018-11-14 Thread Mathieu Arnold
On Tue, Nov 13, 2018 at 09:15:12PM -0500, Kevin P. Neal wrote: > Before anyone panics on my behalf, I did a zfs rollback to avoid the new > named problem. But something needs to be fixed somewhere. > > I just did an svn update of /usr/ports, ran poudriere and then did pkg > upgrade, which

Re: BIND update gone bad

2018-11-13 Thread Matthias Fechner
Am 14.11.18 um 03:15 schrieb Kevin P. Neal: > 13-Nov-2018 21:00:30.959 ENGINE_by_id failed (crypto failure) > 13-Nov-2018 21:00:30.959 error:25066067:DSO support routines:DLFCN_LOAD:could > not load the shared >