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 2018/01/26 23:59:00 UTC

[jira] [Assigned] (GUACAMOLE-489) Secondary socket of "tee" socket is not threadsafe

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

Michael Jumper reassigned GUACAMOLE-489:
----------------------------------------

    Assignee: Michael Jumper

> Secondary socket of "tee" socket is not threadsafe
> --------------------------------------------------
>
>                 Key: GUACAMOLE-489
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-489
>             Project: Guacamole
>          Issue Type: Bug
>          Components: libguac
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>            Priority: Trivial
>
> While working on GUACAMOLE-313, it was discovered that the "tee" implementation of {{guac_socket}} (created through a call to {{guac_socket_tee()}}) only actually locks/unlocks the primary socket when sending instructions. This means that instructions which are manually sent along the secondary socket may overlap with instructions written through the tee socket, resulting in protocol errors.
> Both primary and secondary sockets should be threadsafe relative to instruction writes on the tee socket.



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