Michael Jumper commented on GUACAMOLE-681:

I'm able to reproduce what I think may be the same issue through a slightly 
different sequence. The terminal emulator in 0.9.14 will segfault if you 
attempt to use that particular OSC sequence to assign a named color that is not 
defined. For example, the following will work just fine:

echo -en "\x1B]4;3;blue\x07"

whereas the following will result in the connection dying:

echo -en "\x1B]4;3;blarb\x07"

That particular bug was fixed by [~jimnchen] with commit 
 for related changes for GUACAMOLE-470 and is part of the upcoming 1.0.0 
release. If you can reliably reproduce this with 0.9.14, I suggest trying to 
reproduce against the staging/1.0.0 branch and see if this still occurs.

> Console codes crashing SSH
> --------------------------
>                 Key: GUACAMOLE-681
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-681
>             Project: Guacamole
>          Issue Type: Bug
>          Components: SSH
>    Affects Versions: 0.9.14
>         Environment: Newest docker versions of guacd and guacamole, running 
> on Unraid. Client is connecting from Chromium on Arch Linux.
>            Reporter: Patrick Collins
>            Priority: Critical
> Based on 
> [this|https://issues.apache.org/jira/projects/GUACAMOLE/issues/GUACAMOLE-277] 
> issue, it seems Guacamole is supposed to work with Linux console codes.
> I'm getting reliable crashes when printing certain console codes in a 
> Guacamole SSH session; notably ones printed by .bashrc in [some 
> configurations|https://github.com/dylanaraps/pywal].
> When printed directly on the device, (whether on a tty or a terminal 
> emulator,) the codes work.
> When printed in Guacamole, they immediately crash the session; prompting 
> reconnection.
> This command is enough to crash the session:
> {code:java}
> echo 1b5d343b0a | xxd -r -p{code}
> (It converts some hex to 'ESC []4;' and prints it.)
> Apologies if the priority of this issue is inappropriate; I based it off the 
> "crashes" criterion; but I'm not certain to what extent the program has to 
> crash to qualify.

This message was sent by Atlassian JIRA

Reply via email to