William Roberts
0e15c14f63
Currently, the tpm2 support will use encrypted sessions by creating a primary key that is used to encrypt traffic. This creates a problem as the key created for encrypting the traffic could be faked by an active interposer on the bus. In cases when a pin is used, we can introduce the bind key. The pin is used as the auth value for the seal key, aka the disk encryption key, and that auth value can be used in the session establishment. An attacker would need the pin value to create the secure session and thus an active interposer without the pin could not interpose on TPM traffic. Related-to: #22637 Signed-off-by: William Roberts <william.c.roberts@intel.com>
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.