From: James Morris <jmorris@namei.org>
To: Jeremy Cline <jcline@redhat.com>
Cc: "Serge E . Hallyn" <serge@hallyn.com>,
Matthew Garrett <matthewgarrett@google.com>,
David Howells <dhowells@redhat.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Frank Ch . Eigler" <fche@redhat.com>
Subject: Re: [PATCH] lockdown: Allow unprivileged users to see lockdown status
Date: Thu, 14 May 2020 12:43:45 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.2005141242200.30052@namei.org> (raw)
In-Reply-To: <20200511134230.GA2311339@dev.jcline.org>
On Mon, 11 May 2020, Jeremy Cline wrote:
> On Sat, Feb 22, 2020 at 03:51:24AM +1100, James Morris wrote:
> > On Thu, 20 Feb 2020, Jeremy Cline wrote:
> >
> > > A number of userspace tools, such as systemtap, need a way to see the
> > > current lockdown state so they can gracefully deal with the kernel being
> > > locked down. The state is already exposed in
> > > /sys/kernel/security/lockdown, but is only readable by root. Adjust the
> > > permissions so unprivileged users can read the state.
> > >
> > > Fixes: 000d388ed3bb ("security: Add a static lockdown policy LSM")
> > > Cc: Frank Ch. Eigler <fche@redhat.com>
> > > Signed-off-by: Jeremy Cline <jcline@redhat.com>
> >
> > Looks fine to me, any objection from Matthew or others?
> >
>
> Can we take resounding silence as no objections?
Please resend and I'll apply it to my tree.
>
> - Jeremy
>
> > > ---
> > > security/lockdown/lockdown.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/security/lockdown/lockdown.c b/security/lockdown/lockdown.c
> > > index 5a952617a0eb..87cbdc64d272 100644
> > > --- a/security/lockdown/lockdown.c
> > > +++ b/security/lockdown/lockdown.c
> > > @@ -150,7 +150,7 @@ static int __init lockdown_secfs_init(void)
> > > {
> > > struct dentry *dentry;
> > >
> > > - dentry = securityfs_create_file("lockdown", 0600, NULL, NULL,
> > > + dentry = securityfs_create_file("lockdown", 0644, NULL, NULL,
> > > &lockdown_ops);
> > > return PTR_ERR_OR_ZERO(dentry);
> > > }
> > >
> >
> > --
> > James Morris
> > <jmorris@namei.org>
> >
>
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2020-05-14 2:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 15:17 Jeremy Cline
2020-02-21 16:51 ` James Morris
2020-05-11 13:42 ` Jeremy Cline
2020-05-14 2:43 ` James Morris [this message]
2020-05-14 14:05 ` [PATCH RESEND] " Jeremy Cline
2020-05-14 17:28 ` James Morris
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=alpine.LRH.2.21.2005141242200.30052@namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--cc=fche@redhat.com \
--cc=jcline@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=matthewgarrett@google.com \
--cc=serge@hallyn.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
all inboxes | Powered by JetHome®