debcrafters-packages team mailing list archive

[Lukas Märdian <2111342@xxxxxxxxxxxxxxxxxx>]

@enr0n, yes there is the specific risk of breaking time synchronization
due to the need for an additional NTS/KE (4460/tcp) port, that might not
be accessible everywhere. We want to play this safe and rather give it a
cycle where chrony/NTS is only enabled on new installations. Especially,
as systemd-timesyncd remains in "main" and is therefore still supported.

We're considering to implement the full, automatic upgrade path to NTS
time synchronization in a following cycle, as tracked in SD-2377.


The risk and (manual) upgrade path is described in the Questing release notes: https://discourse.ubuntu.com/t/questing-quokka-release-notes/59220#p-151948-chrony

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2111342

Title:
  Install time-daemon with NTS support by default

Status in Ubuntu:
  Fix Released
Status in chrony package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Deferred

Bug description:
  Ubuntu shall be secure by default, therefore utilize Network Time
  Security (NTS), as time is the trust anchor for many cryptography
  related processes (e.g. certificates).

  NTS was previously enabled in chrony (LP: #2084585) and comes pre-
  installed in certain Ubuntu cloud images. Still, in Ubuntu
  Desktop/Server and other generic Ubuntu images we rely on systemd-
  timesyncd (without support for NTS [1]). This leads to a situation
  where we have to maintain two time-daemons in "main", while still not
  using NTS on most systems.

  [1] https://github.com/systemd/systemd/issues/9481

  References: spec-FO207, SD-2171, chrony MIR (LP: #1744072)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2111342/+subscriptions