linux-kernel - Re: [PATCH] sysctl: fix restrict write access to dmesg

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 30 Mar 2012 17:55:25 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Richard Weinberger <richard@....at>
Cc:	Phillip Lougher <plougher@...hat.com>,
	linux-kernel@...r.kernel.org,
	Dan Rosenberg <drosenberg@...curity.com>,
	"Serge E. Hallyn" <serge@...lyn.com>, Eugene Teo <eteo@...hat.com>,
	Eric Paris <eparis@...hat.com>,
	James Morris <jmorris@...ei.org>,
	Kees Cook <keescook@...omium.org>
Subject: Re: [PATCH] sysctl: fix restrict write access to dmesg_restrict

On Sat, 31 Mar 2012 01:50:52 +0200 Richard Weinberger <richard@....at> wrote:

> Am 31.03.2012 01:43, schrieb Phillip Lougher:
> > Commit bfdc0b4 adds code to restrict access to dmesg_restrict,
> > however, it incorrectly alters kptr_restrict rather than
> > dmesg_restrict.
> > 
> > The original patch from Richard Weinberger
> > (https://lkml.org/lkml/2011/3/14/362) alters dmesg_restrict as
> > expected, and so the patch seems to have been misapplied.
> > 
> 
> Hmm, indeed.
> Any idea how this could happen, Andrew?

Presumably someone else fiddled with the file, patch(1) misapplied the
hunk and I didn't notice.

Send a fix?
--
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/