From: Chris Wright <chrisw@sous-sol.org>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Chris Wright <chrisw@sous-sol.org>, Adrian Bunk <bunk@kernel.org>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, James Morris <jmorris@namei.org>
Subject: Re: LSM: MAINTAINERS points to no longer existing URL
Date: Tue, 20 May 2008 08:55:57 -0700 [thread overview]
Message-ID: <20080520155557.GN30402@sequoia.sous-sol.org> (raw)
In-Reply-To: <1211286579.7486.75.camel@moss-spartans.epoch.ncsc.mil>
* Stephen Smalley (sds@tycho.nsa.gov) wrote:
> On Mon, 2008-05-19 at 14:58 -0700, Chris Wright wrote:
> > * Adrian Bunk (bunk@kernel.org) wrote:
> > > MAINTAINERS says:
> > >
> > > LINUX SECURITY MODULE (LSM) FRAMEWORK
> > > P: Chris Wright
> > > M: chrisw@sous-sol.org
> > > L: linux-security-module@vger.kernel.org
> > > W: http://lsm.immunix.org
> > > T: git kernel.org:/pub/scm/linux/kernel/git/chrisw/lsm-2.6.git
> > > S: Supported
> > >
> > > But http://lsm.immunix.org no longer exists.
> >
> > Indeed, queueing this.
>
> What about the git tree listed above? Is it still being maintained?
> James Morris set up a security-testing git tree that was used e.g. for
> the audit conversion from direct selinux calls to using LSM hooks and
> for the security= boot parameter (i.e. for changes that went beyond just
> one LSM).
Yeah, I updated it last night to add this patch, a couple of other
trivial patches (Lindent-type) that were sent to me, and I would put
the proc ptrace one there as well, since it's touching core/smack/etc...
That needs coordination w/ any follow-on.
thanks,
-chris
prev parent reply other threads:[~2008-05-20 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 21:42 Adrian Bunk
2008-05-19 21:58 ` Chris Wright
2008-05-20 12:29 ` Stephen Smalley
2008-05-20 15:55 ` 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=20080520155557.GN30402@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=bunk@kernel.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
/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
all inboxes | Powered by JetHome®