r2 - 2007-11-24 - 04:17:30 - HarlanStennYou are here: NTP >  Dev Web > ReleaseIssues > BackroomEmail
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.

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.

Backroom Email

Requirements from UDel and Dave

whimsy is the only machine in the backroom flock that may accept incoming internet email.

Background, and (mutual) "nice to have" items

Dave generally works on deacon, the fastest machine in the backroom.

Harlan generally works on whimsy, a usefully fast machine.

Harlan tries to stay out of Dave's way.

When Dave runs a build, it would be Great if no auto* processes or the configure script needed to run.

Requirements from the Development and Release Engineering process

The development and release engineering process for NTP requires outgoing email from the master repository, currently on deacon.

Outgoing email is used for:

  • commit log messages
  • change log messages
  • delta emails
  • SCM trigger notifications
  • trigger tripwire notifications
  • commit "change diffs"

Sometimes NFS goes wonky in the backroom and Harlan has to to bk things on deacon, the machine that has the NTP sources on its local disk drives.

These bk operations need to send email.

If outgoing email will no longer be supported on deacon then we will need to have the NTP sources live locally on a machine that does support outgoing internet email.

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r2 < r1 | More topic actions
SSL security by CAcert
Get the CAcert Root Certificate
This site is powered by the TWiki collaboration platform
IPv6 Ready
Copyright & 1999-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding the site? Send feedback