r4 - 2012-09-24 - 05:13:55 - HarlanStennYou are here: NTP >  Dev Web > DevelopmentIssues > DesignByContractAndNTP
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.

Design By Contract and NTP

I've started to add 'design by contract' assertions into certain areas of the codebase.

The primary reason for this is to make the code even more stable.

The precipitating cause for this is that the codebase is now being regularly scanned by Coverity and Calysto, and these tools are finding errors.

Here's an example of how these assertions can be used:

...
#include "ntp_assert.h"
...

int foo(char *a) {
    int result;
    int value;

    REQUIRE(a != NULL);
    ...
    bar(&value);
    INSIST(value > 2);
    ...

    ENSURE(result != 12);
    return result;
}
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-2018 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