David L. Mills wrote: > DJ, > > I don't know either. The message would seem to come from the packet() > routine in ntp_proto.c, which doesn't know about Autokey. However, the > only message produced by that routine is "packet: flash header ...". A > grep over all ../include, ../ntpd and ../libntp turns up no such message > as you cite. > > I don't remember putting in or taking out such a message; if that > happened it was long (in the scheme of things) ago. As there has been a > number of code adjustments to handle errors and odd cases more > gracefully, the best advice I can give is upgrade to the latest snapshot > (ntp-dev). > > Dave > > DJ wrote: > >> I followed the instructions: >> >> http://www.eecis.udel.edu/~mills/ntp/html/authopt.html >> >> For example, trusted host Alice generates keys using >> >> ntp-keygen -H -T -I -p xyz >> >> where H specifies a new host key, T the trusted certificate, I the IFF >> identity scheme and p the password used to encrypt the private key >> files. The group key file is ntpkey_IFFpar_alice.filestamp, where >> filestamp represents the NTP time in seconds when the file was >> generated. >> >> Host Bob generate keys using >> >> ntp-keygen -H -p abc >> >> where abc is different for each group host. The trusted host generates >> a password-protected group key using >> >> ntp-keygen -q xyz -p abc -e >temp >> >> >> AND all I get, on Bob, is >> >> packet: bad data 400 from address: 138.64.1.48 >>
I did enable that at one point in the debug code. You won't normally see that. That should have nothing to do with autokey. It's no longer in the code so I suggest you upgrade first and try again. Danny >> What's going on with autokey ? >> > > _______________________________________________ > questions mailing list > [email protected] > https://lists.ntp.isc.org/mailman/listinfo/questions > _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
