Bug 18499

Summary: ntpdc passwords don't work (ntp v4)
Product: [Retired] Red Hat Linux Reporter: Dean K. Gibson <redhat>
Component: xntp3Assignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 7.0CC: dr
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-10-07 18:15:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dean K. Gibson 2000-10-06 06:19:18 UTC
Please note that this is also a bug in the current ntp distribution from 
ntp.org, but I thought you would want to know, and perhaps fix it ...

Comment 1 Dean K. Gibson 2000-10-07 18:15:04 UTC
ps:  I logged this under xntp3 because you don't have a way of entering bugs 
for ntp.  You can SEARCH for bugs in component ntp, but you'll never find any, 
since ntp is not listed as a valid component for ENTERING bugs.

Comment 2 Dean K. Gibson 2000-10-07 21:14:04 UTC
Under xntp3, the following segment in the ntp.conf file worked:

requestkey  1234
enable      auth

Under ntp v4, this will NOT allow the use of passwords with key "1234" unless 
either the "enable auth" line is removed, OR the following line is added to 
ntp.conf:

trustedkey  1234

So, this is presumably a change in the authentication requirements for ntp v4.


Comment 3 Dean K. Gibson 2000-10-08 19:06:02 UTC
According to the author of ntp (Professor David Mills of the University of 
Delaware), the authentication code in ntp v4 has been tighted, and this is 
expected behavior.  Hence, it is not a bug and the resolution is to include 
the "trustedkey" line shown above in ntp.conf.