From owner-freebsd-security@FreeBSD.ORG  Fri Apr 22 06:19:25 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 CC4CA16A4CE
	for <freebsd-security@freebsd.org>;
	Fri, 22 Apr 2005 06:19:25 +0000 (GMT)
Received: from Neo-Vortex.net (203-173-19-223.dyn.iinet.net.au
	[203.173.19.223])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 96DAB43D41
	for <freebsd-security@freebsd.org>;
	Fri, 22 Apr 2005 06:19:24 +0000 (GMT)
	(envelope-from root@Neo-Vortex.net)
Received: from localhost.Neo-Vortex.got-root.cc
	(Neo-Vortex@localhost.Neo-Vortex.got-root.cc [127.0.0.1])
	by Neo-Vortex.net (8.13.1/8.12.10) with ESMTP id j3M6JMNg012902;
	Fri, 22 Apr 2005 16:19:22 +1000 (EST)
	(envelope-from root@Neo-Vortex.net)
Date: Fri, 22 Apr 2005 16:19:22 +1000 (EST)
From: Neo-Vortex <root@Neo-Vortex.net>
To: Jesper Wallin <jesper@www.hackunite.net>
In-Reply-To: <42686A29.7090900@hackunite.net>
Message-ID: <20050422161428.X11893@Neo-Vortex.net>
References: <42686A29.7090900@hackunite.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-security@freebsd.org
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 06:19:25 -0000

i had the same thing, although i wanted it for all logouts, my hack works
fairly well unless you use telnet or serial consoles, but works fine for
the normal console and ssh :)

edit /etc/gettytab and there should be a line that looks like this:

default:\
        :cb:ce:ck:lc:fd#1000:im=<snip>\
        :if=/etc/issue:

pretty much, change it to look like this

default:\
	:cb:ce:ck:lc:fd#1000:im=\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n<snip>\f\r\n%s/%m (%h) (%t)\r\n\r\n:sp#1200:\
        :if=/etc/issue:

(sorry if it looks ugly on some systems :P)

but yeah, just fill it up with \r\n - if you use telnet or a serial
console, when it shows the logon screen you have a long wait... but for
the console its fine :) clears when you logout (i think you have to send
signal 1 to init) or just reboot

also, clear just sends a \f - or was it \l, i forgot wich clears it, it
dosent send a screenful of new lines :)

~Neo-Vortex

On Fri, 22 Apr 2005, Jesper Wallin wrote:

> Hello,
>
> 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) ..
>
>
> Best regards,
> Jesper Wallin
>
>
> _______________________________________________
> freebsd-security@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-security
> To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"
>