[
https://issues.apache.org/jira/browse/GUACAMOLE-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17468082#comment-17468082
]
Nick Couchman edited comment on GUACAMOLE-1267 at 1/3/22, 5:07 PM:
-------------------------------------------------------------------
Is the goal to disable remote input, or disable local input? Remote input would
be disabling input from the VNC protocol, which I believe already exists?
Disabling local input would disable local keyboard/mouse when VNC is connected,
allowing only remote (VNC) input.
UPDATE: Nevermind, answered my own question by looking at the pull request -
goal is to disable local (=Server) input when VNC is connected.
was (Author: [email protected]):
Is the goal to disable remote input, or disable local input? Remote input would
be disabling input from the VNC protocol, which I believe already exists?
Disabling local input would disable local keyboard/mouse when VNC is connected,
allowing only remote (VNC) input.
> Add option to the vnc protocol to disable remote input
> ------------------------------------------------------
>
> Key: GUACAMOLE-1267
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1267
> Project: Guacamole
> Issue Type: New Feature
> Components: Documentation, VNC
> Reporter: Stefan Feenstra
> Priority: Minor
>
> For security reasons it can be a required feature to have remote input
> disabled when using the VNC protocol (e.g. on remote costumer facing
> terminals, self service terminals etc).
>
> Suggested solution is to add a setting "disable-server-input" which when set
> will send a message to the VNC client asking to disable the input.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
