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.
TWiki recognises the following formats for date/time strings. For all strings the time is optional.
- 31 Dec 2001 - 23:59
- 2001/12/31 23:59:59
- 2001/12/31 23:59
2001-12-31T23:59:59 - ISO 8601 format
ISO dates may have a timezone specifier, either Z or a signed difference
in hh:mm format. For example:
Some features of TWiki, such as searches, permit the specification of time intervals
. A time interval is a period of time, such as "1337 to 1451" (the Hundred Years War) or "9th February 2005 to 26th March 2005" (the Christian season of Lent).
The recognised format is a restricted
interpretation of the ISO standard 8601
A string is accepted as a valid time interval string if it conforms to the following grammar:
interval ::= date
| date '/' date
| 'P' duration '/' date
| date '/' 'P' duration
date ::= year ('-' month ('-' day ('T' hour (':' minute (':' second)))))
duration ::= NUM unit
| duration NUM unit
unit ::= 'y' | 'm' | 'w' | 'd' | 'h' | 'M' | 'S'
year, month, day, hour, minute, second ::= NUM
An incompletely specified date will be completed by including as much time as possible.
For example, if the start of a date range is specified by just a year, e.g.
, it will be interpreted as starting at January 1st 1999, at zero hours zero minutes zero seconds. Similarly for the end of the range;
will be interpreted as the last second of 2006.
If only one date is specified (e.g. the interval string is
) it will be treated as if the same date were the start and the end i.e.
is interpreted as the whole of the year 1999.
| You write
|| You mean
|| the next 50 years
|| any second during the present day
|| any time in the year 2003
|| 12th Dec 2003, from 0:00 to 23:59:59
|| the first 20 weeks of the year 2003
| from March 28th to May 15th of the year 2003
| the whole year 2003
| three weeks until today
|| the last 24 hours
|| the last 20 weeks of the year 2003
|| today and yesterday
Further examples can be seen here
If you are entering a date at both ends of the time interval string, the end date must include all leading fields, even if these are the same as in the start date. This limitation forms a proper restriction to the ISO8601 standard. i.e. ISO8601 specifies that
means 12th Dec 2003 00:00 to 14th Dec 2003 23:59:59. However this shorthand is not supported by TWiki and must be written as