On Fri, 2005-08-05 at 20:47 -0400, Ken Schneider wrote:
On Fri, 2005-08-05 at 17:24 -0700, Art Fore wrote:
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.
Went to the link you gave, still no luck. Here is what I did and what I got: afore@linux:~> ssh-keygen -t dsa Generating public/private dsa key pair. Enter file in which to save the key (/home/afore/.ssh/id_dsa): Enter passphrase (empty for no passphrase):
Just hit enter so you don't need to type a password. If you supply a password why not use just ole ssh.
Enter same passphrase again: Your identification has been saved in /home/afore/.ssh/id_dsa. Your public key has been saved in /home/afore/.ssh/id_dsa.pub.
copied the id_dsa.pub from local machine to server /afore/.ssh/authroized_keys.
Is this a typo or did you actually spell it authroized_keys? Check the spelling again.
-- 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 authroized is a typo. The file name is authorized_keys. Tried uninstalling everyting on the server, and reinstalling following an email on the freenx site for suse 9.3. Still get NX> 203 NXSSH running with pid: 18116 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. Why is authenticating user nx? seems like it should be afore. Also tried KNX, still no connection Art