linux-kernel - Re: i386-show-unhandled-signals-v3

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]

Message-ID: <20070726111652.56467031@the-village.bc.nu>
Date:	Thu, 26 Jul 2007 11:16:52 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Andi Kleen <ak@...e.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	"Masoud Sharbiani" <masouds@...gle.com>,
	"Kirill Korotaev" <dev@...nvz.org>, linux-kernel@...r.kernel.org
Subject: Re: i386-show-unhandled-signals-v3

On Thu, 26 Jul 2007 11:46:23 +0200
Andi Kleen <ak@...e.de> wrote:

> 
> > Look: if there's a way in which an unprivileged user can trigger a printk
> > we fix it, end of story. 
> 
> I'm firmly against disabling it on x86-64 by default. The printks are extremly
> useful and have found many bugs in the past.

Then add the rate limiting by default.

Lots of things are convenient. Being able to read arbitary kernel memory
from user space is frequently convenient for debugging but that doesn't
mean its a good idea or should be allowed
-
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/