r9 - 2013-09-17 - 20:30:16 - ShubhamSinghalYou are here: NTP >  Dev Web > GoogleSummerOfCode > GSoC2013LoggingDebugging
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.8p13 was released on 07 March 2019. It addresses 1 medium-severity security issue in ntpd, and provides 17 non-security bugfixes and 1 other improvements over 4.2.8p12.

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.

Logging and Debugging

Summary

Related Items: GSoC2012LoggingDebugging, GSoC2010LoggingAndDebugging, GSoC2009LogDebug, GSoC2009LoggingAndDebugging, bug_small.png Bug #1093, bug_small.png Bug #1408, bug_small.png Bug #2028, bug_small.png Bug #2160, bug_small.png Bug #2227

Tasks

Timeline

Date Task Description % Done
05-27 Community Bonding Students get to know mentors, read documentation, get up to speed to begin working on their projects. choice-yes
06-17 Coding Begins Students begin coding for their GSoC projects choice-yes
07-29 BO Midterm Evals Mentors and students can begin submitting mid-term evaluations. choice-yes
08-02 EO Midterm Evals Mid-term evaluations deadline. choice-yes
09-16 Wrap-up Suggested "Pencils Down" date. Take a week to scrub code, write tests, improve documentation, etc.  
09-23 Firm "Pencils Down" Mentors, students and organization administrators can begin submitting final evaluations to Google.  
09-27 Final Evaluation Final Evaluations Deadline  
09-27 Code Samples Students begin uploading code samples  
10-01 Final Results Final Results Announced  

Discussion and Comments

Shubham, please note that some of the msyslog() items have (or had, depending on when I check something in) newlines at the end of the strings: "...\n" - the trailing \n is not wanted for syslog entries. But this means we will probably never want \n at the end of these strings as we can then add one if we are outputting to a TTY or FILE sink. It also means that if the current code has one directive for TTY or FILE output and the same directive for syslog, we should be able to replace this with a single call that says "output to both syslog and TTY/FILE ". There are also some cases (like libntp/audio.c) where we have plain printf() calls - these should be fixed, too.

-- HarlanStenn - 2013-06-27

trailing '\n' will be eliminated for syslog entry by chomping similar to perl.

-- ShubhamSinghal - 2013-07-21

 
Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r9 < r8 < r7 < r6 < r5 | 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-2020 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