A couple of questions - *very* high level ones (which may just mean I'm
missing something):
1) We have the Vino client. Here we are integrating the RealVNC server.
Why are we mixing and matching here? RealVNC provides a very
similar client (or two it seems).
2) Volatile seems low for this, based on my "meager, but non-null"
understanding
of the RealVNC project. Is this a "keep it Volatile for now,
higher later" type
of thing or is there some other reason?
- thanks,
- jek3
Alan Coopersmith wrote:
> I am sponsoring this case for myself and requesting a patch release binding.
> I've set the timeout for Tuesday, October 9.
>
> There are a number of supplementary documents in the case materials.
> These are visible now on the internal ARC web/file server and should
> be mirrored shortly to the external ARC web server at:
> http://www.opensolaris.org/os/community/arc/caselog/2007/545/
>
>
> ------------------------------------------------------------------------
>
> This case delivers Xvnc, an X server that displays to a Remote Frame
> Buffer (RFB) protocol client over the network. RFB clients, better
> known as VNC viewers, are available for most platforms, in both open
> source and commercial flavors. The Vino project (LSARC 2006/371)
> already delivers a VNC viewer to Solaris, along with a VNC server
> that can capture the display from a running session on a normal X server.
>
> The Xvnc implementation in this case is RealVNC 4.1.2, the current
> open source version of the code base maintained by a company formed by
> some of the original VNC authors. For the X server portions of Xvnc,
> this implementation uses the Xorg sources already in the X
> consolidation to reduce the maintenance burden and to share the
> existing Solaris enhancements in the Xorg sources, including the
> Xserver dtrace provider probes and Trusted Extensions support.
>
> Besides the Xvnc server itself, this case delivers the vncpasswd command
> used to set the password for connecting to the server, and the vncserver
> script to allow endusers to more easily start the Xvnc server. (The VNC
> authentication scheme, including vncpasswd, is described in more detail
> in the security questionnaire in [1].)
>
> This project will add /usr/X11/bin/Xvnc to the set of X servers which
> may be started by the /usr/X11/bin/Xserver script & x11-server SMF service.
>
> Imported interfaces:
> --------------------
> Vino Java Client External LSARC 2006/371
> Trusted Solaris X Server Extension Evolving LSARC 2004/109
> Xserver dtrace provider Uncommitted PSARC 2006/609
> svc:/application/x11/x11-server Evolving PSARC 2004/752
> /usr/X11/bin/Xserver Evolving PSARC 2004/752
> Xorg server interfaces (various) PSARC 2004/187,
> PSARC 2004/685,
> PSARC 2005/450,
> PSARC 2007/051,
> PSARC 2007/434
>
> Exported interfaces:
> --------------------
> SUNWxvnc package Uncommitted
> /usr/bin/vncpasswd Volatile [3]
> /usr/bin/vncserver Volatile [4]
> /usr/X11/bin/Xvnc Volatile [5]
>
> References: (located in case materials directory)
>
> 1) Xvnc-security.txt - Security Questionnaire
> 2) rfbproto.pdf - RFB Protocol Spec Version 3.8
> 3) vncpasswd.man.txt - vncpasswd(1) man page
> 4) vncserver.man.txt - vncserver(1) man page
> 5) Xvnc.man.txt - Xvnc(1) man page
>
