[ntp:bugs] [Bug 431] Wrong auth state reported by "ntpq -c as"

[bugzilla at ntp.isc.org]

http://bugs.ntp.isc.org/show_bug.cgi?id=431





------- Additional Comments From mills at udel.edu  2005-05-20 14:10 -------
Subject: Wrong auth state reported by "ntpq -c as"

Martin,

I do apologize for the curt response, but the only thing I will listen 
to is whether moving the peer process bits further left would serve your 
purpose.

Dave

bugzilla at ntp.isc.org wrote:

>http://bugs.ntp.isc.org/show_bug.cgi?id=431
>
>
>
>
>
>------- Additional Comments From martin.burnicki at meinberg.de  2005-05-20 07:52 -------
>Dave,
>
>If anything is consistent as-is, then why is "ntpq -c as" reporting "auth bad"
>when authentication is in fact OK? Even if you change this in the recent ntpq,
>the error would occur vice-versa if the recent ntpq is run against an ntpd older
>than patch level 1.1346.
>
>I recall that in your own postings you told users not to use ntpdc since it is
>version-specific; instead they should use ntpq:
>
><quote>
>The (x)ntpdc programs were never intended to interoperate between
>versions, although some versions did interoperate with others. The
>protocol is not specified in the standard, as the programs are used
>mainly to debug details specific to each version implementations. Use
>the ntpq program instead. The protocol is specified in the standard and
>it works transparently in all versions.
><quote>
>
>For reference, see  
>http://groups.google.com/groups?selm=3C1FB623.57B7EF7D%40udel.edu&output=gplain
>
>Now this has been broken, it's no mor transparent, and I see users asking why
>they don't seem to get authentication work properly, when in fact it already
>does, but just the wrong status is displayed by ntpq. This is exactly what
>happened to me.
>
>We know that in larger networks there are different versions of (x)ntpd running,
>some current Unix versions are still being shipped with NTP v3 versions. I've
>got a Sun machine her with Solaris 9 which has been shipped with xntpd 3-5.93e.
>MD5 authentication works properly, and the status is displaced correctly with
>any version of ntpq. If I run a recent dev version of ntpd, then auth also works
>but is reported as bad. This is the thing that is in fact bad, not the
>authentication status.
>
>Best regards,
>
>Martin
>
>
>
>------- You are receiving this mail because: -------
>You are on the CC list for the bug, or are watching someone who is.
>





------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.