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 51172b3510e5cc36b27fd3a5170d598585b84806 (commit)
via 892636036a54a3f0df779b6558e943b97f9b30c5 (commit)
via
This is an automated email from git. It was generated because a ref
change was pushed to the "chrony/chrony.git" repository.
The annotated tag, 3.5.1 has been created
at 571a7971cad5537a0e98a3c90aa0b02f5d047c3f (tag)
tagging 04328ceeadf7e2b68f246cb4deab9348f4e02825 (commit)
This is an automated email from git. It was generated because a ref
change was pushed to the "chrony/chrony.git" repository.
The branch, 3.5-stable has been created
at 04328ceeadf7e2b68f246cb4deab9348f4e02825 (commit)
- Log
chrony-3.5.1 is now available. It fixes a security issue in writing of
the pidfile.
The source code can be downloaded here:
https://download.tuxfamily.org/chrony/chrony-3.5.1.tar.gz
SHA256 sum:
1ba82f70db85d414cd7420c39858e3ceca4b9eb8b028cbe869512c3a14a2dca7
Changes since version 3.5:
Security
David, thanks for the feedback
> On 29/07/2020, at 12:28 AM, David Bohman wrote:
>
> Why is disabling SIP not an option, at least temporarily? It seems to me that
> you need to replace the timed service in order to use chronyd at all. You
> cannot have two daemons running at the same time who
