[prev in list] [next in list] [prev in thread] [next in thread] 

List:       oss-security
Subject:    Re: [oss-security] terminal emulators' processing of escape sequences
From:       Yui Hirasawa <yui () cock ! li>
Date:       2017-05-19 18:58:58
Message-ID: 20170519185858.mbilbjdi3fafgl2j () kamui ! lair
[Download RAW message or body]

On Wed, May 17, 2017 at 02:25:52AM +0200, Robert Święcki wrote:
> Hi,
>
> 2017-05-17 0:03 GMT+02:00 Solar Designer <solar@openwall.com>:
> >
> > Jason, Robert -
> >
> > On Tue, May 02, 2017 at 12:05:27AM +0200, Robert ??wi??cki wrote:
> > > A harmless example from rxvt - pushing back the new-line character:
> > >
> > > $ echo -ne "\eGQ;"
> > > ;$ 0
> > > bash: 0: command not found
> >
> > Does this also affect rxvt-unicode?
>
> Yes,
>
> Tested with rxvt-unicode-9.22
>
> $ echo -ne "\eGQ;"
> ;$ 0
> bash: 0: command not found
> $

For me on rxvt-unicode 9.22 this command goes into command mode and
executes the first command in the history, thanks to vi-mode in bash.

In clear history it of course goes into infinite loop of re-executing
itself.

Also works with the more portable `printf "\033GQ;"`
[prev in list] [next in list] [prev in thread] [next in thread]