This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

Hello Răzvan


Thank you for raising this bug.



Please see: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sec-vnc-sharing-an-existing-desktop.html



Thank you

------------------


Red_Hat_Enterprise_Linux-Deployment_Guide-6-en-US-6-5.2

Hello Stephen,

Thanks, that's GREAT, but there is something to be added/clarified:

The command:

x0vncserver -PasswordFile=.vnc/passwd -AlwaysShared=1

must be given *on each ocassion* by an user standing in front of the "receiving" machine or can be used at any time (even *after* a reboot)? In other words, x0vncserver acts as a daemon (can be started automagically started at boot)

Setting a password for access, as a minimum security, is OK, but if the above command must be given explicitly every time when a user wants to receive a VNC session, the situation is less than ideal.

One can easily imagine scenarios in which the receiving user is not present (such as remote assistance & configuration provided by some administrator overnight, via VNC) or is simply not able/not wanting to type such an arcane command (non-technical users, the usual case).

Best regards,
Răzvan

(In reply to Răzvan Sandu from comment #14)
> Hello Stephen,
Hello Răzvan
> 
> Thanks, that's GREAT, but there is something to be added/clarified:
> 
> The command:
> 
> x0vncserver -PasswordFile=.vnc/passwd -AlwaysShared=1
> 
> must be given *on each ocassion* by an user standing in front of the
> "receiving" machine
Yes, if you try it you will see it runs in the terminal, even if you try to background it, and outputs logging messages.

 or can be used at any time (even *after* a reboot)? In
> other words, x0vncserver acts as a daemon (can be started automagically
> started at boot)
> 
> Setting a password for access, as a minimum security, is OK, but if the
> above command must be given explicitly every time when a user wants to
> receive a VNC session, the situation is less than ideal.

Besides the privacy issues, an administrator could connect over SSH, become that user, and then issue the command. 
> 
> One can easily imagine scenarios in which the receiving user is not present
> (such as remote assistance & configuration provided by some administrator
> overnight, via VNC) or is simply not able/not wanting to type such an arcane
> command (non-technical users, the usual case).
I agree the command is not user friendly. Perhaps a desktop icon to run the command would help?
See: https://help.gnome.org/admin/system-admin-guide/2.32/menustructure-desktopentry.html.en

Bare in mind GNOME has vino-server. See https://access.redhat.com/node/16608

I think sharing the users desktop is not required if the user is not present. You could use normal VNC or even SSH when the user is not present.
> 
> Best regards,
> Răzvan

Thank you

Regards
Stephen