[ntp:bugs] [Bug 3562] New: ntpq could be paranoid about upstream servers.

bugzilla-daemon at ntp.org bugzilla-daemon at ntp.org
Wed Jan 2 13:26:16 UTC 2019


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

             Bug #: 3562
           Summary: ntpq could be paranoid about upstream servers.
           Product: ntp
           Version: 4.2.8
          Platform: PC
        OS/Version: Windows NT
            Status: CONFIRMED
          Severity: enhancement
          Priority: P5
         Component: ntpq
        AssignedTo: stenn at ntp.org
        ReportedBy: brian.utterback at oracle.com
                CC: bugs at ntp.org
    Classification: Unclassified


We have recently had several reports of the "ntpq -p" command crashing. The
root cause is that the upstream server is sending a malformed status packet
that looks like this:

srcadr=xxx.xxx.xx.xx, srcport=123, dstadr=xxx.xx.xxx.xx, dstport=123,
leap=0, stratum=1, precision=-12, rootdelay=0.000, rootdisp=0.244,
refid, reftime=0xdfb1f11f.00624dce, rec=0xdfbb804a.51d580f6, reach=0xff,
unreach=0, hmode=3, pmode=4, hpoll=10, ppoll=10, headway=0, flash=0x0,
keyid=0, offset=0.180, delay=3.188, dispersion=15.521, jitter=0.181,
xleave=0.063, filtdelay= 3.19 3.45 3.23 3.62 3.26 3.53 3.15 4.02,
filtoffset= 0.18 0.05 -0.08 -0.02 0.14 0.01 -0.04 0.00,
filtdisp= 0.24 16.04 31.62 47.87 64.10 80.03 96.18 112.49
61 111.90

The specific issue is that there is no value after "refid". We are trying to
identify the upstream software that is causing the problem, but ntpq could be
better about checking for bogus packets rather than crashing.

-- 
Configure bugmail: http://bugs.ntp.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the bugs-announce mailing list