time-epoch never changes in SRUs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-core-initramfs |
Fix Released
|
Undecided
|
Unassigned | ||
systemd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* Systems without hwclock come up with a fixed time epoch which is not updated in SRUs
* Ideally booting with a newer built of systemd should move time epoch to be at least when systemd was last built. For example to the value of SOURCE_DATE_EPOCH.
[Test Case]
* Boot without network NTP or hwclock
* Observe that the epoch is the same as the time when NEWS entry in the systemd source code was last touched.
* Boot newer update of systemd, observe that the time epoch is at least 2020
[Regression Potential]
* Bad epoch, may result in unable to perform TLS connections, validated GPG signatures, and snapd assertions. Changing epoch to be more recent is desired. Some machines may rely on the fact that "bionic" without hwclock always comes up in year 2018. But in practice that is incorrect thing to do.
[Other Info]
* By default
option(
description : 'time epoch for time clients')
in systemd is set to the modification time of the NEW entry
time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout(
If available, it should be set to SOURCE_
tags: | added: rls-ff-incoming |
Changed in ubuntu-core-initramfs: | |
status: | New → In Progress |
tags: |
added: verification-done-focal removed: verification-needed-focal |
https:/ /github. com/systemd/ systemd/ pull/15827