From: Manuel Schoelling <manuel.schoelling@gmx.de>
To: Jakub Wilk <jwilk@debian.org>
Cc: plagnioj@jcrosoft.com, tomi.valkeinen@ti.com,
geert@linux-m68k.org, broonie@linaro.org, rdunlap@infradead.org,
dh.herrmann@gmail.com, airlied@redhat.com, mtosatti@redhat.com,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] console: Add persistent scrollback buffers for all VGA consoles
Date: Sat, 31 May 2014 11:49:24 +0200 [thread overview]
Message-ID: <1401529764.4646.12.camel@schoellingm.dzne.de> (raw)
In-Reply-To: <20140530222622.GA1385@jwilk.net>
On Sa, 2014-05-31 at 00:26 +0200, Jakub Wilk wrote:
> * Manuel Schölling <manuel.schoelling@gmx.de>, 2014-05-30, 15:27:
> >Add a scrollback buffers for each VGA console. The benefit is that the
> >scrollback history is not flushed when switching between consoles but
> >is persistent.
>
> Some people rely on this scrollback flushing as a security feature. Is
> there even another way to clear the scrollback, than to switch to
> another vt and then back again?
Thanks for raising this security issue! Maybe we should add something
like VT_FLUSH_SCROLLBACK to vt_ioctl()? [1]
I'm open for better ways to flush the scrollback history.
[1] http://lxr.free-electrons.com/source/drivers/tty/vt/vt_ioctl.c#L334
> Debian ships this:
> http://manpages.debian.org/cgi-bin/man.cgi?query=clear_console
> https://sources.debian.net/src/bash/4.2%2Bdfsg-0.1/debian/clear_console.c
>
next prev parent reply other threads:[~2014-05-31 9:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 13:27 Manuel Schölling
2014-05-30 14:28 ` Geert Uytterhoeven
2014-05-30 14:57 ` Manuel Schoelling
2014-05-30 17:06 ` Randy Dunlap
2014-05-30 22:26 ` Jakub Wilk
2014-05-31 9:49 ` Manuel Schoelling [this message]
2016-04-23 10:07 Manuel Schölling
2016-05-02 17:59 Manuel Schölling
2016-05-09 10:39 Manuel Schölling
2016-05-16 11:25 Manuel Schölling
2016-05-23 21:07 Manuel Schölling
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=1401529764.4646.12.camel@schoellingm.dzne.de \
--to=manuel.schoelling@gmx.de \
--cc=airlied@redhat.com \
--cc=broonie@linaro.org \
--cc=dh.herrmann@gmail.com \
--cc=geert@linux-m68k.org \
--cc=jwilk@debian.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=plagnioj@jcrosoft.com \
--cc=rdunlap@infradead.org \
--cc=tomi.valkeinen@ti.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
all inboxes | Powered by JetHome®