|[chrony-users] chrony and recent vulnerabilities in ntpd|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
For anyone wondering about this and the other vulnerabilities that
were recently fixed in ntpd, I think none of them are in chronyd. Here
are some comments.
As a client, chronyd does supports KoD RATE packets and it sets the
minimum polling interval, but it doesn't accept spoofed replies. Also,
the source port is random since chrony-1.30, which would make the
attack more difficult.
As a server, chronyd doesn't support rate limiting or KoD RATE.
As for the clock stepping issue, chronyd by default doesn't do any
steps from network, only the makestep and initstepslew directives
allow that. The makestep directive works as described, it allows the
clock to be stepped only in the number of updates that was specified.
Allowing chronyd to always step using the -1 limit is not recommended.
If you know your clock can't be wildly off after start, it's
recommended to not use makestep at all. At worst, a MITM attacker can
speed up or slow down your clock by 10%.
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.