| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|\
| |
| |
| |
| | |
gportay/veritysetup-add-support-for-dm-verity-flags
veritysetup: add support for veritytab
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds the support for veritytab.
The veritytab file contains at most five fields, the first four are
mandatory, the last one is optional:
- The first field contains the name of the resulting verity volume; its
block device is set up /dev/mapper/</filename>.
- The second field contains a path to the underlying block data device,
or a specification of a block device via UUID= followed by the UUID.
- The third field contains a path to the underlying block hash device,
or a specification of a block device via UUID= followed by the UUID.
- The fourth field is the roothash in hexadecimal.
- The fifth field, if present, is a comma-delimited list of options.
The following options are recognized only: ignore-corruption,
restart-on-corruption, panic-on-corruption, ignore-zero-blocks,
check-at-most-once and root-hash-signature. The others options will
be implemented later.
Also, this adds support for the new kernel verity command line boolean
option "veritytab" which enables the read for veritytab, and the new
environment variable SYSTEMD_VERITYTAB which sets the path to the file
veritytab to read.
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sometimes, non-ramfs initrd root are useful. Eg, for kdump, because
initramfs is memory consuming, so mount a compressed image in earlier
initrd, chroot into it then let systemd do the rest of job is a good
solution.
But systemd doesn't recognize the initrd environment if rootfs is not a
temporary fs. This is a reasonable check, because switch-root in initrd
will wipe the whole rootfs, will be a disaster if there are any
misdetect.
So extend SYSTEMD_IN_INITRD environment variable, now it accepts boolean
value and two extra keyword, "auto" and "lenient". "auto" is same as
before, and it's the default value. "lenient" will let systemd bypass
the rootfs check.
|
| |
|
|
|
|
|
|
|
|
| |
The boot loader specification link points to the boot loader interface
documentation.
This fixes the link to point to BOOT_LOADER_SPECIFICATION instead of
BOOTLOADER_INTERFACE which is itself.
|
|
|
|
|
|
|
| |
This only changes documentation. In various places we call "ninja"
directly. I figured it would be safer to leave those in place for now,
given the meson replacement commands lines appears to be supported in
newer meson versions only.
|
| |
|
|
|
|
|
|
|
|
| |
Fixes: #17588 #17512
Prompted-by: #17529
(Also relevant: #6076)
|
| |
|
|\
| |
| | |
tree-wide: fix "the the" and "that that"
|
| | |
|
|/
|
|
| |
No significant changes
|
|\
| |
| | |
timer: add new feature FixedRandomDelay=
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
FixedRandomDelay=yes will use
`siphash24(sd_id128_get_machine() || MANAGER_IS_SYSTEM(m) || getuid() || u->id)`,
where || is concatenation, instead of a random number to choose a value between
0 and RandomizedDelaySec= as the timer delay.
This essentially sets up a fixed, but seemingly random, offset for each timer
iteration rather than having a random offset recalculated each time it fires.
Closes #10355
Co-author: Anita Zhang <the.anitazha@gmail.com>
|
| | |
|
|/
|
|
|
|
|
|
|
| |
Fixes: #17504
(While we are it, also move $SYSTEMD_SECCOMP_LOG= env var description
into the right document section)
Also suggested in: https://github.com/systemd/systemd/issues/17245#issuecomment-704773603
|
|\
| |
| | |
Additional fix ups from #17417
|
| |
| |
| |
| |
| | |
Seems that people think it's useful for brevity so make it explicit in
the CODING_STYLE.
|
|/ |
|
|\
| |
| | |
Fix sd_notify() usage in various daemons and update some documentation links
|
| |
| |
| |
| |
| | |
https://www.freedesktop.org/wiki/Software/systemd/multiseat/ says that it
is obsoleted by sd-login(3), so it doesn't make much sense to link to the former.
|
|\ \
| | |
| | | |
bootspec entry character set clarifications
|
| |/
| |
| |
| | |
Prompted-by: https://github.com/systemd/systemd/issues/12572#issuecomment-711074702
|
|/
|
|
|
|
|
|
|
|
| |
Primarily:
1. Mention that we prefer if return parameters carry "ret_" as prefix in
their name
2. Clarify that debug-level logging is always OK, and irrelevant to when
deciding whether a function is logging or non-logging.
|
|\
| |
| | |
systemd-oomd
|
| |
| |
| |
| |
| | |
This adds the hook ups so it can be read with the usual systemd
utilities. Used in later commits by sytemd-oomd.
|
|/
|
|
|
| |
Also, while we are at it, explain that udev won't reprobe if users just
release the lock, they have to close the block device too.
|
|
|
|
|
|
|
| |
We have three somewhat separate ideas: what the directory is for, what $TMPDIR is for, and security considerations.
Let's use paragraphs.
Also, conjunctions in titles aren't capitalized usually.
|
|\
| |
| | |
Read /etc/login.defs
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It makes little sense to make the boundary between systemd and user guids
configurable. Nevertheless, a completely fixed compile-time define is not
enough in two scenarios:
- the systemd_uid_max boundary has moved over time. The default used to be
500 for a long time. Systems which are upgraded over time might have users
in the wrong range, but changing existing systems is complicated and
expensive (offline disks, backups, remote systems, read-only media, etc.)
- systems are used in a heterogenous enviornment, where some vendors pick
one value and others another.
So let's make this boundary overridable using /etc/login.defs.
Fixes #3855, #10184.
|
|/ |
|
|
|
|
|
|
|
| |
SYSTEMD_RDRAND=0 will prevent using RDRAND even on systems whose CPUID claims
to support it. All other values have no effect.
Fixes: #17112
|
|\
| |
| | |
Update dbus docs, make developer mode default
|
| |
| |
| |
| |
| |
| |
| | |
This means that the dbus doc consistency checks will be enabled by default,
including in the CI. I think that will work better than current state where
people do not enable them and them follow-up patches for the docs like the
parent commit must be had.
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
| |
With new directive SystemCallLog= it's possible to list system calls to be
logged. This can be used for auditing or temporarily when constructing system
call filters.
---
v5: drop intermediary, update HASHMAP_FOREACH_KEY() use
v4: skip useless debug messages, actually parse directive
v3: don't declare unused variables with old libseccomp
v2: fix build without seccomp or old libseccomp
|
|
|
|
|
|
|
| |
listening state
Disabled by default. When Enabled, before listening on the socket, flush the content.
Applies when Accept=no only.
|
|
|
|
| |
Fixes: #16550
|
| |
|
|\
| |
| | |
credentials logic to pass privileged data to services
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
| |
procfs mount options
Kernel 5.8 gained a hidepid= implementation that is truly per procfs,
which allows us to mount a distinct once into every unit, with
individual hidepid= settings. Let's expose this via two new settings:
ProtectProc= (wrapping hidpid=) and ProcSubset= (wrapping subset=).
Replaces: #11670
|
|\
| |
| | |
Update bus api docs
|
| | |
|
|/ |
|
| |
|
|\
| |
| | |
nspawn: /run/host/ tweaks
|