tpmdd-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Peter Huewe <peterhuewe@gmx.de>
To: tpmdd-devel@lists.sourceforge.net,
	Ken Goldman <kgold@linux.vnet.ibm.com>,
	linux-ima-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: Re: [tpmdd-devel] New ML for TPM and IMA
Date: Fri, 15 Sep 2017 13:32:55 -0700	[thread overview]
Message-ID: <24D42E05-CF0B-4507-9B2F-D703DB4D1B36@gmx.de> (raw)
In-Reply-To: <05fa761b-707c-4a24-a1a0-a9ce6c0e7eef@linux.vnet.ibm.com>



Am 15. September 2017 13:07:58 GMT-07:00 schrieb Ken Goldman <kgold@linux.vnet.ibm.com>:
>Newbie question:  Do I have to subscribe, or are email addresses being 
>migrated

You have to subscribe yourself.
Due to the new privacy regulations I do not have access to any member information anymore on the old list.


Just send a plaintext  email with the body/text
subscribe linux-integrity
to majordomo@vger.kernel.org

Peter
>
>On 9/15/2017 1:18 PM, Jarkko Sakkinen wrote:
>> 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.
>
>
>------------------------------------------------------------------------------
>Check out the vibrant tech community on one of the world's most
>engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>_______________________________________________
>tpmdd-devel mailing list
>tpmdd-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/tpmdd-devel

-- 
Sent from my mobile

  reply	other threads:[~2017-09-15 20:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-15 17:18 New ML for TPM and IMA Jarkko Sakkinen
2017-09-15 17:21 ` [tpmdd-devel] " 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 [this message]
     [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=24D42E05-CF0B-4507-9B2F-D703DB4D1B36@gmx.de \
    --to=peterhuewe@gmx.de \
    --cc=kgold@linux.vnet.ibm.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 NNTP newsgroup(s).