r3 - 2013-07-21 - 09:51:22 - ShubhamSinghalYou are here: NTP >  Dev Web > GoogleSummerOfCode > GSoC2013LoggingDebugging > GSoC2013LoggingDebuggingDocumentation
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

The logging channels take up parameters

FILE - path to the logging file


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 */
    /* standard error output */
    /* file output */
    /* ringbuffer output */
    /*syslog output*/

} 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

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-2022 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