Mailinglist Archive: opensuse (1714 mails)

< Previous Next >
Re: [opensuse] Xvnc documentation?
  • From: Marc Chamberlin <marc@xxxxxxxxxxxxxxxxxx>
  • Date: Fri, 02 Jul 2010 09:23:13 -0700
  • Message-id: <4C2E1271.7070900@xxxxxxxxxxxxxxxxxx>
On 7/2/2010 2:01 AM, David C. Rankin wrote:
On 07/02/2010 02:29 AM, Marc Chamberlin wrote:
I have been using vncviewer from Linux clients, and RealVNC viewer from Windoz
clients. KRDC will not let me type in a password for some odd reason so I
cannot use it when I have the server set up to require authorization, but it
might work if no password authorization is used....



Nonsense. I use a password with vncserver/vncviewer on a daily basis. When you start your first session on the server, starting 'vncserver -geometry XxY -depth 16 :1' you are prompted for a session password that the client will have to use to connect. On every subsequent server start, the server will default to that password. If you set it up without a password, then you can delete the ~/.vnc/passwd file and set it again. Then when you connect from the client you will always be prompted for a password. HTH..

David -

No no, I wasn't referring to vnccserver or vncviewer at all... Sorry if I was confusing! I was talking explicitly about using KRDC (it is a vnc client and part of KDE's stuff I believe) as the client only. I cannot get KRDC to let me type in a password, even though it will bring up a password prompt window when it connects to a vnc server that requires one. My suggestion was only to say that if one wants to use KRDC as their client, then it might work if it is connecting to some sort of vnc server that does not require password authorization....

Vncviewer works fine for me, when I connect to any working password protected vnc server, such as x11vnc or RealVNC, as I am using and vncserver as you are using.. I don't consider Xvnc or Krfb (KDE's vnc server) as working vnc servers at the moment, both have been broken for years now and I am giving up hope that they will ever be fixed.... same applies to KRDC. IMHO openSuSE ought to drop these from their default releases until they are fixed, as it will really confuse users and newbies in particular, and cause a lot of aggravation.

Using x11vnc (or perhaps vncserver or tightVNC) is an alternative approach that could be picked up and used as a replacement preconfigured xinetd daemon service... But x11vnc needs to be configured if possible, or redesigned to use PAM so that users/administrators don't have to do their own password configuration. (dunno about tightVNC or vncserver, and whether they can even be configured to run as an xinetd daemon) Then the x11vnc service (or perhaps tightVNC, vncserver) could just use the default system authorization services instead...

I might poke at both of these issues further, if I have some spare time...


Marc Chamberlin

A man said unto the universe - "Sir I Exist!"
"However" replied the universe
"I do not see where that creates in me a sense of
an obligation" S Crane.

< Previous Next >