[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110622191022.66135615@lxorguk.ukuu.org.uk>
Date: Wed, 22 Jun 2011 19:10:22 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Joe Perches <joe@...ches.com>
Cc: Vasiliy Kulikov <segoon@...nwall.com>,
Andrew Morton
<akpm@...ux-foundation.org>,
James Morris <jmorris@...ei.org>, Ingo Molnar
<mingo@...e.hu>,
Namhyung Kim <namhyung@...il.com>,
Greg Kroah-Hartman
<gregkh@...e.de>,
kernel-hardening@...ts.openwall.com, linux-kernel@...r.kernel.org,
security@...nel.org
Subject: Re: [PATCH] kernel: escape non-ASCII and control characters in
printk()
On Wed, 22 Jun 2011 09:38:03 -0700
Joe Perches <joe@...ches.com> wrote:
> On Wed, 2011-06-22 at 13:53 +0400, Vasiliy Kulikov wrote:
> > This patch escapes all characters outside of allowed '\n' plus 0x20-0x7E
> > charset passed to printk().
I think this is fundamentally wrong.
It makes sense for some interfaces but not others and arbitarily doing it
makes a nasty mess of anything like file name printing in non English
languages.
The right way to do this IMHO is for the console device itself to have a
filter function, the default would be the 0x20-0x7E but for example with
any console which has an accompanying tty device the right behaviour
depends upon the port UTF8 flag (IUTF8).
If that is set you shouldn't be filtering out unicode, just control codes.
Minor other nit is that you might want to allow BEL through and you
certainly want to allow tab through.
The core code should not be hardcoding policy assumptions about symbol
sets and ASCII, for an awful lot of consoles today that assumption is
just plain wrong, for others it makes sense
So with tty maintainer hat on - NAK to the current approach but a good
idea to do it properly.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
