From: Jay Foster <jay@systech.com>
To: vxWorker <vxWorker@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] NTP authentication in eCos
Date: Tue, 20 Aug 2013 21:51:00 -0000 [thread overview]
Message-ID: <5213E4B1.4090803@systech.com> (raw)
In-Reply-To: <CAPQw2UapfY97dP+QmU1K7XTEFa+oFoiHnSiybDk5RV3a0joskA@mail.gmail.com>
I used the eCos SNTP code. The code I used is about 8 years old, so
maybe things have changed some. I don't know anything about NTP/v4 or
Autokey protocol.
On 8/20/2013 2:34 PM, vxWorker wrote:
> 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<jay@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!
>>>
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2013-08-20 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 18:22 vx worker
2013-08-20 20:38 ` Jay Foster
2013-08-20 21:34 ` vxWorker
2013-08-20 21:51 ` Jay Foster [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5213E4B1.4090803@systech.com \
--to=jay@systech.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=vxWorker@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).