On 2005-04-22 06:21, Jesper Wallin <jesper@www.hackunite.net> wrote:
>Pat Maddox wrote:
>>On 4/21/05, Jesper Wallin <jesper@hackunite.net> 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) ..
>>
>>No, it's not meant to clear the buffer. If you need to clear the
>>buffer, just cat a really, really long file.
>
> Heh, that sounds more like a ugly hack than a solution if you ask me.
Who has physical access to your consoles and why?
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
_______________________________________________
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"