From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: tpmdd-devel@lists.sourceforge.net,
linux-ima-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: New ML for TPM and IMA
Date: Fri, 15 Sep 2017 10:18:25 -0700 [thread overview]
Message-ID: <20170915171825.5zjit5vsrvxgmvrb@linux.intel.com> (raw)
Hi
Many people were kicked out from the SourceForge mailing list in the
July because SF required a resubscription, including non-human users,
such as patchwork.
We decided to create a new mailing list linux-integrit@vger.kernel.org
to cover both TPM and IMA since they tend to have cross dependencies.
Otherwise, the maintainer hierarchy etc. will stay the same.
It is all documented here:
http://kernsec.org/wiki/index.php/Linux_Kernel_Integrity
>From now on use this list for patches and discussion instead of the
legacy list.
Thank you.
/Jarkko
next reply other threads:[~2017-09-15 17:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 17:18 Jarkko Sakkinen [this message]
2017-09-15 17:21 ` [tpmdd-devel] New ML for TPM and IMA Peter Huewe
2017-09-15 17:34 ` Jarkko Sakkinen
2017-09-15 17:25 ` Joe Perches
2017-09-15 17:36 ` Jarkko Sakkinen
2017-09-15 17:40 ` Joe Perches
2017-09-15 17:47 ` [tpmdd-devel] " Peter Huewe
2017-09-15 17:57 ` Jarkko Sakkinen
2017-09-15 18:01 ` Joe Perches
2017-09-15 21:47 ` Jarkko Sakkinen
2017-09-15 21:55 ` Joe Perches
[not found] ` <1505498511.27581.11.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2017-09-18 9:49 ` Marcel Selhorst
2017-09-15 20:07 ` [tpmdd-devel] " Ken Goldman
2017-09-15 20:32 ` Peter Huewe
[not found] ` <20170915171825.5zjit5vsrvxgmvrb-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-09-15 21:08 ` [Linux-ima-devel] " Ken Goldman
2017-09-15 21:44 ` Jarkko Sakkinen
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=20170915171825.5zjit5vsrvxgmvrb@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=linux-ima-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).