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 f149b7b758e9dfc42eb471a38038bcd3ce87db44 (commit) via 883b0dde946105e0910456a0bebb24d57fecb0fc (commit) from 9cba9c8585bc5ebf19bafece118fb2362090547c (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 f149b7b758e9dfc42eb471a38038bcd3ce87db44 Author: Miroslav Lichvar <mlich...@redhat.com> Date: Wed Jan 25 15:58:37 2023 +0100 examples: add AES keys to chrony.keys.example commit 883b0dde946105e0910456a0bebb24d57fecb0fc Author: Miroslav Lichvar <mlich...@redhat.com> Date: Wed Jan 25 14:29:06 2023 +0100 conf: warn if not having read-only access to keys After dropping root privileges, log a warning message if chronyd doesn't have read access or has (unnecessary) write access to the files containing symmetric and server NTS keys. ----------------------------------------------------------------------- Summary of changes: conf.c | 13 +++++++++++++ conf.h | 2 ++ examples/chrony.keys.example | 2 ++ main.c | 6 +++++- util.c | 11 +++++++++++ util.h | 4 ++++ 6 files changed, 37 insertions(+), 1 deletion(-) hooks/post-receive -- chrony/chrony.git -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.