Hi Jay, thanks for your response, I 'll keep that in mind. Were you using SNTP included in eCos? My plan is to port latest NTP source code package (4.2.6p5) to eCos. NTPv4 implemented Autokey protocol, I'am worrying about uncertainties ahead of me in this porting. Does eCos support that? How about openSSL, freeBSD ... ? Does NTP/v4 has any version requirement for those parts? Yan
On Tue, Aug 20, 2013 at 1:38 PM, Jay Foster <j...@systech.com> wrote: > 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! >> > -- Yan Xiu -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
