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.

While you're working with your cloned repository, it's quite possible that changes are happening upstream in the parent repo. If you just want a report on changes in the parent repo, you might try any of the following:

 $ bk changes -R                            # regular report
 $ bk changes -Rv                           # verbose report
 $ bk changes -Rv -nd':GFILE:' | sort -u    # unique list of changed files

If you decide that you want to update your clone with those changes, just run:

 $ bk pull

Since we're assuming you haven't edited anything in your clone yet, the pull should work. If, for some reason, you regret having done the pull, you can always:

 $ bk unpull