Ssuse 9.3 + FreeNX no connection
Posted on the FreeNX help forum, but no answer. I have FreeNX setup on a server running suse 9.3 and am trying to connect with the nx client also on suse 9.3, different machine. I get the following on the details from the client NX> 203 NXSSH running with pid: 28190 NX> 285 Enabling check on switch command NX> 285 Enabling skip of SSH config files NX> 200 Connected to address: 192.168.0.4 on port: 22 NX> 202 Authenticating user: nx NX> 208 Using auth method: publickey NX> 204 Authentication failed. I followed the installation procedure and also copied the client.id_dsa.key file to the appropriate directory on the client machine. If I run nxserver --userlist I get my logon name listed. Any help would be appreciated. Art
On Mon, 2005-08-01 at 13:08 -0700, Art Fore wrote:
Posted on the FreeNX help forum, but no answer. I have FreeNX setup on a server running suse 9.3 and am trying to connect with the nx client also on suse 9.3, different machine. I get the following on the details from the client NX> 203 NXSSH running with pid: 28190 NX> 285 Enabling check on switch command NX> 285 Enabling skip of SSH config files NX> 200 Connected to address: 192.168.0.4 on port: 22 NX> 202 Authenticating user: nx NX> 208 Using auth method: publickey NX> 204 Authentication failed.
I followed the installation procedure and also copied the client.id_dsa.key file to the appropriate directory on the client machine. If I run nxserver --userlist I get my logon name listed.
Any help would be appreciated.
When you copied the public key what file name did you use and what perms/owner did you use? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Mon, 2005-08-01 at 16:17 -0400, Ken Schneider wrote:
On Mon, 2005-08-01 at 13:08 -0700, Art Fore wrote:
Posted on the FreeNX help forum, but no answer. I have FreeNX setup on a server running suse 9.3 and am trying to connect with the nx client also on suse 9.3, different machine. I get the following on the details from the client NX> 203 NXSSH running with pid: 28190 NX> 285 Enabling check on switch command NX> 285 Enabling skip of SSH config files NX> 200 Connected to address: 192.168.0.4 on port: 22 NX> 202 Authenticating user: nx NX> 208 Using auth method: publickey NX> 204 Authentication failed.
I followed the installation procedure and also copied the client.id_dsa.key file to the appropriate directory on the client machine. If I run nxserver --userlist I get my logon name listed.
Any help would be appreciated.
When you copied the public key what file name did you use and what perms/owner did you use?
This would be the info on the client machine. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Mon, 2005-08-01 at 16:17 -0400, Ken Schneider wrote:
On Mon, 2005-08-01 at 13:08 -0700, Art Fore wrote:
Posted on the FreeNX help forum, but no answer. I have FreeNX setup on a server running suse 9.3 and am trying to connect with the nx client also on suse 9.3, different machine. I get the following on the details from the client NX> 203 NXSSH running with pid: 28190 NX> 285 Enabling check on switch command NX> 285 Enabling skip of SSH config files NX> 200 Connected to address: 192.168.0.4 on port: 22 NX> 202 Authenticating user: nx NX> 208 Using auth method: publickey NX> 204 Authentication failed.
I followed the installation procedure and also copied the client.id_dsa.key file to the appropriate directory on the client machine. If I run nxserver --userlist I get my logon name listed.
Any help would be appreciated.
When you copied the public key what file name did you use and what perms/owner did you use?
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
It is client.id_dsa.key which I copied into /usr/NX/share and file permissions are root root rwxr-xr-x. That was per the instructions on the website. Maybe I missed something. Art
On Mon, 2005-08-01 at 19:24 -0700, Art Fore wrote:
On Mon, 2005-08-01 at 16:17 -0400, Ken Schneider wrote:
On Mon, 2005-08-01 at 13:08 -0700, Art Fore wrote:
Posted on the FreeNX help forum, but no answer. I have FreeNX setup on a server running suse 9.3 and am trying to connect with the nx client also on suse 9.3, different machine. I get the following on the details from the client NX> 203 NXSSH running with pid: 28190 NX> 285 Enabling check on switch command NX> 285 Enabling skip of SSH config files NX> 200 Connected to address: 192.168.0.4 on port: 22 NX> 202 Authenticating user: nx NX> 208 Using auth method: publickey NX> 204 Authentication failed.
I followed the installation procedure and also copied the client.id_dsa.key file to the appropriate directory on the client machine. If I run nxserver --userlist I get my logon name listed.
Any help would be appreciated.
When you copied the public key what file name did you use and what perms/owner did you use?
It is client.id_dsa.key which I copied into /usr/NX/share and file permissions are root root rwxr-xr-x. That was per the instructions on the website. Maybe I missed something.
The file on the local pc, the one doing ssh, should reside under /home/<user login>/.ssh/id_dsa.pub and be owned by the user. The same file will be on the remote machine as ~/.ssh/authorized_keys and also owned by the user. Hope this helps. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Mon, 2005-08-01 at 22:54 -0400, Ken Schneider wrote:
On Mon, 2005-08-01 at 19:24 -0700, Art Fore wrote:
On Mon, 2005-08-01 at 16:17 -0400, Ken Schneider wrote:
On Mon, 2005-08-01 at 13:08 -0700, Art Fore wrote:
Posted on the FreeNX help forum, but no answer. I have FreeNX setup on a server running suse 9.3 and am trying to connect with the nx client also on suse 9.3, different machine. I get the following on the details from the client NX> 203 NXSSH running with pid: 28190 NX> 285 Enabling check on switch command NX> 285 Enabling skip of SSH config files NX> 200 Connected to address: 192.168.0.4 on port: 22 NX> 202 Authenticating user: nx NX> 208 Using auth method: publickey NX> 204 Authentication failed.
I followed the installation procedure and also copied the client.id_dsa.key file to the appropriate directory on the client machine. If I run nxserver --userlist I get my logon name listed.
Any help would be appreciated.
When you copied the public key what file name did you use and what perms/owner did you use?
It is client.id_dsa.key which I copied into /usr/NX/share and file permissions are root root rwxr-xr-x. That was per the instructions on the website. Maybe I missed something.
The file on the local pc, the one doing ssh, should reside under /home/<user login>/.ssh/id_dsa.pub and be owned by the user. The same file will be on the remote machine as ~/.ssh/authorized_keys and also owned by the user. Hope this helps.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
The authorized_keys was authorized_keys2 on the server. Copied it to the client as you said and renamed it to id_dsa.pub. Still the same thing and it was owned by me, the user, on both client and server. Art
On Mon, 2005-08-01 at 22:54 -0400, Ken Schneider wrote:
On Mon, 2005-08-01 at 19:24 -0700, Art Fore wrote: The file on the local pc, the one doing ssh, should reside under /home/<user login>/.ssh/id_dsa.pub and be owned by the user. The same file will be on the remote machine as ~/.ssh/authorized_keys and also owned by the user. Hope this helps.
The key should be generated on the client and there will be two files created in the directory you are in when created, id_dsa and id_dsa.pub in .ssh dir. You need put them in the local .ssh dir and copy the id_dsa.pub file to the remote PC and name it authorized_keys in .ssh
On Mon, 2005-08-01 at 21:07 -0700, Art Fore wrote: dir. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
How do I generate this key on the client? Art Ken Schneider wrote:
On Mon, 2005-08-01 at 21:07 -0700, Art Fore wrote:
On Mon, 2005-08-01 at 22:54 -0400, Ken Schneider wrote:
On Mon, 2005-08-01 at 19:24 -0700, Art Fore wrote: The file on the local pc, the one doing ssh, should reside under /home/<user login>/.ssh/id_dsa.pub and be owned by the user. The same file will be on the remote machine as ~/.ssh/authorized_keys and also owned by the user. Hope this helps.
The key should be generated on the client and there will be two files created in the directory you are in when created, id_dsa and id_dsa.pub in .ssh dir. You need put them in the local .ssh dir and copy the id_dsa.pub file to the remote PC and name it authorized_keys in .ssh dir.
On Tue, 2005-08-02 at 08:47 -0700, Art Fore wrote:
How do I generate this key on the client?
Art
Ken Schneider wrote:
On Mon, 2005-08-01 at 21:07 -0700, Art Fore wrote:
On Mon, 2005-08-01 at 22:54 -0400, Ken Schneider wrote:
On Mon, 2005-08-01 at 19:24 -0700, Art Fore wrote: The file on the local pc, the one doing ssh, should reside under /home/<user login>/.ssh/id_dsa.pub and be owned by the user. The same file will be on the remote machine as ~/.ssh/authorized_keys and also owned by the user. Hope this helps.
The key should be generated on the client and there will be two files created in the directory you are in when created, id_dsa and id_dsa.pub in .ssh dir. You need put them in the local .ssh dir and copy the id_dsa.pub file to the remote PC and name it authorized_keys in .ssh dir.
Follow this thread in the archives: http://lists.suse.com/archive/suse-linux-e/2005-Jun/1841.html You can search the archives using google. For this I used: site:lists.suse.com [SLE] id_dsa.pub 9.3 and had one listing. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
participants (3)
-
Art Fore -
Ken Schneider -
William Gallafent