From: Chris Wright <chris@wirex.com>
To: torvalds@transmeta.com, akpm@digeo.com
Cc: linux-kernel@vger.kernel.org, linux-security-module@wirex.com,
greg@kroah.com, sds@epoch.ncsc.mil
Subject: Re: [PATCH][LSM] Early init for security modules 1/4
Date: Fri, 13 Jun 2003 00:30:41 -0700 [thread overview]
Message-ID: <20030613003041.A31635@figure1.int.wirex.com> (raw)
In-Reply-To: <20030613001021.D31636@figure1.int.wirex.com>; from chris@wirex.com on Fri, Jun 13, 2003 at 12:10:21AM -0700
argh, sorry about the blank subject on that first patch. typing too
quickly.
> [LSM] early init for security modules. As discussed before, this allows
<snip>
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
prev parent reply other threads:[~2003-06-13 7:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 7:10 Chris Wright
2003-06-13 7:15 ` [PATCH][LSM] Remove task_kmod_set_label hook 2/4 Chris Wright
2003-06-13 7:19 ` [PATCH][LSM] Remove inode_permission_lite hook 3/4 Chris Wright
2003-06-13 7:22 ` [PATCH][LSM] setfsuid/setgsuid bug fix 4/4 Chris Wright
2003-06-13 7:30 ` Chris Wright [this message]
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=20030613003041.A31635@figure1.int.wirex.com \
--to=chris@wirex.com \
--cc=akpm@digeo.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=sds@epoch.ncsc.mil \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox