public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Glen Turner <glen.turner@aarnet.edu.au>,
	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: Mon, 6 Feb 2006 20:26:55 +0000	[thread overview]
Message-ID: <20060206202654.GC2470@ucw.cz> (raw)
In-Reply-To: <20060203094042.GB30738@flint.arm.linux.org.uk>

Hi!

> > 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.

Maybe not *arbitrary* messages, but any user probably can fake enough
to
confuse modem. Name your process \nATD609123456\n and cause it to eat
all memory, or something like that. OOM killer will print name...


						Pavel
-- 
Thanks, Sharp!

  parent reply	other threads:[~2006-02-06 20:27 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
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 [this message]
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=20060206202654.GC2470@ucw.cz \
    --to=pavel@ucw.cz \
    --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