[jira] [Assigned] (GUACAMOLE-502) Hostname / desktop name replaces connection name

["Michael Jumper (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GUACAMOLE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Jumper reassigned GUACAMOLE-502:
----------------------------------------

    Assignee: Michael Jumper

> Hostname / desktop name replaces connection name
> ------------------------------------------------
>
>                 Key: GUACAMOLE-502
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-502
>             Project: Guacamole
>          Issue Type: Bug
>          Components: RDP, VNC
>    Affects Versions: 0.9.13-incubating, 0.9.14
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>            Priority: Major
>
> All protocols currently supported by Guacamole will send the name of the connection at some point, either as part of the underlying protocol (VNC), to update the window title in response to console codes (SSH and telnet), or as a leftover convention from the early days of Guacamole where sending the name was required (RDP).
> This behavior was essentially lost as Guacamole switch over to its AngularJS-driven interface, as the "name" instruction was ignored in favor of using the connection's name, but has resurfaced as a usability bug due to GUACAMOLE-265, part of 0.9.13-incubating, which allowed SSH/telnet connections to change the window title via OSC 0.
> As the name of the connection sent via VNC and the hostname of the RDP connection are likely to be internal information, this behavior should probably be:
> # Removed entirely from RDP, as the value submitted really is just the value of the "hostname" parameter.
> # Made configurable for VNC, as it is a feature of the VNC protocol, albeit not desirable in all cases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)