On Thursday 16 March 2006 11:16, J. David Boyd wrote: > Bryan Phinney <[EMAIL PROTECTED]> writes: > > There is a workaround, see above. The one issue with leaving the active > > :0 display available via remote access is that anyone accessing the local > > machine would be working with your active session. And, if you are > > active and they can access the keyboard or mouse, they can fight you for > > control. > > I would expect VNC to ask for a password before allowing a connection, the > same as it does when connecting to display :1.
Display :0 is the active console. There is no password to enter because you are already logged into the session remotely and actively using it. That session is simply being mirrored back to the local display device plugged into the video card, right? So, once the session is active (via you remotely), it is already active and no one need log in locally. The local and remote display both show the same thing. Both remote and local keyboards echo keys to the session. Both remote and local mouses will cause the pointer to move. Follow? > > There are good security reasons why you don't want to leave the local > > display active while you are accessing it remotely. > > I agree that security is all important, but I don't see why display :0 > would be any more vulnerable than display :1. Unless the kfrb thing > doesn't prompt for any password when connecting remotely? I'll have to > look at it. Because the local user doesn't need to log into a shared desktop. By definition, you are already logged in and he can watch what you are doing. Similar to remote desktop help with Windows or even with Linux, once that session is "shared" both people see and control the exact same session. ____________________________________________________ Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com Join the Club : http://www.mandrivaclub.com ____________________________________________________
