Re: improve xterm(1) resilience against control code attacks

> Christian Weisgerber wrote on Mon, Mar 07, 2016 at 03:51:41PM +: > > On 2016-03-07, Ingo Schwarze wrote: > > >> Consequently, in the interest of safe and sane defaults, i propose > >> switching our xterm(1) to enable UTF-8 mode by default. > > > Seconded. Please.

Re: improve xterm(1) resilience against control code attacks

On Tue, Mar 08, 2016 at 12:14:45AM +0100, Ingo Schwarze wrote: > Hi Christian, > > Christian Weisgerber wrote on Mon, Mar 07, 2016 at 03:51:41PM +: > > On 2016-03-07, Ingo Schwarze wrote: > > >> Consequently, in the interest of safe and sane defaults, i propose > >>

Re: improve xterm(1) resilience against control code attacks

Hi Christian, Christian Weisgerber wrote on Mon, Mar 07, 2016 at 03:51:41PM +: > On 2016-03-07, Ingo Schwarze wrote: >> Consequently, in the interest of safe and sane defaults, i propose >> switching our xterm(1) to enable UTF-8 mode by default. > Seconded. >> The best

Re: improve xterm(1) resilience against control code attacks

On 2016-03-07, Ingo Schwarze wrote: > Consequently, in the interest of safe and sane defaults, i propose > switching our xterm(1) to enable UTF-8 mode by default. Seconded. > The best place to switch is in the setup function VTInitialize_locale() > that decides whether to

improve xterm(1) resilience against control code attacks

Hi, if two programs communicating encoded character strings to each other disagree about the encoding, that can result in problems. One particular example of such communication is an application program passing output text to a terminal emulator program. If the terminal uses a different