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 [email protected]
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
Am 15. September 2017 10:18:25 GMT-07:00 schrieb Jarkko Sakkinen <[email protected]>:
>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 [email protected]
Of course it's
[email protected]
(Cc'ed)
>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
>
>------------------------------------------------------------------------------
>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
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
--
Sent from my mobile
On Fri, 2017-09-15 at 10:18 -0700, 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 [email protected]
> 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.
And is there to be an update to the MAINTAINERS file entries?
Extended Verification Module (EVM)
L: [email protected]
L: [email protected]
INTEGRITY MEASUREMENT ARCHITECTURE (IMA)
L: [email protected]
L: [email protected]
L: [email protected]
TPM DEVICE DRIVER
L: [email protected] (moderated for non-subscribers)
TPM IBM_VTPM DEVICE DRIVER
L: [email protected] (moderated for non-subscribers)
On Fri, Sep 15, 2017 at 10:21:16AM -0700, Peter Huewe wrote:
>
>
> Am 15. September 2017 10:18:25 GMT-07:00 schrieb Jarkko Sakkinen <[email protected]>:
> >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 [email protected]
>
> Of course it's
> [email protected]
> (Cc'ed)
D'oh, yes :-)
/Jarkko
On Fri, Sep 15, 2017 at 10:25:36AM -0700, Joe Perches wrote:
> On Fri, 2017-09-15 at 10:18 -0700, 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 [email protected]
> > 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.
>
> And is there to be an update to the MAINTAINERS file entries?
>
> Extended Verification Module (EVM)
> L: [email protected]
> L: [email protected]
>
> INTEGRITY MEASUREMENT ARCHITECTURE (IMA)
> L: [email protected]
> L: [email protected]
> L: [email protected]
>
> TPM DEVICE DRIVER
> L: [email protected] (moderated for non-subscribers)
>
> TPM IBM_VTPM DEVICE DRIVER
> L: [email protected] (moderated for non-subscribers)
Yes, I'll get onto it. BTW, do we need two entries for TPM in the
MAINTAINERS file or can I merge those?
/Jarkko
On Fri, 2017-09-15 at 10:36 -0700, Jarkko Sakkinen wrote:
> On Fri, Sep 15, 2017 at 10:25:36AM -0700, Joe Perches wrote:
> > On Fri, 2017-09-15 at 10:18 -0700, Jarkko Sakkinen wrote:
[]
> > > We decided to create a new mailing list [email protected]
> > > to cover both TPM and IMA since they tend to have cross dependencies.
[]
> > And is there to be an update to the MAINTAINERS file entries?
[]
> Yes, I'll get onto it. BTW, do we need two entries for TPM in the
> MAINTAINERS file or can I merge those?
As the individual maintainers are different for the two sections,
I think you need both entries.
Am 15. September 2017 10:40:14 GMT-07:00 schrieb Joe Perches <[email protected]>:
>On Fri, 2017-09-15 at 10:36 -0700, Jarkko Sakkinen wrote:
>> On Fri, Sep 15, 2017 at 10:25:36AM -0700, Joe Perches wrote:
>> > On Fri, 2017-09-15 at 10:18 -0700, Jarkko Sakkinen wrote:
>[]
>> > > We decided to create a new mailing list
>[email protected]
>> > > to cover both TPM and IMA since they tend to have cross
>dependencies.
>[]
>> > And is there to be an update to the MAINTAINERS file entries?
>[]
>> Yes, I'll get onto it. BTW, do we need two entries for TPM in the
>> MAINTAINERS file or can I merge those?
>
>As the individual maintainers are different for the two sections,
>I think you need both entries.
Try to get a hold of ashley and ask whether she is actively maintaining.
While updating Maintainers I vote for removing Marcel Selhorst for tpm.
You can keep me for now :)
Peter
>
>
>------------------------------------------------------------------------------
>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
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
--
Sent from my mobile
On Fri, Sep 15, 2017 at 10:47:06AM -0700, Peter Huewe wrote:
>
>
> Am 15. September 2017 10:40:14 GMT-07:00 schrieb Joe Perches <[email protected]>:
> >On Fri, 2017-09-15 at 10:36 -0700, Jarkko Sakkinen wrote:
> >> On Fri, Sep 15, 2017 at 10:25:36AM -0700, Joe Perches wrote:
> >> > On Fri, 2017-09-15 at 10:18 -0700, Jarkko Sakkinen wrote:
> >[]
> >> > > We decided to create a new mailing list
> >[email protected]
> >> > > to cover both TPM and IMA since they tend to have cross
> >dependencies.
> >[]
> >> > And is there to be an update to the MAINTAINERS file entries?
> >[]
> >> Yes, I'll get onto it. BTW, do we need two entries for TPM in the
> >> MAINTAINERS file or can I merge those?
> >
> >As the individual maintainers are different for the two sections,
> >I think you need both entries.
>
> Try to get a hold of ashley and ask whether she is actively maintaining.
>
> While updating Maintainers I vote for removing Marcel Selhorst for tpm.
>
> You can keep me for now :)
> Peter
During the last bit less than couple of years I've been maintaining
TPM and a bit less than four years I've been contributing I've never
heard anything of Ashley.
What is the expiration time?
/JArkko
On Fri, 2017-09-15 at 10:57 -0700, Jarkko Sakkinen wrote:
> On Fri, Sep 15, 2017 at 10:47:06AM -0700, Peter Huewe wrote:
> > Am 15. September 2017 10:40:14 GMT-07:00 schrieb Joe Perches <[email protected]>:
> > > As the individual maintainers are different for the two sections,
> > > I think you need both entries.
> >
> > Try to get a hold of ashley and ask whether she is actively maintaining.
> >
> > While updating Maintainers I vote for removing Marcel Selhorst for tpm.
> >
> > You can keep me for now :)
> > Peter
>
> During the last bit less than couple of years I've been maintaining
> TPM and a bit less than four years I've been contributing I've never
> heard anything of Ashley.
>
> What is the expiration time?
There is no fixed time at all.
Generally when the email bounces or when the maintainer resigns.
(involuntarily or not...)
It seems a couple years since Ashley signed anything and five years
since Marcel Selhorst signed anything.
It's polite to add a CREDITS entry when removing inactive maintainers.
Newbie question: Do I have to subscribe, or are email addresses being
migrated?
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 [email protected]
> 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.
Am 15. September 2017 13:07:58 GMT-07:00 schrieb Ken Goldman <[email protected]>:
>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 [email protected]
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
>[email protected]
>> 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
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
--
Sent from my mobile
On Fri, Sep 15, 2017 at 11:01:51AM -0700, Joe Perches wrote:
> On Fri, 2017-09-15 at 10:57 -0700, Jarkko Sakkinen wrote:
> > On Fri, Sep 15, 2017 at 10:47:06AM -0700, Peter Huewe wrote:
> > > Am 15. September 2017 10:40:14 GMT-07:00 schrieb Joe Perches <[email protected]>:
> > > > As the individual maintainers are different for the two sections,
> > > > I think you need both entries.
> > >
> > > Try to get a hold of ashley and ask whether she is actively maintaining.
> > >
> > > While updating Maintainers I vote for removing Marcel Selhorst for tpm.
> > >
> > > You can keep me for now :)
> > > Peter
> >
> > During the last bit less than couple of years I've been maintaining
> > TPM and a bit less than four years I've been contributing I've never
> > heard anything of Ashley.
> >
> > What is the expiration time?
>
> There is no fixed time at all.
> Generally when the email bounces or when the maintainer resigns.
> (involuntarily or not...)
>
> It seems a couple years since Ashley signed anything and five years
> since Marcel Selhorst signed anything.
>
> It's polite to add a CREDITS entry when removing inactive maintainers.
The file ends:
"
# Don't add your name here, unless you really _are_ after Marc
# alphabetically. Leonard used to be very proud of being the
# last entry, and he'll get positively pissed if he can't even
# be second-to-last. (and this file really _is_ supposed to be
# in alphabetic order)
"
So where do I should add?-)
/Jarkko
On Fri, 2017-09-15 at 14:47 -0700, Jarkko Sakkinen wrote:
> On Fri, Sep 15, 2017 at 11:01:51AM -0700, Joe Perches wrote:
[]
> > It's polite to add a CREDITS entry when removing inactive maintainers.
>
> The file ends:
>
> "
> # Don't add your name here, unless you really _are_ after Marc
> # alphabetically. Leonard used to be very proud of being the
> # last entry, and he'll get positively pissed if he can't even
> # be second-to-last. (and this file really _is_ supposed to be
> # in alphabetic order)
> "
>
> So where do I should add?-)
http://www.varley.net/Pages/Manhattan.htm