| Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
fd_* functions in our codebase usually mean fd-specific operations,
while this one actually takes openat()-style params. Rename it
accordingly hence.
|
|
- Drop fstat() fallback path now that we assume fdinfo
is available
- Use at_flags_normalize_nofollow()
- Accept empty path the same way as NULL
- Accept fd being AT_FDCWD and filename being "."
|
|
|
|
|
|
We can now assume name_to_handle_at() syscall is available,
however the underlying fs can still lack support for it.
|
|
|
|
|
|
The documentation and code agree on the same name, since always, but
when I put together the IDL I made a mistake and insert a "Not" that
wasn't supposed to be there.
Let's correct that.
|
|
We got this almost always right. Fix this for a few outliers.
|
|
On CentOS Stream 9/10 booting mkosi qemu with --firmware=linux doesn't
add the virtual TPM to the virtual machine which means TEST-74-AUX-UTILS.run.sh
fails because it requires a TPM.
Let's move the systemd-pcrlock logic that requires a TPM to
TEST-70-TPM.pcrlock to avoid the problem.
|
|
On CentOS Stream, the qemu binary is /usr/libexec/qemu-kvm so use
that if it's available.
|
|
zypper has some new rather questionable userspace level permission
checking that blows ups completely when operating as root on an
cache directory owned by a non-root user, so let's build the tools
tree and set up meson as root to avoid the issue.
(https://github.com/openSUSE/libzypp/issues/603)
Also drop a leftover debug message from coverage.yml while we're at
it.
|
|
|
|
Let's drop these from CentOS Stream tools trees as they are not in
EPEL 10 yet.
|
|
Let's add more coverage for building with tools trees by building
each image with a tools tree of the same distribution and release.
Because not every tools tree distribution has a newer meson yet, we
only use --max-lines= when meson actually knows the option.
|
|
|
|
|
|
|
|
|
|
|
|
This in particular makes sure that we normalize the user name and update
it in the PAM session, once we acquire it. This means that if you have a
user with name "a" and alias "b", and the user logs in as "b" they end
up properly with "a" as user name set, as intended by the PAM gods.
Moreover, if you have a user "c" in a ralm "d", they may log in by
specifying "c" or "c@d", with equivalent results.
|
|
|
|
|
|
This ensures that user names can be specified either in the regular
short syntax or with a realm appended, and both are accepted. (The
latter of course only if the record actually defines a realm)
|
|
|
|
|
|
|
|
Uses the newly added policy-digest verb of systemd-measure, for the same
purpose: build a UKI and get digests for the .pcrsig section out, so
that they can be offline signed and reattached
|
|
When doing offline signing we need to know the exact payload
to sign, and the 'calculate' verb doesn't really show that, it
shows the PCR values. But what we sign is the hash of the policy.
So add a new verb that outputs the json payload that goes in the
.pcrsig section, without the .sig object, so that we can take them
and give the .pol object to an offline and asynchronous signing
service, such as SUSE's Open Build Service, and then add the .sig
object to the json and attach it to a UKI.
|
|
|
|
|
|
|
|
This doesn't make the RNG cryptographic strength, but if we have it
easily accessible, why not include the pidfd id. It is after all not
vulnerable to reuse.
|
|
Note that this drops a lot of "const" qualifiers on PidRef arguments.
That's because pidref_is_self() suddenly might end changing the PidRef
because it acquires the pidfd ID.
We had this previously already with pidfd_equal(), but this amplifies
the problem.
I guess we C's "const" doesn't really work for stuff that contains
caches, that is just conceptually constant, but not actually.
|
|
let's start caching our own pidfd id, since it's somewhat involved to
get but a much better identifier for things than the classic PID is.
|
|
|
|
let's be strict here, our codebase allows it.
|
|
This is shown every time nspawn is started, which is annoying
and there's nothing a user can do about it, since it depends on
an extremely new kernel. Downgrade to debug.
Follow-up for 611ae598889471830b2f1d7251c271b79884b1c4
|
|
Should be useful for debugging udev rules.
|
|
This introduces io.systemd.Udev.SetTrace varlink method. With the
method, trace logging by udev worker can be dynamically controlled.
|
|
This adds udev.trace[=BOOL] kernel command line option to control trace
logging.
|
|
No functional change, just refactoring.
|
|
According to RFC 9460 "An empty list of addresses is invalid."
https://www.rfc-editor.org/rfc/rfc9460.html#section-7.3
|
|
|
|
|
|
|
|
|
|
|
|
mkosi does this itself so no need to do it in systemd.
|
