systemd

systemd:main

  1. Git
  2. lp:systemd
  3. main
Last commit made on 2023-08-31
Get this branch:
git clone -b main https://git.launchpad.net/systemd

Branch merges

Branch information

Name:
main
Repository:
lp:systemd

Recent commits

c27465d... by Lennart Poettering <email address hidden>

glyph-util: bring glyphs into same order everywhere

The enum definition, the two string tables and the test all were using
different orders (and in case of the test even missed entries).

Let's unify this, and make sure we always use the same order. This
settles the confusion, and makes the order used for the unicode string
table the canonical one, adjusting the other lists to match it. And adds
the missing entries to the tets.

359b5e7... by Lennart Poettering <email address hidden>

Merge pull request #29004 from poettering/measure-log

tpm2: whenever we measure, also write a tpm log record

c23b07d... by "Milton D. Miller II" <email address hidden>

NEWS: Typo

Let's not encourage the lawyers.

a699b1e... by Luca Boccassi

busctl: do not print start/stop monitoring messages with --quiet/--json

b0881b6... by Luca Boccassi

mkosi: pin CentOS9 kernel to working version

Newer kernels are affected by a regression that causes a kernel panic
on shutdown, so pin them for now. Can be reverted once that problem is
fixed.

https://bugzilla.redhat.com/show_bug.cgi?id=2234390

a4e941e... by Lennart Poettering <email address hidden>

test: add test for new measurement log

cb19bda... by Lennart Poettering <email address hidden>

tpm2: whenever we measure, also write a tpm log record

Previously we only logged our measurements to the journal. This is not a
great solution though, since regular logs are subject to rotation, which
is something we really cannot have for measurements (as it means we can
never reproduce the PCR values from the data). Hence, let's maintain an
explicit log.

Ideally, we'd just use the TCG Canonical Event Log format 1:1
(https://trustedcomputinggroup.org/resource/canonical-event-log-format/).
However it's not a perfect fit fo us, for various reasons. But let's
follow it (in its JSON incantation) as closely at it makes sense, so
that it can easily be converted to the full format by programs consuming
it.

Code comments explain where we deviate from the TCG CEL-JSON, and what
to do about it when reading the data.

73ac952... by Luca Boccassi

Merge pull request #29013 from yuwata/sd-dhcp-client-ensure-iaid-and-duid

sd-dhcp-client: set IAID and DUID earlier

3b981f7... by Yu Watanabe <email address hidden>

Revert "test-dhcp-client: add temporary workaround for assertion failure"

This reverts commit 1686c884bfa846f8da87621e87870eb18dd8107c.

The issue should be fixed by the previous commit. Let's drop the
workaround.

5e2a89d... by Yu Watanabe <email address hidden>

sd-dhcp-client: ensure IAID and DUID being set on start

After b2851e8d6287ab9bb3cd6e42395271c45ce0e377, if IAID and DUID are not
set on start, calling sd_dhcp_client_set_iaid_duid_en() in
client_message_init() triggers assertion, as the client is already
running at the stage. Let's set IAID and DUID earlier.

Fixes #28990.