From: Solar Designer <solar@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] Linux security workgroup usage of kernel-hardening mailing list
Date: Tue, 25 Sep 2012 22:07:15 +0400 [thread overview]
Message-ID: <20120925180715.GA20237@openwall.com> (raw)
In-Reply-To: <5061BE52.50808@linux.vnet.ibm.com>
On Tue, Sep 25, 2012 at 10:23:14AM -0400, Corey Bryant wrote:
> Excellent, thanks! Should we tag our subjects with anything? I was
> thinking "lswg: ".
It's your call, but I doubt that such tagging would be of much/any use.
The topics you have listed are some of what's supposed to be discussed
on this list, and some of the threads may proceed to other related
topics, which are not limited to the focus of lswg (but the tags would
remain). Similarly, postings by non-lswg folks may be relevant to you.
I think it'd be too difficult/unreasonable to keep the separation.
Alexander
next prev parent reply other threads:[~2012-09-25 18:07 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
2012-09-25 18:07 ` Solar Designer [this message]
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=20120925180715.GA20237@openwall.com \
--to=solar@openwall.com \
--cc=kernel-hardening@lists.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.