Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

replaced NTPSec with chrony #121

Merged
merged 1 commit into from
Sep 13, 2023
Merged

replaced NTPSec with chrony #121

merged 1 commit into from
Sep 13, 2023

Conversation

svenrademakers
Copy link
Collaborator

NTPSec pulls in Python3 which eats up close to 50% of our rootfs partition. Chrony was picked for its lightweight characteristics. No further investigation is done on the exposure of chrony to NTP amplification attacks.

commit fixes #109

NTPSec pulls in Python3 which eats up close to 50% of our rootfs
partition. Chrony was picked for its lightweight characteristics. No
further investigation is done on the exposure of chrony to NTP
amplification attacks.

commit fixes #109
Copy link
Contributor

@ruslashev ruslashev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome. And I was afraid that a huge *.pyc collection was caused by a python version bump.

@@ -0,0 +1,4 @@
pool pool.ntp.org iburst
makestep 0.1 5
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why limit is 5? I am not very well-versed in terminology, but all examples suggest 3.

Same for driftfile -- all examples listed it.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • driftfile: I want to limit file writes to eMMC, As a consequence this means that there is a potential for the clock to drift during startup. This is mitigated by rtcsync option, were we put more emphasis on making the RTC ticks leading.
  • makestep: since we don't write a drift file i want to instruct chrony to be a bit more aggressive with syncing the time by allowing more steps to sync to the correct time

@svenrademakers svenrademakers merged commit ce92f84 into master Sep 13, 2023
1 check passed
@svenrademakers svenrademakers deleted the feature/chrony branch September 13, 2023 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Get rid of Python3 dependency
2 participants