From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Jarkko Sakkinen" <jarkko@kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Peter Huewe" <peterhuewe@gmx.de>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"David Howells" <dhowells@redhat.com>, <keyrings@vger.kernel.org>,
<linux-integrity@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] TPM DEVICE DRIVER: tpmdd-next-6.10-rc1
Date: Fri, 10 May 2024 11:12:40 +0300 [thread overview]
Message-ID: <D15TAQ4AQ2KO.28SP4AL9V89BL@kernel.org> (raw)
In-Reply-To: <D15DSV117DQZ.3GJOTXCTGZHE9@kernel.org>
On Thu May 9, 2024 at 11:04 PM EEST, Jarkko Sakkinen wrote:
> Hi,
>
> These are the changes for the TPM driver with a single major new
> feature: TPM bus encryption and integrity protection. The key pair
> on TPM side is generated from so called null random seed per power
> on of the machine [1]. This supports the TPM encryption of the hard
> drive by adding layer of protection against bus interposer attacks.
>
> Other than the pull request a few minor fixes and documentation for
> tpm_tis to clarify basics of TPM localities for future patch review
> discussions (will be extended and refined over times, just a seed).
>
> [1] https://lore.kernel.org/linux-integrity/20240429202811.13643-1-James.Bottomley@HansenPartnership.com/
Two former PR's (keys, trusted keys) look a bit different as I realized
that my current script does not scale too well. So I do in future use
a method where the subsystem name is picked from MAINTAINERS and I have
crafted aerc templates [1] for each subsystem (also CC lists need
tuning).
This will get better and more polished as I get my scripting more
polished. If anything went wrong, it is mostly because process changes
have their glitches :-)
https://man.archlinux.org/man/aerc-templates.7.en
BR, Jarkko
next prev parent reply other threads:[~2024-05-10 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 20:04 [GIT PULL] TPM DEVICE DRIVER: tpmdd-next-6.10-rc1 Jarkko Sakkinen
2024-05-10 8:12 ` Jarkko Sakkinen [this message]
2024-05-13 17:50 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D15TAQ4AQ2KO.28SP4AL9V89BL@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=jgg@ziepe.ca \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox