This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: NTP authentication in eCos
- From: Jay Foster <jay at systech dot com>
- To: vx worker <vxworker at gmail dot com>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Tue, 20 Aug 2013 13:38:05 -0700
- Subject: Re: NTP authentication in eCos
- References: <CAPK02p5um4od5n-iiT52rLjuPmRDOsObe2H9oR8ifjPhByUo5w at mail dot gmail dot com>
- Reply-to: jay at systech dot com
I have used the sntp eCos. I don't use authentication, but did have a
problem a while back with the sntp code not working with ntp servers
that were configured to do NTP auth. The eCos sntp code includes the
KeyIdentifier and MessageDigest fields in it's NTP packets to the NTP
server, but it never fills them in with anything useful. As long as the
NTP server isn't configured for NTP auth, it ignores this and all worked
fine. I encountered an NTP server that was configured for auth, and
would not respond to the eCos NTP packets because the auth failed. I
removed the two fields from the NTP_PACKET structure and it then worked
fine. So, if you add auth support, you should change the code to send
the KeyIdentifier and MessageDigest fields only when they have been
actually filled in with something (ie, doing auth).
Jay
On 8/20/2013 11:22 AM, vx worker wrote:
Hello everybody! Now I need to make NTP authentication work in eCos.
Does anybody have similar experience on this? or any information?
Thanks, Yan!
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss