[ntp:hackers] 4.2.8p4-RC1 fails with crypto_key error (no core file produced)

juergen perlinger juergen.perlinger at t-online.de
Wed Oct 7 07:51:40 UTC 2015


On 10/06/2015 11:50 PM, John Marshall wrote:
> 4.2.8p4-RC1 builds fine for me but fails immediately with the following
> message to SYSLOG.  ntpd does not produce a core file, it just stops.  I
> have logged a bug (2928).
> 
>  Oct  7 07:03:45 rwsrv08 ntpd[52383]: ntpd 4.2.8p4-RC1 at 1.3265-o Tue Oct  6 19:59:44 UTC 2015 (1): Starting
>  Oct  7 07:03:45 rwsrv08 ntpd[52383]: Command line: /usr/sbin/ntpd -g -w 120 -N -c /data/ntpd/ntp.conf -p /var/run/ntpd.pid
>  Oct  7 07:03:46 rwsrv08 ntpd[52384]: proto: precision = 0.908 usec (-20)
>  Oct  7 07:03:46 rwsrv08 ntpd[52384]: crypto_key: error:06074078:digital envelope routines:EVP_PBE_CipherInit:keygen failure 
> 
> I worked back through the ntp-dev releases and 4.3.71 is the most recent
> one which works for me.
> 
> I am running broadcast servers with autokey.
>   broadcast ff08::101 ttl 1 autokey
> 
I tried to find out what happened between 4.3.71 and 4.3.72, and (of
course...) there's nothing obvious.

IMHO there's only one location that could produce that error, and the
daemon does a clean 'exit(-1)' in that case. This would fit your
description.

One of the things that changed where some build options regarding
threading, and I'm getting suspicious here.

I'm Linux based, so my mileage may vary, but can you run ntpd with one
debug ('-d') under strace/ktrace control, capture the output and provide
it? (either direct mail or as attachment to the bug. gzipped, if possible.)

I can't promise anything more than having a look.

Cheers,
	Pearly


More information about the hackers mailing list