RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 714687 - RFE: Clear screen including scroll-back buffer before log-in
Summary: RFE: Clear screen including scroll-back buffer before log-in
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: mingetty
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Petr Pisar
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On: 714684 806803
Blocks: 836165 947781 1159824
TreeView+ depends on / blocked
 
Reported: 2011-06-20 12:52 UTC by Petr Pisar
Modified: 2016-07-26 08:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 691406
Environment:
Last Closed: 2016-07-26 08:31:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Petr Pisar 2011-06-20 12:52:17 UTC 
+++ This bug was initially created as a clone of Bug #691406 +++

There was a discussion (bug #681600) how to disable access to text printed by previous user on the console to prevent sensitive data leak.

mingetty should instruct Linux virtual terminal to clear screen including scroll-back buffer. Once Linux will implement it (bug #684261), adapt mingetty to perform the safe clear.

Because current behavior is not to clear the screen and there can be demand not to do it always (e.g. to debug broken login shell or to investigate init scripts output on /dev/console), new mingetty positional argument will be added to switch on/off the screen cleaning.

--- Additional comment from ppisar on 2011-06-10 09:38:26 GMT ---

F16 delivers kernel-3.0* that supports \E[3;J to clear screen including scroll-back buffer.

F16 uses systemd as init that by default reallocate VT before spawning mingetty, thus the scroll-back buffer is always empty.

To test this bug report, one can use following command:

# openvt -f -c 10 -s -w -- /bin/bash \
  -c 'dmesg; exec /sbin/mingetty --loginprog=/bin/false tty10'

This allocates TTY10, switches console there, pollutes buffer with kernel log, and then executes mingetty. Now it's possible to press Shift-PgUp to verify the buffer has gone.

I will add new positional argument to mingetty to enable safe console clearing. The clearing will be done by issuing the the new escape sequence followed by the older 2J variant to clean at least current visible area if mingetty run on system not supporting the new 3J sequence.

--- Additional comment from ppisar on 2011-06-10 11:31:31 GMT ---

Se there is already --noclear option defaulting to clear. So adding the new sequence seems to be enough.

--- Additional comment from ppisar on 2011-06-10 12:26:42 GMT ---

Created attachment 504091 [details]
Implementation

Tested with Linux 3.0-0.rc2.git0.1.fc16.x86_64 on VGA console.
-----

Based on discussion with Steve Grubb, I propose this feature for RHEL-6.2 as an
alternative to disabled scroll-back buffer.
Comment 1 RHEL Program Management 2011-07-06 00:06:38 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 3 Suzanne Logcher 2012-01-31 21:16:08 UTC 
This request was evaluated by Red Hat Product Management for inclusion in the
current release of Red Hat Enterprise Linux. Because the affected component is
not scheduled to be updated in the current release, Red Hat is unfortunately
unable to address this request at this time.  It has been proposed for the next
release. If you would like it considered as an exception in the current
release, please ask your support representative.
Comment 4 RHEL Program Management 2013-10-14 01:04:02 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 7 Petr Pisar 2016-07-26 08:31:13 UTC 
Red Hat Enterprise Linux version 6 is entering the Production 2 phase of its lifetime and this bug doesn't meet the criteria for it, i.e. only high severity issues will be fixed. Please see https://access.redhat.com/support/policy/updates/errata/ for further information.
Note You need to log in before you can comment on or make changes to this bug.