[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150903063629.GA29383@openwall.com>
Date: Thu, 3 Sep 2015 09:36:29 +0300
From: Solar Designer <solar@...nwall.com>
To: oss-security@...ts.openwall.com
Subject: Re: CVE request: screen stack overflow (deep recursion)
On Thu, Sep 03, 2015 at 05:25:11AM +0000, Fiedler Roman wrote:
> What about "tail -f /var/log/syslog", Apache or other kind of logs for
> debugging? [Yes, that's often how logs are running over the screen in videos
> when talking about IT-security]. It's convenient and I'm using screen
> exactly to avoid any injection of commands via TIOCSTI into my current TTY
> when a context switch is needed before starting tail, e.g. when working with
> LXC containers.
"tail -f" on a log file is indeed very common, but it is bad practice
(akin to other very common bad practices like a sysadmin going into a
user's homedir as root). A safer alternative in terms of terminal
escapes is the "F" keypress in "less -nU" (or in "less -nUEX" to more
closely resemble "tail -f"). Unfortunately, I am not aware of a
command-line option that would do this (that is, assume that "F" was
pressed right away) - perhaps one should be added, if it's not already
in there. Unfortunately, less is more complicated and has greater
attack surface than tail. Maybe this can be partially mitigated by
using the C locale with it (no UTF-8), but I did not look into that.
Alexander
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
