Nicola Ruggero <nic...@...> writes: > Hi, xrdp runs Xvnc with a parameter that tells Xvnc to use > $HOME/.vnc/sesman_$USERNAME_passwd as password file. > This means that Xvnc (launched by xrdp will match the password against > that file). See vncpasswd. > > So you have to create a $HOME/.vnc/sesman_$USERNAME_passwd with the > same unix password and it should work!
Hi again Nicola, Now I am REALLY confused! 1. Logged on to the Terminal Server console as my test user. Ran vncpasswd. It said that it was using /root/.vnc/passwd! Puzzled, but pressing on, I provided the password for my test user (didn't bother with a RO password). It told me that it was truncating it to 8 char. Again, puzzled by what the consequences of this are, but in true myopic style, I pressed on. I now had a /root/.vnc/passwd file, which I copied and overwrote the $HOME/.vnc/sesman_$USERNAME_passwd. And low and behold, when tested from a remote client, using my test user credentials, it worked! Working, meaning, that I now get an xrdp login dialog AND a KDE login dialog that requires the same user credentials to be entered. Is this to be expected? 2. Always wishing to understand what/how it works, I deleted all copies of */.vnc/*.passwd and tested again. You can guess my surprise when the remote client was still able to connect. How on earth is this happening? If xrdp needed a password file to work, how is it now working without one now?????? Regards, Martin ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ xrdp-devel mailing list xrdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xrdp-devel
