From: WANG Cong <xiyou.wangcong@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Restrict write access to dmesg_restrict
Date: Tue, 15 Mar 2011 13:46:28 +0000 (UTC) [thread overview]
Message-ID: <ilnqjj$rjj$2@dough.gmane.org> (raw)
In-Reply-To: 1300131356-24389-1-git-send-email-richard@nod.at
On Mon, 14 Mar 2011 20:35:56 +0100, Richard Weinberger wrote:
> When dmesg_restrict is set to 1 CAP_SYS_ADMIN is needed to read the
> kernel ring buffer.
> But a root user without CAP_SYS_ADMIN is able to reset dmesg_restrict to
> 0.
>
> This is an issue when e.g. LXC (Linux Containers) are used and complete
> user space is running without CAP_SYS_ADMIN. A unprivileged and jailed
> root user can bypass the dmesg_restrict protection.
>
> With this patch writing to dmesg_restrict is only allowed when root has
> CAP_SYS_ADMIN.
>
> Signed-off-by: Richard Weinberger <richard@nod.at>
Makes sense.
Reviewed-by: WANG Cong <xiyou.wangcong@gmail.com>
Thanks.
prev parent reply other threads:[~2011-03-15 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 19:35 [PATCH] Restrict write access to dmesg_restrict Richard Weinberger
2011-03-14 19:49 ` Dan Rosenberg
2011-03-14 20:02 ` Richard Weinberger
2011-03-15 13:46 ` WANG Cong [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='ilnqjj$rjj$2@dough.gmane.org' \
--to=xiyou.wangcong@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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