GitHub user mike-jumper opened a pull request:

    https://github.com/apache/incubator-guacamole-server/pull/17

    GUACAMOLE-5: Add per-user "read-only" parameter to all protocols.

    Previously, the only protocol providing a "read-only" parameter was VNC, as 
VNC servers inherently support screen sharing. Now that Guacamole supports 
screen sharing regardless of underlying protocol, such parameters should be 
provided across the board.
    
    This change adds a "read-only" parameter to the RDP, SSH, and telnet 
protocols, and extends the existing "read-only" parameter of VNC to be handled 
on a per-user (rather than per-connection) basis.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mike-jumper/incubator-guacamole-server 
read-only

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-guacamole-server/pull/17.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #17
    
----
commit 0641ccf601dda415edeee265bbfb788041a4836e
Author: Michael Jumper <[email protected]>
Date:   2016-07-25T04:34:21Z

    GUACAMOLE-5: Store connection parameters at user level. Maintain reference 
to owner's connection parameters at client level.

commit 80085890907ee014532db0cd1a5ffc7732625f4f
Author: Michael Jumper <[email protected]>
Date:   2016-07-25T04:38:53Z

    GUACAMOLE-5: Handle VNC's "read-only" parameter on a per-user basis.

commit 9eafcfd0ffba00a1233fddb95e916fdba8ab510c
Author: Michael Jumper <[email protected]>
Date:   2016-07-25T05:03:08Z

    GUACAMOLE-5: Add "read-only" parameter to RDP, SSH, and telnet (per-user, 
just like VNC).

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to