linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Petr Písař" <ppisar@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Clean console safely
Date: Wed, 13 Apr 2011 17:40:51 +0300	[thread overview]
Message-ID: <1302705651.2768.21.camel@localhost> (raw)
In-Reply-To: <1302705170-15712-2-git-send-email-ppisar@redhat.com>

On Wed, 2011-04-13 at 16:32 +0200, Petr Písař 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(-)

You forgot to "Signed-off-by:" it.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)


  reply	other threads:[~2011-04-13 14:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 14:32 Clean console safely Petr Písař
2011-04-13 14:32 ` [PATCH] " Petr Písař
2011-04-13 14:40   ` Artem Bityutskiy [this message]
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
2011-04-13 14:55 ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2011-03-24  9:56 [PATCH] " Petr Písař
2011-03-24 10:24 ` Alan Cox
2011-03-24 14:15   ` Petr Pisar
2011-03-24 14:51     ` Alan Cox

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=1302705651.2768.21.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@suse.de \
    --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;
as well as URLs for NNTP newsgroup(s).