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.

There are a number of commands you can use to just query the properties of changesets, either the changesets that are already in your repo or the changesets that you'd get from your parent if you did a bk pull. Before you get into these commands, you should review how to specify revision ranges at BkRevisionRanges, since you can use this syntax to identify cset ranges. And you can also review the keywords that will be useful over at BkKeywords.

The main command for querying various things about a changeset is bk changes. There are two other commands -- bk rset and bk cset -- but these are listed as not for normal human consumption so we won't get into them here.

First, how to list some meta-info about csets in your current repository:

 $ bk changes -r+                 # default info about this cset
 $ bk changes -r+ -nd:REV:        # most recent cset's number only
 $ bk changes -r+ -nd:COMMENTS:   # most recent cset's comment field only

Some variations you can add to the above:

• different keywords, as explained in bk prs

• different revision numbers, and revision ranges, as explained at BkRevisionRanges

• reversing the chronological order of the output with -f

and other options documented at bk helptool changes.

In addition to information about the changeset itself, you can display information about the files in a changeset by adding the -v option to bk changes, as in:

 $ bk changes -r+ -vnd:GFILE:     # files involved in that cset

Finally, you can query changesets that you haven't even pulled from the parent repo yet with any variation of:

 $ bk changes -R