Fincer
/
openntpd-openbsd
mirror of https://github.com/Fincer/openntpd-openbsd
1
0
Fork 0
Code Issues 0 Projects 0 Releases 61 Wiki Activity
Source code pulled from OpenBSD for OpenNTPD. The place to contribute to this code is via the OpenBSD CVS tree.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
8734 Commits
49 Branches
13 MiB
Tree: 1f569ed8b2
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '1f569ed8b2'
${ noResults }
openntpd-openbsd/src/etc/ntpd.conf

11 lines
362 B
Raw Normal View History

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.
4 years ago
Drop comments; we already have a fully documented file under /etc/examples/ntpd.conf ok deraadt@ benno@ schwarze@
9 years ago
​
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
9 years ago
​
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
5 years ago
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
9 years ago
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.
4 years ago
​
​
​
 
  1. # $OpenBSD: ntpd.conf,v 1.16 2019/11/06 19:04:12 deraadt Exp $
  2. #
  3. # See ntpd.conf(5) and /etc/examples/ntpd.conf
  4. 

  5. servers pool.ntp.org
  6. server time.cloudflare.com
  7. sensor *
  8. 

  9. constraint from "9.9.9.9"              # quad9 v4 without DNS
  10. constraint from "2620:fe::fe"          # quad9 v6 without DNS
  11. constraints from "www.google.com"      # intentionally not 8.8.8.8