[Git][NTPsec/ntpsec][master] 2 commits: Tweaks to buildprep for FreeBSD and Alpine
Hal Murray (@hal.murray)
gitlab at mg.gitlab.com
Sun Mar 30 19:52:34 UTC 2025
Hal Murray pushed to branch master at NTPsec / ntpsec
Commits:
bb938256 by Hal Murray at 2025-03-30T12:51:45-07:00
Tweaks to buildprep for FreeBSD and Alpine
- - - - -
d9afd462 by Hal Murray at 2025-03-30T12:51:45-07:00
Doc tweaks for ntpd and assoc
Drop Broadcast and Multicast
Drop Symmetric Active/Passive
Needs more work
- - - - -
3 changed files:
- buildprep
- docs/assoc.adoc
- docs/includes/ntpd-body.adoc
Changes:
=====================================
buildprep
=====================================
@@ -176,12 +176,11 @@ daemon () {
case $installer in
apk)
# Alpine Linux
- $install build-base python # basic tools
- $install bison "python${PYVERS}-dev" linux-headers
+ $install build-base python3 # basic tools
+ $install bison python3-dev linux-headers
$install openssl-dev libcap-dev libseccomp-dev
- # probably needs more, but this builds
- # can't find timepps.h: gpsd and chrony have their own ??
- echo "Last tested a long time ago"
+ $install pps-tools pps-tools-dev
+ echo "Last tested: Alpine 3.21.3, March 2025"
;;
apt)
# Debian and derivatives
@@ -224,7 +223,8 @@ daemon () {
;;
pkg)
# FreeBSD
- $install bison python3
+ $install bison python3 # python3 => python3.xx
+ $install python # python => python3
# certificates for NTS
$install ca_root_nss
echo "Last tested: FreeBSD 14.2, March 2025"
=====================================
docs/assoc.adoc
=====================================
@@ -19,9 +19,7 @@ include::includes/hand.adoc[]
* link:#modes[Association Modes]
* link:#client[Client/Server Mode]
-* link:#symact[Symmetric Active/Passive Mode]
-* link:#broad[Broadcast/Multicast Modes]
-* link:#many[Manycast Mode]
+* link:#pool[Pool Mode]
* link:#poll[Poll Interval Management]
* link:#burst[Burst Options]
@@ -77,60 +75,8 @@ the default minimum and maximum values. The +minpoll+ and +maxpoll+
options can be used to bracket the range. Unless noted otherwise, these
options should not be used with reference clock drivers.
-[[symact]]
-== Symmetric Active/Passive Mode
-
-Symmetric active/passive mode is intended for configurations where a
-clique of low-stratum peers operate as mutual backups for each other.
-Each peer operates with one or more primary reference sources, such as a
-reference clock, or a set of secondary (stratum 2) servers known to be
-reliable and authentic. Should one of the peers lose all reference
-sources or simply cease operation, the other peers will automatically
-reconfigure so that time and related values can flow from the surviving
-peers to all hosts in the subnet. In some contexts this would be
-described as a "push-pull" operation, in that the peer either pulls or
-pushes the time and related values depending on the particular
-configuration.
-
-A symmetric active peer sends a symmetric active (mode 1) message to a
-designated peer. If a matching configured symmetric active association
-is found, the designated peer returns a symmetric active message. If no
-matching association is found, the designated peer mobilizes an ephemeral
-symmetric passive association and returns a symmetric passive (mode 2)
-message. Since an intruder can impersonate a symmetric active peer and
-cause a spurious symmetric passive association to be mobilized,
-symmetric passive mode should always be cryptographically validated.
-
-Due to unresolvable security issues with symmetric mode, NTPsec
-includes only partial support for it. The deprecated +peer+ directive
-which formerly set up a symmetric active association is now a synonym
-for +server+. Servers which receive symmetric active messages will
-immediately reply with symmetric passive responses without setting up
-any new association; essentially they treat such messages exactly
-like client-mode messages, aside from putting a different mode number
-into the response.
-
-[[broad]]
-== Broadcast/Multicast Modes
-
-These modes cannot be effectively secured and are deprecated in
-NTPsec. Client-mode support has been removed; server-side support
-is retained for backward compatibility but may be removed in a
-future release.
-
-NTP broadcast modes are intended for configurations
-involving one or a few servers and a possibly very large client
-population. Broadcast mode can be used with Ethernet, FDDI and WiFi
-spans interconnected by hubs or switches. Ordinarily, broadcast packets
-do not extend beyond a router.
-
-A server is configured to send broadcast messages using the
-+broadcast+ command and specifying the subnet address for broadcast.
-
-[[many]]
-== Manycast and Pool Modes
-
-Manycast is no longer supported by NTPsec.
+[[pool]]
+== Pool Mode
For more information on pool mode, see the
link:discover.html[Automatic Server Discovery Schemes] page.
=====================================
docs/includes/ntpd-body.adoc
=====================================
@@ -567,9 +567,15 @@ RFC 1119::
RFC 1305::
David L. Mills, _Network Time Protocol (Version 3)_
+RFC 1589::
+ David L. Mills, _A Kernel Model for Precision Timekeeping_
+
RFC 2030::
D.{empty} Mills, _Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI_
+RFC 2783::
+ J.{empty} Mogul and D. Mills and J. Brittenson and J. Stone and U. Windl, _Pulse-Per-Second API for UNIX-like Operating Systems, Version 1.0_
+
RFC 5905::
David L. Mills and J. Martin, Ed. and J. Burbank and W. Kasch, _Network
Time Protocol Version 4: Protocol and Algorithms Specification_
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/-/compare/9b10e28c9219a8f6435c37e5da610ea6a76647b8...d9afd462a14747bdc584bcff3e6e3569de8cea6c
--
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/-/compare/9b10e28c9219a8f6435c37e5da610ea6a76647b8...d9afd462a14747bdc584bcff3e6e3569de8cea6c
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/vc/attachments/20250330/7e54e8dd/attachment-0001.htm>
More information about the vc
mailing list