r4 - 2014-02-02 - 23:56:26 - HarlanStennYou are here: NTP >  Dev Web > DevelopmentIssues > KoDResponses
NTP users are strongly urged to take immediate action to ensure that their NTP daemons are not susceptible to being used in distributed denial-of-service (DDoS) attacks. Please also take this opportunity to defeat denial-of-service attacks by implementing Ingress and Egress filtering through BCP38.

ntp-4.2.8p12 was released on 14 August 2018. It addresses 1 low-/medium-severity security issue in ntpd, 1 low-severity security issue in ntpq and ntpdc, and provides 27 non-security bugfixes and 4 other improvements over 4.2.8p11.

Please see the NTP Security Notice for vulnerability and mitigation details.

Are you using Autokey in production? If so, please contact Harlan - he's got some questions for you.

Kiss-o'-Death (KOD) Responses

Related Topics: NtpProtocolResponseMatrix

KOD codes and meanings

Per RFC5905, Section 7.4 and Figure 13.

DENY - Access denied by remote server

The client MUST demobilize any associations to that server and stop sending packets to that server.

Question: For how long?

 

RATE - Rate exceeded. The server has temporarily denied access because the client exceeded the rate threshold.

The client MUST immediately reduce its polling interval to that server and continue to reduce it each time it receives a RATE kiss code.

Question: How long before the client might try and ask more frequently?

 

RSTR - Access denied due to local policy

The client MUST demobilize any associations to that server and stop sending packets to that server.

Question: For how long?

 

X***

These codes are unregistered and experimental codes. Unless your implementation recognizes the particular code, it MUST be ignored.

"For how long"?

What are good numbers for how long one should "back off" after a KOD response? "Forever" seems way too long. This is similar to the question of "how long should we use an IP we got from a DNS name before we re-resolve it?" In this latter case, Harlan can easily see the case where the TTL value is likely "too short". But that's a different question for a different topic...

 
  • Perhaps it could be a function of the ppoll value from the received KOD packet with some hard-coded minimum and maximum? -- MiroslavLichvar - 28 Jan 2014

Is the KOD mechanism really useful?

 
  • For enforcement, no. As an advisory mechanism, certainly. Think of them as an error return code from any other type of request. -- BrianUtterback - 22 Jan 2014

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r4 < r3 < r2 < r1 | More topic actions
 
SSL security by CAcert
Get the CAcert Root Certificate
This site is powered by the TWiki collaboration platform
IPv6 Ready
Copyright & 1999-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding the site? Send feedback