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.8p15 was released on 23 June 2020. It addresses 1 medium-severity security issue in ntpd, and provides 13 non-security bugfixes over 4.2.8p13.

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.

Data Structures for Config Saving

A Log can be sent to a File, Syslog, or stderr.

So, the possible logging channels are

• FILE
• SYSLOG
• STDERR

The logging channels take up parameters

FILE - path to the logging file

SYSLOG - name of the SYSLOG FACILITY

STDERR - stderr (is this a parameter?)

The corresponding to each combination of channel_type and channel_parameters, there shall be a list of tags that are to be logged

The data structure that I have in mind is like the following

A structure for a logging channel with members Logging Channel, Channel Parmeters, A linked list of tags, that shall be a linked list on its own, that are to be logged, corresponding to that channel.

typedef enum {
    /* standard output */
    STDOUT,
    /* standard error output */
    STDERROUT,
    /* file output */
    FILEOUT,
    /* ringbuffer output */
    RBUFOUT
    /*syslog output*/
    SYSLOG

} logc_loggerType_t;

typedef struct {

    char *category;

    LoggingTagsList *next;

} LoggingTagsList;

typedef struct {

    int channel_number;

    char *channel_parameter;

    LoggingTagsList categories;

    LoggingChannel *next;

} LoggingChannel;

And then when we encounter a tag, we can look it up in the channels' structures and log it accordingly if found.

-- ShubhamSinghal - 2013-07-20