On Sun, 31 Mar 2002, martin f krafft wrote:
> > It should support encryption (I'm thinking ssh or ssl) by default, > > and compression where appropriate (a number of X protocol compression > > schemes have been proposes, but none have really taken off). > > it needn't support anything. it should use XDMCP. how you tunnel that > is up to you... Do you see the session started by this server as logging you into sessions on the remote machines ? I'd assumed that you already had started sessions on the remote displays, more like Xnest. My solution does make it difficult to run xdm on the server - the local and the remote users could become different (at least the only thing the local user can do as the remote user is access the remote display). > > It would also be nice if it could also connect to VNC servers. > > well, maybe. then again i don't see how that would be better than > regular XDMCP querying by the VNC servers? XDMCP is only a login protocol; once the user is authorized the clients revert to speaking X so, if I'm understanding correctly, that doesn't work unless your VNC server speaks X. I clearly don't understand the logic of this well enough to start implementing anything, even if I did have the time. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
