Uploaded image for project: 'Guacamole'
  1. Guacamole
  2. GUACAMOLE-790

Encode/Encrypt websocket messages

    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Minor
    • Resolution: Invalid
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      It would be nice to have a feature that will either encode, encrypt, or otherwise obfuscate the contents of the tunnel's websocket messages. For example:

      Plaintext (original):

      3.key,3.102,1.1;

      Encoded:

      3.enc,24.My5rZXksMy4xMDIsMS4xOw==;

      This would require the client app to encode the message prior to sending it to the server, as well as decoding the message upon receipt from the server prior to parsing it. Example javascript to encode prior to the socket.send(message) call in Tunnel.js:

       message = "3.enc," + getElement(btoa(message));

      Of course, you would also need similar functions for the guacamole-server.  I wasn't able to figure out how to get it to work there; it's been a while since I've touched C.  For incoming messages, after it parses these encoded messages, the "enc" handler would decode the data. Since the data is another websocket message, the handler would then need to re-parse and handle that instruction.

      Purpose: additional privacy and security in insecure environments. While TLS would encrypt the entire communication, sometimes this cannot be trusted, or sometimes organizations/higher-level entities will proxy/man-in-the-middle to decrypt and inspect TLS sessions prior to re-encrypting. In these cases, it would be nice to have a means of protecting the websocket messages so that they remain unreadable (or at least encoded/not directly readable) when running over on an untrusted network.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              travis.royer Travis Royer
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: