]> git.ipfire.org Git - thirdparty/chrony.git/log
thirdparty/chrony.git
10 days agodoc: fix typo in README master
Rob Gill [Tue, 16 Apr 2024 01:00:30 +0000 (11:00 +1000)] 
doc: fix typo in README

Typo correction only - no change to content

Signed-off-by: Rob Gill <rrobgill@protonmail.com>
10 days agodoc: fix typo in chronyc docs
Rob Gill [Tue, 16 Apr 2024 00:52:22 +0000 (10:52 +1000)] 
doc: fix typo in chronyc docs

Typo fix only - no change to content

Signed-off-by: Rob Gill <rrobgill@protonmail.com>
10 days agontp: log failed connection to Samba signd socket
Miroslav Lichvar [Mon, 15 Apr 2024 14:19:06 +0000 (16:19 +0200)] 
ntp: log failed connection to Samba signd socket

Log an error message (in addition to the socket-specific debug message)
when the connection to signd socket fails, but only once before a
successful signd exchange to avoid flooding the system log.

2 weeks agodoc: add contributing.adoc
Miroslav Lichvar [Thu, 11 Apr 2024 10:54:26 +0000 (12:54 +0200)] 
doc: add contributing.adoc

2 weeks agotest: add --enable-debug option to 002-scanbuild
Miroslav Lichvar [Thu, 11 Apr 2024 10:53:01 +0000 (12:53 +0200)] 
test: add --enable-debug option to 002-scanbuild

2 weeks agoavoid some static analysis errors
Miroslav Lichvar [Thu, 11 Apr 2024 07:20:44 +0000 (09:20 +0200)] 
avoid some static analysis errors

Modify the code to avoid some false positives reported by the clang and
gcc static analyzers.

2 weeks agosys_linux: disable other external timestamping channels
Miroslav Lichvar [Wed, 10 Apr 2024 10:05:57 +0000 (12:05 +0200)] 
sys_linux: disable other external timestamping channels

Use new ioctls added in Linux 6.7 to disable receiving events from other
channels when enabling external timestamping on a PHC. This should save
some CPU time when other applications or chronyd instances are using
other channels of the same PHC.

2 weeks agorefclock: update comment in PHC driver
Miroslav Lichvar [Wed, 10 Apr 2024 10:02:50 +0000 (12:02 +0200)] 
refclock: update comment in PHC driver

Since Linux 6.7 external timestamping events are no longer shared among
all descriptors of a PHC. Each descriptor gets its own copy of each
timestamp.

3 weeks agocmdmon: add reserved fields to local command
Miroslav Lichvar [Thu, 4 Apr 2024 13:17:43 +0000 (15:17 +0200)] 
cmdmon: add reserved fields to local command

Add two reserved fields initialized to zero to the new REQ_LOCAL3
command to allow adding more options (e.g. delay in activation) without
changing the command number again.

3 weeks agotest: add tests of local directive options
Miroslav Lichvar [Thu, 4 Apr 2024 13:00:20 +0000 (15:00 +0200)] 
test: add tests of local directive options

3 weeks agoreference: add "local activate" option
Andy Fiddaman [Mon, 25 Mar 2024 19:05:52 +0000 (19:05 +0000)] 
reference: add "local activate" option

This option sets an activating root distance for the local reference. The
local reference will not be used until the root distance drops below the
configured value for the first time. This can be used to prevent the local
reference from being activated on a server which has never been synchronised
with an upstream server. The default value of 0.0 causes no activating
distance to be used, such that the local reference is always eligible for
activation.

3 weeks agoleapdb: fix leapsec list processing with 32-bit time_t
Miroslav Lichvar [Wed, 3 Apr 2024 09:01:44 +0000 (11:01 +0200)] 
leapdb: fix leapsec list processing with 32-bit time_t

A 32-bit time_t value overflows when converted to the Y1900 epoch used
in the leapsec list. Use a 64-bit variable in get_list_leap() to fix the
comparisons on systems using 32-bit time_t.

Fixes: 53823b9f1c07 ("leapdb: support leap-seconds.list as second source")
3 weeks agontp: add server support for KoD RATE
Miroslav Lichvar [Tue, 2 Apr 2024 13:25:51 +0000 (15:25 +0200)] 
ntp: add server support for KoD RATE

Add "kod" option to the ratelimit directive to respond with the KoD
RATE code to randomly selected requests exceeding the configured limit.
This complements the client support of KoD RATE. It's disabled by
default.

There can be only one KoD code in one response. If both NTS NAK and RATE
codes are triggered, drop the response. The KoD RATE code can be set in
an NTS-authenticated response.

3 weeks agoclientlog: add support for KoD rate limiting
Miroslav Lichvar [Tue, 2 Apr 2024 13:05:19 +0000 (15:05 +0200)] 
clientlog: add support for KoD rate limiting

Add a third return value to CLG_LimitServiceRate() to indicate the
server should send a response requesting the client to reduce its
polling rate. It randomly selects from a fraction (configurable to 1/2,
1/4, 1/8, 1/16, or disabled) of responses which would be dropped
(after selecting responses for the leak option).

3 weeks agoclientlog: return enum from CLG_LimitServiceRate()
Miroslav Lichvar [Tue, 2 Apr 2024 09:37:39 +0000 (11:37 +0200)] 
clientlog: return enum from CLG_LimitServiceRate()

Change CLG_LimitServiceRate() to return an enum in preparation for
adding KoD RATE support.

3 weeks agonts: check for NTS NAK specifically when responding
Miroslav Lichvar [Tue, 2 Apr 2024 09:33:04 +0000 (11:33 +0200)] 
nts: check for NTS NAK specifically when responding

Ignore other KoD codes than NTS NAK when deciding if the server response
should not be authenticated.

6 weeks agontp: avoid unnecessary restart of resolving round on refresh
Miroslav Lichvar [Thu, 14 Mar 2024 14:37:15 +0000 (15:37 +0100)] 
ntp: avoid unnecessary restart of resolving round on refresh

Don't call NSR_ResolveSources() when a resolving round is already
started. This cuts the number of calls of the system resolver made due
to the refresh command to half.

6 weeks agontp: don't keep refresh requests in list of unresolved sources
Miroslav Lichvar [Thu, 14 Mar 2024 14:32:28 +0000 (15:32 +0100)] 
ntp: don't keep refresh requests in list of unresolved sources

The refresh command adds requests to reresolve addresses of all sources.
If some sources didn't have an IP address resolved yet, the
corresponding requests were not removed after failed resolving. Repeated
refresh commands increased the number of requests and number of calls of
the system resolver, which might not be caching DNS responses.

Remove all refresh requests from the list after resolving attempt to fix
that.

Reported-by: t.barnewski@avm.de
Fixes: d7e3ad17ff7a ("ntp: create sources for unresolved addresses")
6 weeks agontp: add more debug messages for resolving
Miroslav Lichvar [Thu, 14 Mar 2024 14:09:09 +0000 (15:09 +0100)] 
ntp: add more debug messages for resolving

6 weeks agoconf: don't load sourcedir during initstepslew and RTC init
Miroslav Lichvar [Tue, 12 Mar 2024 13:30:27 +0000 (14:30 +0100)] 
conf: don't load sourcedir during initstepslew and RTC init

If the reload sources command was received in the chronyd start-up
sequence with initstepslew and/or RTC init (-s option), the sources
loaded from sourcedirs caused a crash due to failed assertion after
adding sources specified in the config.

Ignore the reload sources command until chronyd enters the normal
operation mode.

Fixes: 519796de3756 ("conf: add sourcedirs directive")
6 weeks agotest: replace another C99-style declaration in for loop
Miroslav Lichvar [Mon, 11 Mar 2024 10:59:11 +0000 (11:59 +0100)] 
test: replace another C99-style declaration in for loop

7 weeks agocmdmon: add offset command
Miroslav Lichvar [Thu, 7 Mar 2024 15:20:27 +0000 (16:20 +0100)] 
cmdmon: add offset command

Add a new command to modify the offset option of NTP sources and
reference clocks.

7 weeks agontp+refclock: add functions to modify offset option
Miroslav Lichvar [Thu, 7 Mar 2024 15:19:04 +0000 (16:19 +0100)] 
ntp+refclock: add functions to modify offset option

7 weeks agortc+getdate: initialize tm_wday for mktime()
Miroslav Lichvar [Mon, 4 Mar 2024 10:34:22 +0000 (11:34 +0100)] 
rtc+getdate: initialize tm_wday for mktime()

Even though mktime() is documented as ignoring the tm_wday field, the
coverity static analyzer complains about passing an uninitialized value.
Set the field to zero to make it happy.

7 weeks agotest: avoid C99-style declaration in for loop
Miroslav Lichvar [Mon, 12 Feb 2024 13:42:03 +0000 (14:42 +0100)] 
test: avoid C99-style declaration in for loop

This fixes compilation without the -std=c99 option with an older gcc.

2 months agoexamples: switch chrony.conf examples to leapseclist
Miroslav Lichvar [Thu, 8 Feb 2024 15:18:57 +0000 (16:18 +0100)] 
examples: switch chrony.conf examples to leapseclist

2 months agotest: improve 113-leapsecond and 124-tai tests
Miroslav Lichvar [Wed, 7 Feb 2024 14:48:43 +0000 (15:48 +0100)] 
test: improve 113-leapsecond and 124-tai tests

Use leapseclist instead of leapsectz and test also negative leap
seconds. Add a test for leapsectz when the date command indicates
right/UTC is available on the system and mktime() works as expected.
Check TAI offset in the server's log.

2 months agotest: add leapdb unit test
Patrick Oppenlander [Thu, 8 Feb 2024 03:36:29 +0000 (14:36 +1100)] 
test: add leapdb unit test

2 months agoleapdb: support leap-seconds.list as second source
Patrick Oppenlander [Thu, 8 Feb 2024 03:36:28 +0000 (14:36 +1100)] 
leapdb: support leap-seconds.list as second source

The existing implementation of getting leap second information from a
timezone in get_tz_leap() relies on non-portable C library behaviour.

Specifically, mktime is not required to return '60' in the tm_sec field
when a leap second is inserted leading to "Timezone right/UTC failed
leap second check, ignoring" errors on musl based systems.

This patch adds support for getting leap second information from the
leap-seconds.list file included with tzdata and adds a new configuration
directive leapseclist to switch on the feature.

2 months agoleapdb: move source check into separate function
Patrick Oppenlander [Thu, 8 Feb 2024 03:36:27 +0000 (14:36 +1100)] 
leapdb: move source check into separate function

The sanity checks are valid for all possible sources of leap second
information, so move them into a separate function check_leap_source().

2 months agoleapdb: make twice per day check logic common
Patrick Oppenlander [Thu, 8 Feb 2024 03:36:26 +0000 (14:36 +1100)] 
leapdb: make twice per day check logic common

We want to do the twice per day check regardless of the data source.
Move the check up one level from get_tz_leap() into LDB_GetLeap().

2 months agoreference: move leap second source into leapdb
Patrick Oppenlander [Thu, 8 Feb 2024 03:36:25 +0000 (14:36 +1100)] 
reference: move leap second source into leapdb

Separate out source of leap second data into a new module in preparation
for supporting more sources such as leap-seconds.list.

2 months agocmdmon: add timestamp counters to ntpdata report
Miroslav Lichvar [Tue, 6 Feb 2024 13:56:30 +0000 (14:56 +0100)] 
cmdmon: add timestamp counters to ntpdata report

2 months agontp: add per-source counters of kernel and hardware timestamps
Miroslav Lichvar [Tue, 6 Feb 2024 13:27:14 +0000 (14:27 +0100)] 
ntp: add per-source counters of kernel and hardware timestamps

2 months agocmdmon: add ipv4/ipv6 options to add source command
Miroslav Lichvar [Mon, 5 Feb 2024 13:43:03 +0000 (14:43 +0100)] 
cmdmon: add ipv4/ipv6 options to add source command

2 months agocmdmon: simplify flag checking in handle_add_source()
Miroslav Lichvar [Mon, 5 Feb 2024 13:38:51 +0000 (14:38 +0100)] 
cmdmon: simplify flag checking in handle_add_source()

2 months agoconf: add ipv4 and ipv6 options to server/pool/peer directive
Miroslav Lichvar [Mon, 5 Feb 2024 13:20:19 +0000 (14:20 +0100)] 
conf: add ipv4 and ipv6 options to server/pool/peer directive

Accept "ipv4" and "ipv6" options in the server/pool/peer directive to
use only IPv4 or IPv6 addresses respectively.

The configuration is different from the "server [-4|-6] hostname" syntax
supported by ntpd to avoid breaking existing scripts which expect the
hostname to always be the first argument of the directives.

2 months agontp: support per-source IP family restriction
Miroslav Lichvar [Mon, 5 Feb 2024 13:06:52 +0000 (14:06 +0100)] 
ntp: support per-source IP family restriction

Add a new parameter to the NSR_AddSourceByName() function to allow
individual sources to be limited to IPv4 or IPv6 addresses. This doesn't
change the options passed to the resolver. It's just an additional
filter in the processing of resolved addresses following the -4/-6
command-line option of chronyd.

3 months agontp: fix authenticated requests in serverstats
Miroslav Lichvar [Mon, 8 Jan 2024 10:35:56 +0000 (11:35 +0100)] 
ntp: fix authenticated requests in serverstats

Fix the CLG_UpdateNtpStats() call to count requests passing the
authentication check instead of requests triggering a KoD response
(i.e. NTS NAK).

4 months agoupdate copyright years 4.5
Miroslav Lichvar [Tue, 5 Dec 2023 13:14:00 +0000 (14:14 +0100)] 
update copyright years

4 months agodoc: update FAQ on improving accuracy
Miroslav Lichvar [Tue, 5 Dec 2023 12:54:44 +0000 (13:54 +0100)] 
doc: update FAQ on improving accuracy

4 months agodoc: mention dependency of net corrections on HW timestamping
Miroslav Lichvar [Tue, 5 Dec 2023 12:03:27 +0000 (13:03 +0100)] 
doc: mention dependency of net corrections on HW timestamping

4 months agodoc: improve description of reload sources command
Miroslav Lichvar [Mon, 4 Dec 2023 11:38:03 +0000 (12:38 +0100)] 
doc: improve description of reload sources command

4 months agosources: rework logging of selection loss
Miroslav Lichvar [Tue, 28 Nov 2023 10:28:03 +0000 (11:28 +0100)] 
sources: rework logging of selection loss

The commit 5dd288dc0cbd ("sources: reselect earlier when removing
selected source") didn't cover all paths that can lead to a missing log
message when all sources are removed.

Add a flag to track the loss of selection and postpone the log message
in transient states where no message is logged to avoid spamming in
normal operation. Call SRC_SelectSource() after removing the source
to get a log message if there are no (selectable) sources left.

Reported-by: Thomas Lange <thomas@corelatus.se>
5 months agodoc: update NEWS 4.5-pre1
Miroslav Lichvar [Wed, 22 Nov 2023 09:46:33 +0000 (10:46 +0100)] 
doc: update NEWS

5 months agodoc: update README
Miroslav Lichvar [Wed, 22 Nov 2023 09:34:59 +0000 (10:34 +0100)] 
doc: update README

5 months agodoc: replace foobar naming in examples
Miroslav Lichvar [Wed, 22 Nov 2023 09:29:01 +0000 (10:29 +0100)] 
doc: replace foobar naming in examples

5 months agodoc: update description of NTP over PTP in FAQ
Miroslav Lichvar [Wed, 22 Nov 2023 08:51:14 +0000 (09:51 +0100)] 
doc: update description of NTP over PTP in FAQ

5 months agodoc: mention version supporting socket activation in FAQ
Miroslav Lichvar [Wed, 22 Nov 2023 08:50:44 +0000 (09:50 +0100)] 
doc: mention version supporting socket activation in FAQ

5 months agodoc: improve ntstrustedcerts description
Miroslav Lichvar [Wed, 22 Nov 2023 09:19:53 +0000 (10:19 +0100)] 
doc: improve ntstrustedcerts description

5 months agodoc: improve cmdport description
Miroslav Lichvar [Wed, 22 Nov 2023 08:48:36 +0000 (09:48 +0100)] 
doc: improve cmdport description

5 months agosources: drop unreachable log message
Miroslav Lichvar [Tue, 21 Nov 2023 10:25:10 +0000 (11:25 +0100)] 
sources: drop unreachable log message

With forced reselection during source removal selected_source_index
can only be INVALID_SOURCE if there are no sources. The "Can't
synchronise: no sources" message couldn't be logged even before that as
SRC_ReselectSource() resets the index before calling SRC_SelectSource().

Replace the message with an assertion.

5 months agosources: reselect earlier when removing selected source
Miroslav Lichvar [Tue, 21 Nov 2023 10:10:23 +0000 (11:10 +0100)] 
sources: reselect earlier when removing selected source

When a selected source is being removed, reset the instance and rerun
the selection while the source is still marked as selected. This forces
a "Can't synchronise" message to be logged when all sources are removed.

Reported-by: Thomas Lange <thomas@corelatus.se>
5 months agosources: reselect after resetting selected source
Miroslav Lichvar [Tue, 21 Nov 2023 10:05:41 +0000 (11:05 +0100)] 
sources: reselect after resetting selected source

Avoid showing in the sources report a selected source which has no
samples (e.g. after replacement).

5 months agontp: allow reusing timestamps of unused samples
Miroslav Lichvar [Tue, 21 Nov 2023 08:28:40 +0000 (09:28 +0100)] 
ntp: allow reusing timestamps of unused samples

When switching from basic mode to interleaved mode following a response
which wasn't accumulated due to failed test A, B, C, or D, allow
timestamps of the failed sample to be reused in interleaved mode, i.e.
replacing the server's less accurate transmit timestamp with a more
accurate timestamp server can turn a failed sample into acceptable one.

Move the presend check into test A to simplify the code.

5 months agontp: fix presend in interleaved mode
Miroslav Lichvar [Tue, 21 Nov 2023 06:51:37 +0000 (07:51 +0100)] 
ntp: fix presend in interleaved mode

The presend option in interleaved mode uses two presend requests instead
of one to get an interleaved response from servers like chrony which
delay the first interleaved response due to an optimization saving
timestamps only for clients actually using the interleaved mode.

After commit 0ae6f2485b97 ("ntp: don't use first response in interleaved
mode") the first interleaved response following the two presend
responses in basic mode is dropped as the preferred set of timestamps
minimizing error in delay was already used by the second sample in
basic mode. There are only three responses in the burst and no sample is
accumulated.

Increasing the number of presend requests to three to get a fourth
sample would be wasteful. Instead, allow reusing timestamps of the
second presend sample in basic mode, which is never accumulated.

Reported-by: Aaron Thompson
Fixes: 0ae6f2485b97 ("ntp: don't use first response in interleaved mode")
5 months agonts: close reusable sockets in helper process
Miroslav Lichvar [Mon, 20 Nov 2023 12:34:59 +0000 (13:34 +0100)] 
nts: close reusable sockets in helper process

Close all reusable sockets when the NTS-KE server helper is forked. It
is not supposed to have access to any of the server sockets, just the
socket for getting requests from the main process and the syslog socket.

5 months agosocket: provide function for closing reusable sockets
Miroslav Lichvar [Mon, 20 Nov 2023 12:34:38 +0000 (13:34 +0100)] 
socket: provide function for closing reusable sockets

5 months agosocket: set close-on-exec on all reusable sockets
Miroslav Lichvar [Mon, 20 Nov 2023 12:25:27 +0000 (13:25 +0100)] 
socket: set close-on-exec on all reusable sockets

Set the CLOEXEC flag on all reusable sockets in the initialization to
avoid leaking them to sendmail (mailonchange directive) in case the
chrony configuration doesn't use all sockets provided by systemd.

5 months agodoc: add FAQ section on minimizing service downtime
Luke Valenta [Wed, 1 Nov 2023 20:40:35 +0000 (16:40 -0400)] 
doc: add FAQ section on minimizing service downtime

5 months agosocket: add support for systemd sockets
Luke Valenta [Thu, 26 Oct 2023 16:48:56 +0000 (12:48 -0400)] 
socket: add support for systemd sockets

Before opening new IPv4/IPv6 server sockets, chronyd will check for
matching reusable sockets passed from the service manager (for example,
passed via systemd socket activation:
https://www.freedesktop.org/software/systemd/man/latest/sd_listen_fds.html)
and use those instead.

Aside from IPV6_V6ONLY (which cannot be set on already-bound sockets),
the daemon sets the same socket options on reusable sockets as it would
on sockets it opens itself.

Unit tests test the correct parsing of the LISTEN_FDS environment
variable.

Add 011-systemd system test to test socket activation for DGRAM and
STREAM sockets (both IPv4 and IPv6).  The tests use the
systemd-socket-activate test tool, which has some limitations requiring
workarounds discussed in inline comments.

5 months agologging: move severity_chars to fix compiler warning
Luke Valenta [Tue, 7 Nov 2023 19:39:40 +0000 (14:39 -0500)] 
logging: move severity_chars to fix compiler warning

5 months agologging: add log severity to file log prefix when debug is enabled
Luke Valenta [Wed, 1 Nov 2023 20:32:45 +0000 (16:32 -0400)] 
logging: add log severity to file log prefix when debug is enabled

5 months agontp: initialize network correction of transmitted packets
Miroslav Lichvar [Thu, 2 Nov 2023 11:41:55 +0000 (12:41 +0100)] 
ntp: initialize network correction of transmitted packets

Initialize the unused value of network correction parsed from
own transmitted packets to avoid a use-of-uninitialized-value error
in NIO_UnwrapMessage() reported by clang.

Fixes: 6372a9f93f59 ("ntp: save PTP correction from NTP-over-PTP messages")
6 months agodoc: document '-L -1' option for debug logging output
Luke Valenta [Fri, 20 Oct 2023 15:54:41 +0000 (11:54 -0400)] 
doc: document '-L -1' option for debug logging output

7 months agontp: add client support for network correction
Miroslav Lichvar [Tue, 26 Sep 2023 10:52:39 +0000 (12:52 +0200)] 
ntp: add client support for network correction

If the network correction is known for both the request and response,
and their sum is not larger that the measured peer delay, allowing the
transparent clocks to be running up to 100 ppm faster than the client's
clock, apply the corrections to the NTP offset and peer delay. Don't
correct the root delay to not change the estimated maximum error.

7 months agontp: add server support for network correction
Miroslav Lichvar [Tue, 26 Sep 2023 10:39:25 +0000 (12:39 +0200)] 
ntp: add server support for network correction

Provide the network correction (PTP correction + RX duration) of the
request in the new extension field if included in the request and
NTP-over-PTP is enabled.

7 months agontp: add extension field to provide network correction
Miroslav Lichvar [Tue, 26 Sep 2023 10:30:10 +0000 (12:30 +0200)] 
ntp: add extension field to provide network correction

To be able to verify PTP corrections, the client will need to know both
the correction of the request received by the server and the correction
of the response. Add a new experimental NTP extension field that the
clients will use to request the correction and servers return the
value.

7 months agontp: save PTP correction from NTP-over-PTP messages
Miroslav Lichvar [Tue, 26 Sep 2023 10:22:47 +0000 (12:22 +0200)] 
ntp: save PTP correction from NTP-over-PTP messages

When the RX duration is known (HW timestamping), save the PTP correction
from received PTP messages in the local RX timestamp.

7 months agontp: extend local timestamp for PTP correction
Miroslav Lichvar [Tue, 26 Sep 2023 10:14:56 +0000 (12:14 +0200)] 
ntp: extend local timestamp for PTP correction

Add two new fields to the NTP_Local_Timestamp structure:
- receive duration as the time it takes to receive the ethernet frame,
  currently known only with HW timestamping
- network correction as a generalized PTP correction

The PTP correction is provided by transparent clocks in the correction
field of PTP messages to remove the receive, processing and queueing
delays of network switches and routers. Only one-step end-to-end unicast
transparent clocks are useful for NTP-over-PTP. Two-step transparent
clocks use follow-up messages and peer-to-peer transparent clocks don't
handle delay requests.

The RX duration will be included in the network correction to compensate
for asymmetric link speeds of the server and client as the NTP RX
timestamp corresponds to the end of the reception (in order to
compensate for the asymmetry in the normal case when no corrections
are applied).

7 months agontp: add function for detection of experimental fields
Miroslav Lichvar [Thu, 21 Sep 2023 09:02:24 +0000 (11:02 +0200)] 
ntp: add function for detection of experimental fields

7 months agontp: assert size of exp_mono_root field
Miroslav Lichvar [Tue, 12 Sep 2023 12:03:50 +0000 (14:03 +0200)] 
ntp: assert size of exp_mono_root field

7 months agontp: rename exp1 extension field
Miroslav Lichvar [Tue, 12 Sep 2023 10:19:03 +0000 (12:19 +0200)] 
ntp: rename exp1 extension field

Rename the exp1 extension field to exp_mono_root (monotonic timestamp +
root delay/dispersion) to better distinguish it from future experimental
extension fields.

7 months agoutil: add conversion between intervals and NTP 64-bit format
Miroslav Lichvar [Thu, 21 Sep 2023 12:02:11 +0000 (14:02 +0200)] 
util: add conversion between intervals and NTP 64-bit format

This will be needed to save PTP correction in NTP timestamp format.

7 months agodoc: don't require same version for experimental features
Miroslav Lichvar [Tue, 26 Sep 2023 10:12:14 +0000 (12:12 +0200)] 
doc: don't require same version for experimental features

7 months agoconfigure: prefer gnutls over nss and tomcrypt for hashing
Miroslav Lichvar [Tue, 12 Sep 2023 08:36:23 +0000 (10:36 +0200)] 
configure: prefer gnutls over nss and tomcrypt for hashing

Reorder the tests in the configure script to prefer gnutls over nss and
tomcrypt as its support includes AES-CMAC.

7 months agoconfigure: don't try AES-SIV-CMAC in nettle when disabled
Miroslav Lichvar [Tue, 12 Sep 2023 08:19:09 +0000 (10:19 +0200)] 
configure: don't try AES-SIV-CMAC in nettle when disabled

Avoid confusing message when --without-nettle is specified.

7 months agosiv: add support for AES-GCM-SIV in gnutls
Miroslav Lichvar [Tue, 12 Sep 2023 08:18:01 +0000 (10:18 +0200)] 
siv: add support for AES-GCM-SIV in gnutls

Add support for AES-128-GCM-SIV in the current development code of
gnutls. There doesn't seem to be an API to get the cipher's minimum and
maximum nonce length and it doesn't check for invalid lengths. Hardcode
and check the limits in chrony for now.

7 months agoconf: improve log message for failed additions in sources reload
Miroslav Lichvar [Mon, 11 Sep 2023 14:14:53 +0000 (16:14 +0200)] 
conf: improve log message for failed additions in sources reload

Describe the error status in the log message when adding a source from
sourcedir failed.

7 months agoconf: cast subtraction operands in source comparison
Miroslav Lichvar [Mon, 11 Sep 2023 13:58:17 +0000 (15:58 +0200)] 
conf: cast subtraction operands in source comparison

Cast the values to int to not break the sorting in case they are changed
to unsigned types.

7 months agoconf: fix reloading modified sources specified by IP address
Miroslav Lichvar [Mon, 11 Sep 2023 13:29:04 +0000 (15:29 +0200)] 
conf: fix reloading modified sources specified by IP address

When reloading a modified source from sourcedir which is ordered before
the original source (e.g. maxpoll was decreased), the new source is
added before the original one is removed. If the source is specified by
IP address, the addition fails due to the conflict with the original
source. Sources specified by hostname don't conflict. They are resolved
later (repeatedly if the resolver provides only conflicting addresses).

Split the processing of sorted source lists into two phases, so all
modified sources are removed before they are added again to avoid the
conflict.

Reported-by: Thomas Lange <thomas@corelatus.se>
8 months agodoc: update NEWS and README 4.4
Miroslav Lichvar [Wed, 9 Aug 2023 13:20:55 +0000 (15:20 +0200)] 
doc: update NEWS and README

8 months agosocket: enable nanosecond resolution RX timestamp on FreeBSD
Josef 'Jeff' Sipek [Wed, 9 Aug 2023 11:58:38 +0000 (07:58 -0400)] 
socket: enable nanosecond resolution RX timestamp on FreeBSD

FreeBSD allows switching the receive timestamp format to struct timespec by
setting the SO_TS_CLOCK socket option to SO_TS_REALTIME after enabling
SO_TIMESTAMP.  If successful, the kernel then starts adding SCM_REALTIME
control messages instead of SCM_TIMESTAMP.

8 months agotest: make 139-nts more reliable
Miroslav Lichvar [Tue, 8 Aug 2023 15:11:46 +0000 (17:11 +0200)] 
test: make 139-nts more reliable

8 months agotest: make 114-presend more reliable
Miroslav Lichvar [Tue, 8 Aug 2023 14:21:39 +0000 (16:21 +0200)] 
test: make 114-presend more reliable

Avoid frequently ending in the middle of a client/server exchange with
long delays. This changed after commit 4a11399c2ebb ("ntp: rework
calculation of transmit timeout").

8 months agontp: don't require previous HW TX timestamp to wait for another
Miroslav Lichvar [Tue, 8 Aug 2023 13:44:25 +0000 (15:44 +0200)] 
ntp: don't require previous HW TX timestamp to wait for another

Clients sockets are closed immediately after receiving valid response.
Don't wait for the first early HW TX timestamp to enable waiting for
late timestamps. It may take a long time or never come if the HW/driver
is consistently slow. It's a chicken and egg problem.

Instead, simply check if HW timestamping is enabled on at least one
interface. Responses from NTP sources on other interfaces will always be
saved (for 1 millisecond by default).

8 months agontp: fix adding noselect to selection options
Miroslav Lichvar [Mon, 7 Aug 2023 12:52:01 +0000 (14:52 +0200)] 
ntp: fix adding noselect to selection options

If noselect is present in the configured options, don't assume it
cannot change and the effective options are equal. This fixes chronyc
selectopts +noselect command.

Fixes: 38777348143e ("sources: add function to modify selection options")
8 months agocontrib: replace tuxfamily with chrony-project
Bryan Christianson [Thu, 27 Jul 2023 23:16:00 +0000 (11:16 +1200)] 
contrib: replace tuxfamily with chrony-project

The chrony project has moved from tuxfamily.org to chrony-project.org.
Reflect these changes in the macOS startup files and documentation.

9 months agodoc: update links to chrony website
Miroslav Lichvar [Wed, 26 Jul 2023 14:36:39 +0000 (16:36 +0200)] 
doc: update links to chrony website

9 months agodoc: don't mention mailing lists in README
Miroslav Lichvar [Wed, 26 Jul 2023 14:32:28 +0000 (16:32 +0200)] 
doc: don't mention mailing lists in README

Current information about mailing lists is available on the project's
website.

9 months agoupdate copyright years
Miroslav Lichvar [Thu, 20 Jul 2023 10:57:33 +0000 (12:57 +0200)] 
update copyright years

9 months agodoc: add more questions to FAQ
Miroslav Lichvar [Thu, 20 Jul 2023 08:59:05 +0000 (10:59 +0200)] 
doc: add more questions to FAQ

9 months agodoc: fix typo in FAQ
Miroslav Lichvar [Thu, 20 Jul 2023 08:58:54 +0000 (10:58 +0200)] 
doc: fix typo in FAQ

9 months agodoc: refer to root distance in chronyc sources report
Miroslav Lichvar [Wed, 28 Jun 2023 12:53:09 +0000 (14:53 +0200)] 
doc: refer to root distance in chronyc sources report

9 months agotest: make 132-logchange more reliable
Miroslav Lichvar [Tue, 18 Jul 2023 13:16:03 +0000 (15:16 +0200)] 
test: make 132-logchange more reliable

9 months agotest: make 148-replacement more reliable
Miroslav Lichvar [Tue, 18 Jul 2023 13:15:45 +0000 (15:15 +0200)] 
test: make 148-replacement more reliable

9 months agotest: improve ntp_sources unit test
Miroslav Lichvar [Tue, 18 Jul 2023 11:08:40 +0000 (13:08 +0200)] 
test: improve ntp_sources unit test

9 months agontp: handle negotiated NTS-KE server in refreshment
Miroslav Lichvar [Mon, 17 Jul 2023 14:22:19 +0000 (16:22 +0200)] 
ntp: handle negotiated NTS-KE server in refreshment

When refreshing a source, compare the newly resolved addresses with the
originally resolved address instead of the current address to avoid
unnecessary replacements when the address is changed due to the NTS-KE
server negotiation.

9 months agonts: fix log severity for loaded server keys
Miroslav Lichvar [Tue, 11 Jul 2023 15:35:46 +0000 (17:35 +0200)] 
nts: fix log severity for loaded server keys

9 months agomakefile: compile getdate.o with -fwrapv option
Miroslav Lichvar [Mon, 26 Jun 2023 11:20:22 +0000 (13:20 +0200)] 
makefile: compile getdate.o with -fwrapv option

The getdate code (copied from gnulib before it was switched to GPLv3)
has multiple issues with signed integer overflows. Use the -fwrapv
compiler option for this object to at least make the operations defined.