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.
There's one more thing you might want to do if you're part of a larger group that wants to experiment with bitkeeper on the same remote, parent repository and that's to make your own local tracking repository
. A tracking repository (and I'm hoping I'm using the terminology correctly) is just a clone of the remote repo of interest, from which you'll make additional
local clones. It's just an extra level of clone so that you always have a local, good, undamaged copy of the remote repo, just in case you make a mess of yours.
As an example of setting up a tracking repo and a local repo off of that:
$ bk clone http://linux.bkbits.net:8080/linux-2.5 # tracking repo
$ cd <somewhere else>
$ bk clone file:///<absolute path to tracking repo> <dirname>
You now have your own copy of the repo that you can trash to your heart's content, and which you can delete and reclone at will.
To keep up to date, you'll run
- Update the tracking repo.
- Update your local repo off of that.
Note that you don't need to do any checkouts in the tracking repo; just leave everything in the SCCS-managed directories in that repo and do the checkouts in your local clone. In the simplest case, the only
things you'll ever do with the tracking repo is update it, and update from
it, at least for now.