From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5629 invoked by alias); 20 Aug 2013 21:34:41 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 5619 invoked by uid 89); 20 Aug 2013 21:34:41 -0000 X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.2 Received: from mail-ve0-f179.google.com (HELO mail-ve0-f179.google.com) (209.85.128.179) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Tue, 20 Aug 2013 21:34:40 +0000 Received: by mail-ve0-f179.google.com with SMTP id c13so793400vea.38 for ; Tue, 20 Aug 2013 14:34:38 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.220.181.136 with SMTP id by8mr3007191vcb.11.1377034478832; Tue, 20 Aug 2013 14:34:38 -0700 (PDT) Received: by 10.58.112.165 with HTTP; Tue, 20 Aug 2013 14:34:38 -0700 (PDT) In-Reply-To: <5213D3AD.60307@systech.com> References: <5213D3AD.60307@systech.com> Date: Tue, 20 Aug 2013 21:34:00 -0000 Message-ID: From: vxWorker To: jay@systech.com Cc: ecos-discuss@ecos.sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [ECOS] NTP authentication in eCos X-SW-Source: 2013-08/txt/msg00002.txt.bz2 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 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