From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: Solar Designer <solar@openwall.com>
Cc: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] Linux security workgroup usage of kernel-hardening mailing list
Date: Tue, 25 Sep 2012 10:23:14 -0400 [thread overview]
Message-ID: <5061BE52.50808@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120925040202.GA17983@openwall.com>
On 09/25/2012 12:02 AM, Solar Designer wrote:
> On Mon, Sep 24, 2012 at 02:49:35PM -0400, Corey Bryant wrote:
>> The charter of the workgroup is to provide on-going security
>> verification of Linux kernel subsystems in order to assist in securing
>> the Linux Kernel and maintain trust and confidence in the security of
>> the Linux ecosystem.
>>
>> This may include, but is not limited to, topics such as tooling to
>> assist in securing the Linux Kernel, verification and testing of
>> critical subsystems for vulnerabilities, security improvements for build
>> tools, and providing guidance for maintaining subsystem security.
>>
>> Would it be okay if we used the kernel-hardening mailing list for
>> communication?
>
> Of course! Please do.
>
Excellent, thanks! Should we tag our subjects with anything? I was
thinking "lswg: ".
>> If our traffic ever gets to be too much
>
> This would be a good problem to have (well, assuming that list traffic
> correlates with actual progress).
:)
>
> Alexander
>
>
>
--
Regards,
Corey Bryant
next prev parent reply other threads:[~2012-09-25 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 18:49 [kernel-hardening] Linux security workgroup usage of kernel-hardening mailing list Corey Bryant
2012-09-25 4:02 ` Solar Designer
2012-09-25 14:23 ` Corey Bryant [this message]
2012-09-25 18:07 ` Solar Designer
2012-09-25 21:08 ` Corey Bryant
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=5061BE52.50808@linux.vnet.ibm.com \
--to=coreyb@linux.vnet.ibm.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=solar@openwall.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.