| 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
| ||
|
Message-ID: <20101117100321.GB1574@ucw.cz> Date: Wed, 17 Nov 2010 11:03:21 +0100 From: Pavel Machek <pavel@....cz> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: Dan Rosenberg <drosenberg@...curity.com>, linux-kernel@...r.kernel.org, security@...nel.org, stable@...nel.org Subject: Re: [PATCH] Restrict unprivileged access to kernel syslog On Tue 2010-11-09 12:06:49, Alan Cox wrote: > On Mon, 08 Nov 2010 22:28:58 -0500 > Dan Rosenberg <drosenberg@...curity.com> wrote: > > > The kernel syslog contains debugging information that is often useful > > during exploitation of other vulnerabilities, such as kernel heap > > addresses. Rather than futilely attempt to sanitize hundreds (or > > thousands) of printk statements and simultaneously cripple useful > > debugging functionality, it is far simpler to create an option that > > prevents unprivileged users from reading the syslog. > > Except for anything that appears on the screen - which is remotely > readable via the screen access APIs. Looks sane to me (pointless but > sane) and the checks match the ones needed to redirect the console so you > need CAP_SYS_ADMIN either way. /dev/vcsa is only protected by filesystem permissions IIRC. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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