From owner-freebsd-security@FreeBSD.ORG  Fri Apr 22 14:47:42 2005
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id CD5F616A4CE; Fri, 22 Apr 2005 14:47:42 +0000 (GMT)
Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 398EF43D69; Fri, 22 Apr 2005 14:47:42 +0000 (GMT)
	(envelope-from dean@dragon.stack.nl)
Received: from dragon.stack.nl (dragon.stack.nl
	[IPv6:2001:610:1108:5011:207:e9ff:fe09:230])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mailhost.stack.nl (Postfix) with ESMTP id 4AF291F3D6;
	Fri, 22 Apr 2005 16:47:41 +0200 (CEST)
Received: by dragon.stack.nl (Postfix, from userid 1600)
	id 185585F157; Fri, 22 Apr 2005 16:47:41 +0200 (CEST)
Date: Fri, 22 Apr 2005 16:47:41 +0200
From: Dean Strik <dean@stack.nl>
To: Giorgos Keramidas <keramida@freebsd.org>
Message-ID: <20050422144740.GB81889@dragon.stack.nl>
References: <42686A29.7090900@hackunite.net>
	<810a540e05042120493eb79da0@mail.gmail.com> <42687BDD.6000008@hackunite.net>
	<20050422115200.GA58483@orion.daedalusnetworks.priv>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050422115200.GA58483@orion.daedalusnetworks.priv>
X-Editor: VIM Rulez! http://www.vim.org/
X-MUD: Outerspace - telnet://mud.stack.nl:3333
X-Really: Yes
User-Agent: Mutt/1.5.9i
cc: freebsd-security@freebsd.org
cc: Pat Maddox <pergesu@gmail.com>
cc: Jesper Wallin <jesper@www.hackunite.net>
Subject: Re: Information disclosure?
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Security issues [members-only posting]
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Apr 2005 14:47:42 -0000

Giorgos Keramidas wrote:
> Putting "deliberate paranoia" aside for a while, you can always _force_
> the syscons buffer to be cleared by toggling between a couple of
> different video modes:
> 
> 	# vidcontrol 80x30 ; vidcontrol 80x25 ; clear ; logout

vidcontrol -C is simpler and actually works :-)
Changing the videomodes doesn't generally clear the buffer.

-- 
Dean C. Strik             Eindhoven University of Technology
dean@stack.nl  |  dean@ipnet6.org  |  http://www.ipnet6.org/
"This isn't right. This isn't even wrong." -- Wolfgang Pauli