<blush> Umm, anyone believe me if I said it's a typo? </blush> At anyrate thanks for the correction, it is sure to confuse people... And I'm really sorry about that... Jerry On Tuesday 22 February 2005 00:25, Ken Schneider wrote:
On Mon, 2005-02-21 at 17:17, Jerry Westrick wrote:
Hello Joe...
There are many ways to use VNC. You are trying to mix 2 diferent methods, let me explain:
User Method: ========= Here you first log into the machine, and start a private vncserver. The vncserver session runs X-Windows with you already logged on. The session remains running in back ground until you stop the session, either by killing it, or exiting the X-Windoes session. The major advantage of this method is that program you start running in the session continue running after you've disconnected, and you can connect back to it to see the results. In order to keep unwanted people off your session, VNC implements it's own password which must be provided before VNC will allow you to connect.
Preloaded User sessions =============== It is possible to "pre-start" such Users Sessions at boot time, but this leaves a bunch of X-Windows running in background eating resources and doing nothing but waiting to see if someone someday will connect to them. To avoid wasting these resources the 3 method was developed.
Init.d User Session Kickoff ================= It's possible, (although I've seldom seen it done) to have init.d kickoff a user session. Here we use the init.d program (which is light weight, and usually running anyway) to wait for someone to connect to a vnc session... Once a connection is attempted, init.d then starts a VNCServer session and passes the connection off to it. For this to work init.d is setup to start off a specific user session on a specific port. init.d is further instructed to wait for the session to end before starting another session for that port. Here you also need the VNC Password since you donot use the x-widnows login. Here you can also leave the VNC session running while disconnected.
I think you are confusing init.d with xinetd. init is used to start and stop programs as you go from one runlevel to another, such as starting and stopping the machine. xinetd is used to start programs when called upon, VNC could be one possible use.
Init.d X-Windows Login =============== The normal way this is setup is that init.d starts up the vnc Session with the X-Windows login screen, and is terminated as soon as you disconnect. This allows any number of people to connect simultaneously while not wasting resource on Sessions doing nothing. Since X-Windows is asking for the Username/password, and the password is different for each user, VNC requires no password of it's own to connect. This is similar to Windows Terminal server in that any number of people can be working on the server at the same time.
Desktop Sharing =========== It is possible with KDE (and GNOME also) to share your desktop via VNC to another machine. This is used mainly for remote support, and can be setup to require a password (or not).
Now to answer your questions:
First off, I've never seen anyone setup the VNC PASSWORD and X_WIndows login, I don't see a reason for the double password schemes. If the user is not allowed to login, then take him out of the list of user allowed to login. If he is allowed to login I don't see how a having a password shared among all user who are allowed to login is going to help security.
Are you trying to allow certain users to login locally, but not remotely? There are better ways of doing that.
As to removing the list of users from the login screen go to: Start-->Control Center->System Administration->Login manager->Users There you'll find an option called "Show List", un-check it.
Jerry
On Monday 21 February 2005 22:01, Joe Zitnik wrote:
I'm running SLES 9. I'd like to use VNC to access the server remotely, and currently it is working, but there are some issues. I would like it set up so that when I go to access the server via VNC, it asks for a VNC password. Currently, if I type "servername:5901" in the VNC server name box, I am taken directly to a SuSe log in screen. I am never prompted for a password from VNC to get that screen. I have tried using vncpasswd to set a password, but when I launch VNC remotely, it never prompts me for the password I entered. I have rebooted thinking X might need to be restarted. I would also like to set the SuSe login screen to NOT display users on the left of the login box. How can I disable this? Thanks.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
* Only reply to the list please*
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge