From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Glen Turner <glen.turner@aarnet.edu.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Kumar Gala <galak@kernel.crashing.org>,
linux-kernel@vger.kernel.org
Subject: Re: 8250 serial console fixes -- issue
Date: Fri, 3 Feb 2006 09:40:42 +0000 [thread overview]
Message-ID: <20060203094042.GB30738@flint.arm.linux.org.uk> (raw)
In-Reply-To: <43E2B8D6.1070707@aarnet.edu.au>
On Fri, Feb 03, 2006 at 12:28:46PM +1030, Glen Turner wrote:
> Hi Alan,
>
> The serial console driver has a host of issues
>
> [...]
>
> - [SECURITY] 'r' should require DCD to be asserted
> before outputing characters. Otherwise we talk to
> Hayes modem command mode. This allows a non-root
> user to re-program the modem and is a major security
> issue is people configure calling line identification
> or encryption to restrict use of the serial console.
How is this possible? A normal user can't produce arbitarily formatted
kernel messages, and if they have access to /dev/ttyS they can do what
ever they like with the port anyway.
(If a user can produce arbitarily formatted kernel messages, that in
itself is a security bug - how do you know if that OOPS was produced
by a malicious user, or a real oops?)
> - 'r' option has insanely slow CTS timeout. So if a
> terminal server is inactive the kernel can take
> 30 minutes to boot as each character write to the
> serial console requires a CTS timeout.
You'd rather we threw away these messages?
> I occassionally clean up and repost a patch I wrote years
> ago which never gets integrated (although it ships in the
> patchset of a number of kernels from supercomputer vendors).
> I'm happy to clean it up again if there's a hope of
> integration.
It'd help if you talked to the right person - I've been looking after
the serial layer since 2.5.something.
--
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 9:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 1:21 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 [this message]
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
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
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=20060203094042.GB30738@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=galak@kernel.crashing.org \
--cc=glen.turner@aarnet.edu.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome