[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1K38aL-0003KY-Qq@pomaz-ex.szeredi.hu>
Date: Mon, 02 Jun 2008 13:52:21 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: matthew@....cx
CC: hch@...radead.org, linux-security-module@...r.kernel.org,
linux-fsdevel@...r.kernel.org, jmorris@...ei.org,
sds@...ho.nsa.gov, eparis@...hat.com, casey@...aufler-ca.com,
agruen@...e.de, jjohansen@...e.de,
penguin-kernel@...ove.SAKURA.ne.jp, viro@...IV.linux.org.uk,
linux-kernel@...r.kernel.org
Subject: Re: [patch 01/15] security: pass path to inode_create
> > > I maintain, that moving lsm hooks into callers is insane. And that's
> > > *the* sanest alternative that anybody has been able to come up with to
> > > passing down vfsmounts into the vfs.
> >
> > Not so. I showed how pathname-based security could be done *without*
> > passing vfsmounts down at all. Unfortunately, you weren't interested.
>
> Umm, not sure what you are referring to. Could you please give a
> pointer? I'm sure the apparmor developers would be more than
> interested in such a scheme, if it does indeed work.
Found it:
http://lkml.org/lkml/2008/4/9/98
I did not take part in that discussion and could not have been able to
contribute anyway. From a cursory read of the thread, the idea was
good, but not entirely applicable to apparmor. Or did I miss
something?
Thanks,
Miklos
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists