You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@guacamole.apache.org by "Michael Jumper (JIRA)" <ji...@apache.org> on 2019/01/07 17:25:00 UTC

[jira] [Resolved] (GUACAMOLE-510) Nested socket index is not initialized

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

Michael Jumper resolved GUACAMOLE-510.
--------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

Fixed by GUACAMOLE-662 via commit [47ad6f4|https://github.com/apache/guacamole-server/pull/208/commits/47ad6f4b59dc861ae8f17e41885c7f2947ff2bad].

> Nested socket index is not initialized
> --------------------------------------
>
>                 Key: GUACAMOLE-510
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-510
>             Project: Guacamole
>          Issue Type: Bug
>          Components: libguac
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>            Priority: Trivial
>             Fix For: 2.0.0
>
>
> Although {{guac_socket_nest()}} takes an index parameter, this parameter is never used and the index of the socket is left uninitialized.
> This is not a problem in practice as nested sockets are no longer used (the Guacamole protocol has evolved to inherently support streaming large blocks of data and no longer needs to nest itself as a workaround). It's likely that {{guac_socket_nest()}} and the "nest" instruction should be deprecated, but this should be fixed in the meantime.



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