d2bf22fb8d
cryptenroll allows to specify a custom TPM driver separated from parameters with colon e.g. `systemd-cryptenroll --tpm2-device=swtpm:` tells to load swtpm tss driver and use it as a device. Unfortunately it does not work, swtpm driver init() fails with ``` debug:tcti:src/tss2-tcti/tcti-swtpm.c:570:Tss2_Tcti_Swtpm_Init() Dup'd conf string to: 0x562f91cbc000 debug:tcti:src/util/key-value-parse.c:85:parse_key_value_string() parsing key/value: swtpm: WARNING:tcti:src/util/key-value-parse.c:50:parse_key_value() key / value string is invalid Failed to initialize TCTI context: tcti:A parameter has a bad value ``` It turns out that cryptenroll suppose to use the driver name internally and strip it before passing the rest of parameters to init() function. Without doing it swtpm receives incorrect key-value property and gets confused. Fix it by passing the correct parameter (without driver name) to the init() function. Fixes #20708 |
||
---|---|---|
.github | ||
.lgtm/cpp-queries | ||
.semaphore | ||
catalog | ||
coccinelle | ||
docs | ||
factory/etc | ||
hwdb.d | ||
man | ||
mkosi.default.d | ||
modprobe.d | ||
network | ||
po | ||
presets | ||
rules.d | ||
shell-completion | ||
src | ||
sysctl.d | ||
sysusers.d | ||
test | ||
tmpfiles.d | ||
tools | ||
units | ||
xorg | ||
.clang-format | ||
.ctags | ||
.dir-locals.el | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.lgtm.yml | ||
.mailmap | ||
.packit.yml | ||
.vimrc | ||
.ycm_extra_conf.py | ||
configure | ||
LICENSE.GPL2 | ||
LICENSE.LGPL2.1 | ||
Makefile | ||
meson_options.txt | ||
meson.build | ||
mkosi.build | ||
NEWS | ||
README | ||
README.md | ||
TODO |
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.