lø., 08.12.2007 kl. 08.26 -0500, skrev Brett Serkez: > On Dec 8, 2007 7:25 AM, Kulbir Saini <kulbirsaini@xxxxxxxxxxxxxxxxxxx> wrote: > > > > Problem: When I login to my system using 'vncviewer <IP>:0', i can access > > everything on the remote pc but the problem is the screen on server system > > (system with <IP>) unlocks and everything that I do remotely is replicated > > on the actual system. > > > > Somebody will say, wtf? it is designed to be so. But the problem is the > > screen unlocks and anybody in my lab can capture my system and do whatever > > he/she wants. > > > > Its a big security issue. > > > > And somebody may even get a heart attack when he/she sees that the mouse is > > static and no human being is near the pc and still the windows are opening > > and closing and some text is being typed in terminal :-O :P > > This is working as designed. You can use the vncserver daemon to > create virtual desktops, as many as the system resources of your > system can support, these will not be visible on the desktop. Then > you can connect to any of these virtual desktops from the console or > remotely as you desire. > Then shouldn't this be the default for vino when sharing the dekstop? I guess the case where the screen unlocks and everything is shown on the screen is great in the case where support staff wants to show users what to do on screen, but is that really the most relevant case? Cheers Kjartan -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
