mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Petr Písař" <ppisar@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Clean console safely
Date: Thu, 24 Mar 2011 10:24:31 +0000	[thread overview]
Message-ID: <20110324102431.5e017efe@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1300960611-4820-1-git-send-email-ppisar@redhat.com>

On Thu, 24 Mar 2011 10:56:51 +0100
Petr Písař <ppisar@redhat.com> wrote:

> Traditional \E[2J sequence erases console display but scroll-back
> buffer and underlying device (frame) buffer keep data that can be
> accessed by scrolling console back.
> 
> This patch introduce new \E[J parameter 3 that allows to scramble
> scroll-back buffer explicitly. Session locking programs (screen,
> vlock) can use it to prevent attacker to browse locked console
> history.
> ---
>  drivers/tty/vt/vt.c |    6 ++++++
>  1 files changed, 6 insertions(+), 0 deletions(-)

Looks sensible enough

There are a set of official codes that are probably more relevant, and
also deal with the timing of events

See DECSR/DECSRC on a later VT terminal, also DECSTR which 

DECSR = secure reset, return to power up state, \E[n+p where n is an
optional value from 1-16383 which if provided is replied back from the tty
as a DECSRC response (hence 'secure'). It's defined to clear off
screen memory, and also other weirdness a user may have set up so could
reasonably also be extended a bit if there is other stuff founbd in
future that such a reset really ought to clean up - eg for mingetty.

http://www.vt100.net/docs/vt520-rm/ek-vt520-rm.pdf (page 299)

ED 3J looks fine but is a new "made up" extension.


  reply	other threads:[~2011-03-24 10:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24  9:56 Petr Písař
2011-03-24 10:24 ` Alan Cox [this message]
2011-03-24 14:15   ` Petr Pisar
2011-03-24 14:51     ` Alan Cox
2011-04-13 14:32 Petr Písař
2011-04-13 14:32 ` [PATCH] " Petr Písař
2011-04-13 14:40   ` Artem Bityutskiy
2011-04-13 14:54     ` Petr Písař
2011-04-13 15:01       ` Greg KH
2011-04-13 15:33         ` Petr Pisar
2011-04-13 15:46           ` Greg KH
2011-04-13 15:18       ` Chris Ball
2011-04-13 15:28         ` Petr Pisar
2011-04-13 15:44           ` Chris Ball
2011-04-13 23:55             ` Daniel Taylor
2011-04-15  8:08               ` Petr Písař
2016-07-21 12:53                 ` Jiri Slaby
2011-04-13 15:32         ` Alexander Stein

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=20110324102431.5e017efe@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ppisar@redhat.com \
    /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