oss-sec mailing list archives
Re: terminal emulators' processing of escape sequences
From: Dominique Martinet <asmadeus () codewreck org>
Date: Wed, 17 May 2017 00:16:28 +0200
Solar Designer wrote on Wed, May 17, 2017:
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 foundDoes this also affect rxvt-unicode?
Yes (at least on rxvt-unicode 9.21 and 9.22) Actually, on rxvt 2.7.10 this will try to execute the command '1' instead so I'd wager they meant urxvt from the start... But both are similarily affected anyhow. -- Dominique Martinet
Current thread:
- Re: terminal emulators' processing of escape sequences, (continued)
- Re: terminal emulators' processing of escape sequences Robert Święcki (May 17)
- AW: terminal emulators' processing of escape sequences Fiedler Roman (May 17)
- Re: terminal emulators' processing of escape sequences Daniel Kahn Gillmor (May 17)
- Re: terminal emulators' processing of escape sequences Robert Święcki (May 17)
- Re: terminal emulators' processing of escape sequences Robert Święcki (May 17)
- Re: terminal emulators' processing of escape sequences Daniel Kahn Gillmor (May 18)
- Re: terminal emulators' processing of escape sequences Tavis Ormandy (May 19)
- Re: terminal emulators' processing of escape sequences Solar Designer (May 17)
- Re: terminal emulators' processing of escape sequences Marc Lehmann (May 17)
- rxvt-unicode "insecure" setting [Was: terminal emulators' processing of escape sequences] Ian Zimmerman (May 17)
- Re: terminal emulators' processing of escape sequences Dominique Martinet (May 17)
- Re: terminal emulators' processing of escape sequences Guido Berhoerster (May 03)
- Re: terminal emulators' processing of escape sequences Ryan Munz (May 08)