Code Read the original on Omgubuntu 2 min read 0

Canonical funds Rust rewrite of NTP for Ubuntu time sync

Canonical has announced plans to transition Ubuntu to a new time synchronization client powered by the Rust programming language. By becoming a Gold Sponsor of the Trifecta Tech Foundation, the company will provide 40,000 euros in annual funding to develop ntpd-rs. This initiative aims to replace existing tools like Chrony and gpsd with a memory-safe alternative starting with Ubuntu 27.04, prioritizing system security and long-term stability for Linux users.

#Ubuntu #Rust #Canonical #Cybersecurity #Networking
Стилізований білий годинник із чорною та червоною стрілками і логотипом мови програмування Rust на жовтому технологічному фоні.
Стилізований білий годинник із чорною та червоною стрілками і логотипом мови програмування Rust на жовтому технологічному фоні. · Image source: Omgubuntu

According to Omgubuntu, Canonical is moving forward with an ambitious plan to integrate ntpd-rs, a Rust-based rewrite of the Network Time Protocol (NTP), as the default time synchronization client for Ubuntu. To facilitate this transition, the company has committed 40,000 euros in annual funding to the Trifecta Tech Foundation, a non-profit organization dedicated to developing memory-safe software projects.

Timeline for Rust integration

The rollout of ntpd-rs is scheduled to occur in phases across upcoming Ubuntu releases. The new client will first be made available for testing in Ubuntu 26.10, which is slated for release in October. Following the testing phase, Canonical intends for ntpd-rs to become the primary time sync client and server by the launch of Ubuntu 27.04.

The transition is designed to be comprehensive, eventually replacing several existing utilities including:

  • Chrony
  • linuxptp
  • gpsd

Security and memory safety goals

While the underlying mechanism of checking in with internet time servers remains unchanged, the shift to Rust is driven by a desire for enhanced security. Ubuntu previously updated its time sync stack in version 25.10 by replacing systemd-timesyncd with Chrony and adding Network Time Security (NTS). The move to ntpd-rs continues this trend of hardening the operating system against vulnerabilities.

The Trifecta Tech Foundation chair, Erik Jonkers, noted that the funding will support long-term reliability and the development of necessary components like AppArmor rules. This partnership builds on a successful history between Canonical and the foundation, which previously co-sponsored the development of sudo-rs. That project was adopted as the system default in Ubuntu 25.10 and carried over to the 26.04 LTS release.

The broader 'oxidation' strategy

Jon Seager, Ubuntu VP of Engineering at Canonical, stated that the company is "excited to deepen our already productive relationship with the Trifecta Tech Foundation to make these transitions viable for the wider ecosystem." This move aligns with Ubuntu’s broader strategy to "oxidize" the distribution by replacing legacy C-based components with Rust. Although the change will be largely invisible to the average user, Canonical views the investment as a necessary step toward providing a more stable and secure foundation for its users.

FAQ

When will ntpd-rs be released on Ubuntu?
The new Rust-based time synchronization client will be available for testing in Ubuntu 26.10, which is scheduled for release in October. It is intended to become the primary time sync client and server by the launch of Ubuntu 27.04.
Why is Canonical switching to a Rust rewrite for NTP?
Canonical is moving to ntpd-rs to prioritize memory safety and enhanced security. This shift is part of a broader strategy to oxidize Ubuntu by replacing legacy C-based components with Rust to provide a more stable and secure foundation.
What other tools will be replaced by ntpd-rs?
The transition to the new Rust-based client is designed to be comprehensive, eventually replacing several existing utilities including Chrony linuxptp and gpsd.
Telegram

Fresh news on our Telegram

Get instant alerts for new posts in «Code»

@procodeandevenmore