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.
An intuitive way to see when somebody did something in a determined part of the code is through annotate command.
The annotate command requiers one obligatory parameter: a file name, which is the file we want to explore. Suppose we want to see the annotated version of the source ntpd.c, well we just type (assuming that we are working at our repository root):
$ bk annotate ntpd/ntpd.c
This particular example will generate a huge output, we can just redirect or pipe it to a file or a program.
$ bk annotate ntpd/ntpd.c | less # less is more than more :-D
Say we want to see only the annotated version at a specific revision, this can be done using the parameter -r, like this:
$ bk annotate -r1.1 ntpd/ntpd.c
Nice don't you think?, you are now looking at the first revision of the NTP daemon source code.
We can manage the format of each annotated line by using the -Aformat parameter, where format stands for:
b Prefix each line with the basename of the file.
d Prefix each line with the date of last modification.
n Prefix each line with its line number.
p Prefix each line with pathname of the file relative to the root of the repository.
r Prefix each line with the revision of last modification.
u Prefix each line the name of the user who last modified it.
Try this:
$ bk annotate -Adu ntpd/ntpd.c
Now we know when who modified what in ntpd.c.
To see which lines were added when we can use the -R parameter:
$ bk annotate -R1.20 ntpd/ntpd.c # See what was added in revision #20
For a complete usage see the command online help by typing:
$ bk help annotate
--
FernandoHauscarriaga - 06 Mar 2007