[chrony-dev] [GIT] chrony/chrony.git branch master updated. 4.1-67-g17e6258

[<git@xxxxxxxxxxxxx>]

This is an automated email from git. It was generated because a ref
change was pushed to the "chrony/chrony.git" repository.

The branch, master has been updated
       via  17e6258694e0b612bc59851c5a289631a869b0ac (commit)
       via  d7a444593fb9469b224cd656dc052b2d0ed51ce7 (commit)
       via  701b9415a506c11f9fd993bba6f25211a3235ffa (commit)
       via  d5894c073812e18ab8358cda0a7dcf4afd81d79c (commit)
       via  a0a9560258cef3fa7dcd16e5f24eb087867641a0 (commit)
       via  09067e06d386b25f3c841dcae32b1d8602d46742 (commit)
      from  dbbdd5af0661bdbe51c0d35e5c93668275b5b60a (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 17e6258694e0b612bc59851c5a289631a869b0ac
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date:   Tue Nov 23 16:05:16 2021 +0100

    doc: update FAQ

commit d7a444593fb9469b224cd656dc052b2d0ed51ce7
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date:   Wed Nov 24 15:05:15 2021 +0100

    ntp: improve check for PTP socket
    
    Check for INVALID_SOCK_FD in case the PTP port is enabled, but opening
    one of the PTP sockets failed.

commit 701b9415a506c11f9fd993bba6f25211a3235ffa
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date:   Wed Nov 24 12:10:46 2021 +0100

    test: update 110-chronyc test

commit d5894c073812e18ab8358cda0a7dcf4afd81d79c
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date:   Tue Nov 23 14:41:08 2021 +0100

    main: add assertions for timespec signedness
    
    Some of the code (e.g. util and clientlog) may work with negative
    values. Require that time_t and the tv_nsec types are signed. This seems
    to be the case on all supported systems, but it it is not required by
    POSIX.

commit a0a9560258cef3fa7dcd16e5f24eb087867641a0
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date:   Tue Nov 23 13:17:26 2021 +0100

    util: reset GetRandom functions in helpers after fork
    
    Close /dev/urandom and drop cached getrandom() data after forking helper
    processes to avoid them getting the same sequence of random numbers
    (e.g. two NTS-KE helpers generating cookies with identical nonces).
    arc4random() is assumed to be able to detect forks and reseed
    automatically.
    
    This is not strictly necessary with the current code, which does not use
    the GetRandom functions before the NTS-KE helper processes are forked,
    but that could change in future.
    
    Also, call the reset function before exit to close /dev/urandom in order
    to avoid valgrind reporting the file object as "still reachable".

commit 09067e06d386b25f3c841dcae32b1d8602d46742
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date:   Tue Nov 23 10:35:22 2021 +0100

    ntp: fix exp1 EF search in process_response()
    
    Don't ignore the magic field when searching for the exp1 extension
    field in a received response. If there were two exp1 fields in the
    packet, and only one of them had the expected magic value, it should
    pick the right one.
    
    Fixes: 2319f72b29a9 ("ntp: add client support for experimental extension field")

-----------------------------------------------------------------------

Summary of changes:
 doc/faq.adoc                | 17 ++++++++++++++++-
 main.c                      |  9 +++++++++
 ntp_core.c                  |  4 +++-
 ntp_io.c                    |  3 ++-
 nts_ke_server.c             |  4 ++++
 privops.c                   |  2 ++
 test/simulation/110-chronyc |  2 +-
 test/unit/util.c            | 10 ++++++++++
 util.c                      | 35 ++++++++++++++++++++++++++---------
 util.h                      |  4 ++++
 10 files changed, 77 insertions(+), 13 deletions(-)


hooks/post-receive
-- 
chrony/chrony.git

-- 
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.