Linux Integrity Measurement development
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Mimi Zohar <zohar@linux.ibm.com>,
	Roberto Sassu <roberto.sassu@huawei.com>
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
	Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	linux-integrity@vger.kernel.org, linux-crypto@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] tpm: Check return value of crypto_kpp_set_secret()
Date: Wed, 11 Nov 2026 14:37:41 -0800	[thread overview]
Message-ID: <20261111223741.GC41158@quark> (raw)
In-Reply-To: <at6fpcT5EJIZD8DD@kernel.org>

On Mon, Oct 26, 2026 at 02:32:37AM +0200, Jarkko Sakkinen wrote:
> Adding Mimi and Roberto.
> 
> On Sun, Oct 25, 2026 at 04:40:09PM -0700, Eric Biggers wrote:
> > On Mon, Oct 26, 2026 at 01:28:41AM +0200, Jarkko Sakkinen wrote:
> > > I'm not sure if it already is but if it isn't, probably also at
> > > linux-integrity turning on Sashiko would make sense.
> > 
> > Sashiko currently has monitoring enabled for linux-integrity, but not
> > email replies
> > (https://github.com/sashiko-dev/sashiko/blob/main/projects/linux/mailing_lists.toml#L45).
> > 
> > (Note: this particular patch was Cc'ed to linux-crypto, which does have
> > Sashiko email replies enabled.  So Sashiko would have replied if it had
> > found an issue anyway.)
> > 
> > I definitely would support enabling email replies on linux-integrity
> > (for issues found only), like a lot of other lists already do:
> > 
> >    ["linux-integrity@vger.kernel.org"]
> >    reply_to = ["author", "list", "recipients"]         
> > 
> > If the maintainers of security/integrity/ would ack that, I can open a
> > pull request to the Sashiko GitHub repo that changes it.  Or someone
> > else can go ahead and do it if they want.
> > 

Mimi and Roberto, any thoughts on whether you want Sashiko replies
enabled on linux-integrity?

- Eric

      reply	other threads:[~2026-11-11 22:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-25 21:11 [PATCH] tpm: Check return value of crypto_kpp_set_secret() Eric Biggers
2026-10-25 22:12 ` Jarkko Sakkinen
2026-10-25 22:47   ` Eric Biggers
2026-10-25 23:11     ` Jarkko Sakkinen
2026-10-25 23:28       ` Jarkko Sakkinen
2026-10-25 23:40         ` Eric Biggers
2026-10-26  0:32           ` Jarkko Sakkinen
2026-11-11 22:37             ` Eric Biggers [this message]

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=20261111223741.GC41158@quark \
    --to=ebiggers@kernel.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=roberto.sassu@huawei.com \
    --cc=stable@vger.kernel.org \
    --cc=zohar@linux.ibm.com \
    /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