[policy-1.9-5] VNC module in X AVC
Aleksey Nogin
aleksey at nogin.org
Sun Mar 21 03:09:53 UTC 2004
On 20.03.2004 18:56, Russell Coker wrote:
> What exactly does Xvnc do?
It starts a "virtual" X server - it does not attemts to interact with
the local hardware, but it will listen on 6000+display port as a normal
X server (so the clients can connect) and it will listen on the
5900+display port, so that the vncviewer clients can connect (possibly
remote, possibly several simultaneously) and on port 5800+display for
http requests (essentially providing a Java version of the VNC client).
> Does it do the same sort of stuff as when the user
> runs "startx" but for remote display only?
This is different. Normally Xvnc is started by the /usr/bin/vncserver
script (there is also /etc/rc.d/init.d/vncserver script which might need
a separate treatment), which would first start Xvnc and then start
appropriate X clients to the newly created display.
--
Aleksey Nogin
Home Page: http://nogin.org/
E-Mail: nogin at cs.caltech.edu (office), aleksey at nogin.org (personal)
Office: Jorgensen 70, tel: (626) 395-2907
More information about the fedora-selinux-list
mailing list