Perform contraint validation against 9.9.9.9 and 2620:fe::fe also (which
avoids DNS lookups entirely, but yes this https is correctly validated)
long discussions with otto, florian, and the quad9 crew.

add server time.cloudflare.com.
- Cloudflare have very good adjacency (if PCH did anycast ntp, we'd use it)
- As ntp input, it is great they don't leapsmear
- Not all their nodes do ntp, hope they succeed at scaling that up
- ntpd constrains (un-auth) ntp packets within a TLS constraint window
so there is no downside (unlike pool.ntp entries which slowly decay
but that's a story for another commit..)
ok otto

Drop comments; we already have a fully documented file under
/etc/examples/ntpd.conf

ok deraadt@ benno@ schwarze@

enable ntpd by default at install time. We use pools and a reliable
constraint to keep them in check. in the worst case of being on a
dark net, nothing changes.

this is being enabled by default to allow gathering of more operational
information from users. and if the operational heuristics in ntpd can be
suitable refined, this may stay the default into the future. if not, ntpd
will become even more awesome along the way.

with reyk rpe

- move the ntpd.conf file to examples directory
- move it from BIN1 to EXAMPLES in src/etc/Makefile
- change the installer to create the file instead of editing it
- add a '+' to the corresponding changelist entry

suggested by and OK deraadt@
OK for the installer change krw@

more precise comment for sensor *; ok henning@ jmc@

change comment for pool.ntp.org: not fixed to 8 servers and not just
stratum 2. ok henning@

show examples for sensors. use nmea as suggested by mbalmer, henning agrees.

update URL for pool servers
From: Pierre Riteau <pierre.riteau@free.fr>

since we have both the server and the servers keyword we ought to
provide an example for a single server as well...

Adresses->Addresses

it is "servers" now for pool.ntp.org

better defaults; ok henning

make this a reasonable default; don't listen anywhere and sync to
pool.ntp.org. Give some commented out examples tho.

server spec takes hostnames now, default to pool.ntp.org

sample ntpd config file

add server time.cloudflare.com.
- Cloudflare have very good adjacency (if PCH did anycast ntp, we'd use it)
- As ntp input, it is great they don't leapsmear
- Not all their nodes do ntp, hope they succeed at scaling that up
- ntpd constrains (un-auth) ntp packets within a TLS constraint window
so there is no downside (unlike pool.ntp entries which slowly decay
but that's a story for another commit..)
ok otto

Drop comments; we already have a fully documented file under
/etc/examples/ntpd.conf

ok deraadt@ benno@ schwarze@

enable ntpd by default at install time. We use pools and a reliable
constraint to keep them in check. in the worst case of being on a
dark net, nothing changes.

this is being enabled by default to allow gathering of more operational
information from users. and if the operational heuristics in ntpd can be
suitable refined, this may stay the default into the future. if not, ntpd
will become even more awesome along the way.

with reyk rpe

- move the ntpd.conf file to examples directory
- move it from BIN1 to EXAMPLES in src/etc/Makefile
- change the installer to create the file instead of editing it
- add a '+' to the corresponding changelist entry

suggested by and OK deraadt@
OK for the installer change krw@

more precise comment for sensor *; ok henning@ jmc@

change comment for pool.ntp.org: not fixed to 8 servers and not just
stratum 2. ok henning@

show examples for sensors. use nmea as suggested by mbalmer, henning agrees.

update URL for pool servers
From: Pierre Riteau <pierre.riteau@free.fr>

since we have both the server and the servers keyword we ought to
provide an example for a single server as well...

Adresses->Addresses

it is "servers" now for pool.ntp.org

better defaults; ok henning

make this a reasonable default; don't listen anywhere and sync to
pool.ntp.org. Give some commented out examples tho.

server spec takes hostnames now, default to pool.ntp.org

sample ntpd config file

Drop comments; we already have a fully documented file under
/etc/examples/ntpd.conf

ok deraadt@ benno@ schwarze@

enable ntpd by default at install time. We use pools and a reliable
constraint to keep them in check. in the worst case of being on a
dark net, nothing changes.

this is being enabled by default to allow gathering of more operational
information from users. and if the operational heuristics in ntpd can be
suitable refined, this may stay the default into the future. if not, ntpd
will become even more awesome along the way.

with reyk rpe

- move the ntpd.conf file to examples directory
- move it from BIN1 to EXAMPLES in src/etc/Makefile
- change the installer to create the file instead of editing it
- add a '+' to the corresponding changelist entry

suggested by and OK deraadt@
OK for the installer change krw@

more precise comment for sensor *; ok henning@ jmc@

change comment for pool.ntp.org: not fixed to 8 servers and not just
stratum 2. ok henning@

show examples for sensors. use nmea as suggested by mbalmer, henning agrees.

update URL for pool servers
From: Pierre Riteau <pierre.riteau@free.fr>

since we have both the server and the servers keyword we ought to
provide an example for a single server as well...

Adresses->Addresses

it is "servers" now for pool.ntp.org

better defaults; ok henning

make this a reasonable default; don't listen anywhere and sync to
pool.ntp.org. Give some commented out examples tho.

server spec takes hostnames now, default to pool.ntp.org

sample ntpd config file