From owner-freebsd-security@FreeBSD.ORG  Fri Apr 22 03:49:59 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 A63C616A4CE
	for <freebsd-security@freebsd.org>;
	Fri, 22 Apr 2005 03:49:59 +0000 (GMT)
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.202])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 56F3D43D1D
	for <freebsd-security@freebsd.org>;
	Fri, 22 Apr 2005 03:49:59 +0000 (GMT)
	(envelope-from pergesu@gmail.com)
Received: by zproxy.gmail.com with SMTP id 40so754564nzk
	for <freebsd-security@freebsd.org>;
	Thu, 21 Apr 2005 20:49:58 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=d8Je2xIjJhPCRy3eB9OA6AbQppGWB9PCPSCHFIGYhSMqKHk9zMk1ebOHryUWVSz6AwRUk1jIGk84f+8Xo9EStGdPH74YbDXGJrw9LAOrSj25rN5piaiMvQ41UddHZrdAEr0O6bhW1NWIA7Rg97rpeOQXRiH1Bab1kLfV5jPrL1w=
Received: by 10.36.36.13 with SMTP id j13mr251438nzj;
        Thu, 21 Apr 2005 20:49:58 -0700 (PDT)
Received: by 10.36.48.9 with HTTP; Thu, 21 Apr 2005 20:49:58 -0700 (PDT)
Message-ID: <810a540e05042120493eb79da0@mail.gmail.com>
Date: Thu, 21 Apr 2005 21:49:58 -0600
From: Pat Maddox <pergesu@gmail.com>
To: freebsd-security@freebsd.org
In-Reply-To: <42686A29.7090900@hackunite.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <42686A29.7090900@hackunite.net>
Subject: Re: Information disclosure?
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Pat Maddox <pergesu@gmail.com>
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 03:49:59 -0000

No, it's not meant to clear the buffer.  If you need to clear the
buffer, just cat a really, really long file.



On 4/21/05, Jesper Wallin <jesper@hackunite.net> wrote:
> Hello,
>=20
> For some reason, I thought little about the "clear" command today..
> Let's say a privileged user (root) logs on, edit a sensitive file (e.g,
> a file containing a password, running vipw, etc) .. then runs clear and
> logout. Then anyone can press the scroll-lock command, scroll back up
> and read the sensitive information.. Isn't "clear" ment to clear the
> backbuffer instead of printing a full screen of returns? If it does, I'm
> not sure how that would effect a user running "clear" on a pty (telnet,
> sshd, screen, etc) ..
>=20
> Best regards,
> Jesper Wallin
>=20
> _______________________________________________
> freebsd-security@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-security
> To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.or=
g"
>