[chrony-dev] [GIT] chrony/chrony.git branch master updated. 4.3-17-g7b97668 |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
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 7b97668319f9449b4adb1a978bb1fe9b0fb22e4d (commit)
via 6f5df7e4a437aca3014f2898ea65af5bd64acb39 (commit)
from 5a39074e01a654570d3b581ae5feda9f010fd8f2 (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 7b97668319f9449b4adb1a978bb1fe9b0fb22e4d
Author: Holger Hoffstätte <holger@xxxxxxxxxxxxxxxxxxxxxx>
Date: Wed Nov 9 09:17:14 2022 +0100
getdate: fix various warnings which will be errors with clang-16
These were found by Gentoo's QA while rebuilding the world with
clang-16: https://bugs.gentoo.org/880519
Signed-off-by: Holger Hoffstätte <holger@xxxxxxxxxxxxxxxxxxxxxx>
commit 6f5df7e4a437aca3014f2898ea65af5bd64acb39
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date: Mon Oct 24 16:14:35 2022 +0200
nts: warn if server started without ntsdumpdir
If an NTS server is configured without ntsdumpdir, keys will not be
saved and reloaded after restart, which will cause existing cookies
to be invalidated and can cause a short-term denial of service if
the server has so many clients that it cannot handle them all
making an NTS-KE session within one polling interval.
Log a warning message if a server key+certificate is specified without
ntsdumpdir.
-----------------------------------------------------------------------
Summary of changes:
getdate.y | 19 +++++++------------
nts_ke_server.c | 5 +++++
2 files changed, 12 insertions(+), 12 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.