On Thu, Jul 22, 2010 at 07:27:28AM +0200, Martin Koegler wrote: > On Wed, Jul 21, 2010 at 12:48:05PM -0500, DRC wrote: > > On 7/21/10 3:16 AM, Adam Tkac wrote: > > > This is a valid argument but I would like to see feedback from other > > > TigerVNC developers to decide which types should be enabled by > > > default. I will open a separate thread for this. > > > > I am joining into this discussion late, so I don't think I fully > > understand how the system currently works, but IMHO, the way it should > > work is as follows: > > > > -- A set of "allowed" security types can be configured for the VNC > > server. It should be possible for a SysAdmin to specify this in a > > central config file, which will take precedence over command line > > options or per-user config files (thus, if a SysAdmin decides, for > > instance, to disable the use of VncAuth, the user can't override this > > decision.) > > If the user has shell access and the vnc server is started using the > uid of the user by the user (eg. not by inetd), a user can bypass the > sysadmin setting (eg. by starting a modified version from $HOME). > > As Xvnc can run as any user, I would like to stick to the normal user > unix default for such unprivileged programs: parameters take precedence > over config file.
+1 This is current behavior and in my opinion it is correct. > > -- The first entry in the set of allowed security types becomes the > > default security type for the viewer, but the viewer can override this > > and use any of the other allowed security types. > > I agree with this - this will require to enable all security types by > default in the viewer. As the (unused) client preference setting has > been removed, the viewer will always select the first security type of > the server, which is also enabled on the client. I reworked parsing code a little. In the current trunk client sets encoding priority. The first encoding on the client's command line has the highest priority, second supplied encoding has the second priority etc. In my opinion this behavior is better than server-side encoding priority. > > -- The default set of allowed security types for the server is the set > > of all security types that TigerVNC supports, with VncAuth being the > > first entry and VncNone being the last. Thus, any viewers that do not > > override the default will revert to using the legacy VNC password > > authentication. However, the SysAdmin can change the set of allowed > > security types on the server side to force all viewers to use something > > more secure than VncAuth. > > I would not enable the *None by default in the server, as anybody can > connect to it. Its easy to start Xvnc and forgetting to set > SecurityTypes. +1 Regards, Adam -- Adam Tkac, Red Hat, Inc. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
