From: Jay Foster <jay@systech.com>
To: vx worker <vxworker@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] NTP authentication in eCos
Date: Tue, 20 Aug 2013 20:38:00 -0000 [thread overview]
Message-ID: <5213D3AD.60307@systech.com> (raw)
In-Reply-To: <CAPK02p5um4od5n-iiT52rLjuPmRDOsObe2H9oR8ifjPhByUo5w@mail.gmail.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
next prev parent reply other threads:[~2013-08-20 20:38 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 [this message]
2013-08-20 21:34 ` vxWorker
2013-08-20 21:51 ` Jay Foster
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=5213D3AD.60307@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).