M Harris wrote: > On Thursday 31 May 2007 18:28, [EMAIL PROTECTED] wrote: >> I am trying to use KDE desktop sharing. However I am unable to login >> into the remote desktop via http > Some additional details [ how you are going to use this in your setup ] > would > be great... because there are several good ways to do this. > > I share several of my systems [ and multiple desktops ] across my > network > using vncserver, and tightvnc tunnels over ssh, to allow many users access to > several (a few) servers via shared desktops. > > I can provide a point-by-point howto, but the big picture for now is > this: > > First each server machine runs headless. From remote a user can start a > vncserver (from their userid home dir) which starts a virtual frame > buffer---and starts KDE. [ some of my users start gnome, but that's another > story ] Then the user issues a remote background command over an ssh tunnel > that starts vncviewer [ running on the server machine ] and then pipes the > vncserver back over the X11 ssh session... including password requests etc > all compressed and encrypted. This works *very* well for local area nets with > adequate speeds, eliminates the need to open a vnc port on the server, and > keeps the whole shabang secure. If the desktop needs to be *shared* then the > vncserver is started with the option to share. I have used this technique > for net-meetings and for collaboration... doesn't work well across the WAN... > but for local setups its fine. You can do a similar thing using the vncviewer > from the client machine and logging into an open vnc server port on the > host... but if you do this its a better idea to change the default server > port number to something else---- otherwise, its not a good idea. > > Directly logging in to a remote desktop isn't such a good idea... also, > its > not a real good idea to log directly into an open vnc port... or another way > to put this is that it is not a good idea to keep a vnc server port open. > With the first technique the only port open is ssh. Shipping vnc over ssh is > more secure, if not much faster----even compressed. > > Is this what you have in mind, or something else? > > > > You might want to consider vncviewer -via hostname hostname:1. This will create a ssh connection to hostname with the same user id you are running from.
-- Joseph Loo [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
