From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Glen Turner <glen.turner@aarnet.edu.au>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: 8250 serial console fixes -- issue
Date: Fri, 3 Feb 2006 22:13:46 +0000 [thread overview]
Message-ID: <20060203221346.GA10700@flint.arm.linux.org.uk> (raw)
In-Reply-To: <m3lkwse3nz.fsf@defiant.localdomain>
On Fri, Feb 03, 2006 at 06:46:24PM +0100, Krzysztof Halasa wrote:
> Russell King <rmk+lkml@arm.linux.org.uk> writes:
>
> > My point stands - if the user can provide an arbitary string to printk,
> > they can fake any kernel message. That in itself is a security bug.
> > If there is an instance of that, then that's the real bug which would
> > need fixing.
>
> I think the AT problem is valid - the user doesn't have to be able to
> send anything to the console, the system alone can screw it up with
> something as simple as ATZ^M (or with almost any string with embedded
> [aA][tT].*^M).
Stop throwing FUD into this issue. The original claim was that a
non-root user could send arbitary strings via the console system.
This was an independent claim from the other issues.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-02-03 22:13 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 1:21 8250 serial console fixes -- issue Kumar Gala
2006-02-02 1:47 ` Alan Cox
2006-02-02 5:54 ` Kumar Gala
2006-02-02 8:05 ` Kumar Gala
2006-02-02 17:10 ` Kumar Gala
2006-02-03 1:58 ` Glen Turner
2006-02-03 9:40 ` Russell King
2006-02-03 14:27 ` Glen Turner
2006-02-03 16:02 ` Russell King
2006-02-03 17:08 ` Glen Turner
2006-02-03 22:23 ` Russell King
2006-02-04 11:15 ` Russell King
2006-02-04 16:18 ` Krzysztof Halasa
2006-02-04 23:16 ` Russell King
2006-02-04 23:54 ` Krzysztof Halasa
2006-02-05 0:00 ` Russell King
2006-02-05 12:57 ` Krzysztof Halasa
2006-02-03 17:46 ` Krzysztof Halasa
2006-02-03 22:13 ` Russell King [this message]
2006-02-04 16:08 ` Krzysztof Halasa
2006-02-04 23:20 ` Russell King
2006-02-05 3:12 ` Glen Turner
2006-02-05 21:26 ` Krzysztof Halasa
2006-02-06 9:47 ` Russell King
2006-02-07 3:27 ` Glen Turner
2006-02-03 15:05 ` Kumar Gala
2006-02-06 20:26 ` Pavel Machek
2006-02-06 20:55 ` Russell King
2006-02-07 4:00 ` Glen Turner
2006-02-07 9:18 ` Pavel Machek
2006-02-07 17:43 ` Russell King
2006-02-07 22:23 ` Krzysztof Halasa
2006-02-08 0:59 ` Junio C Hamano
2006-02-08 1:19 ` Lee Revell
-- strict thread matches above, loose matches on Subject: below --
2006-02-03 10:00 linux
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=20060203221346.GA10700@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=glen.turner@aarnet.edu.au \
--cc=khc@pm.waw.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.