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.
Are you using Autokey in production? If so, please contact Harlan - he's got some questions for you.
Release Engineering Issues
"What's New" list for the announcements
I'd like to see us have a decent solution to this issue for the 4.3.0 release.
"What's New" for
Presently, we grab the first whack of entries in the
file up to the version that is stored in the
file. This is tolerable because we really should be noting the differences between each point release in
As I understand it, SteveKostecke
suggests this document contain:
- the Version number
- Release Focus
- Code Cleanup
- Minor Feature Enhancements
- Major Feature Enhancements
- Minor Bug Fixes
- Major Bug Fixes
- Minor Security Fixes
- Major Security Fixes
It would also be nice to have a less-than 600 character summary of the changes written in complete sentences using 3rd-person English.
"What's New" for
While we sometimes note changes in the
, we do not (presently) identify changes in each point release for
It might be useful to
the previous and current
files to generate the "What's New" list for the announcements.
If we go to something along the lines of the
, we could do the same.
This approach could work for both
files primarily because:
- we use
autoconf and these files are required by GNU coding standards
- I like that we can keep detailed change information in a
ChangeLog and summarize the important changes in a
One current problem is that maintenance of these files is difficult.
We now generate the
file from the
commit logs, and as of
we can easily remove the empty merge comments, which make this list much more readable.
file is still manually maintained.
While I'm not thrilled with the
file that comes with
, I do see that contains useful information and if I could figure out an easy way to maintain such a file I'd probably use that format.
Here's something: http://ch.tudelft.nl/~arthur/svn2cl/
This is an xsl stylesheet for generating a classic GNU-style ChangeLog from a subversion repository log. It is made from several changelog-like scripts using found in different places.
It's similar to cvs2cl (http://www.red-bean.com/cvs2cl/
- 19 Oct 2006