I want do ssh without password from windows to AIX. I can use putty and WinScp tool to do it. However, when I use ssh secure shell, I still need input password to login AIX
I use the following steps to do:
Keys Generated with ssh-keygen2
In order to set up user public-key authentication, do a manual setup according to the following instructions.
The following terms will be used in this example: Remote is the SSH Secure Shell server into which you are trying to connect. RemoteUser is the user name on the server into which you would like to login. Local is the machine running a SSH Secure Shell client. LocalUser is the user name on the client machine that should be allowed to login to Remote as RemoteUser.
To make sure that public-key authentication is enabled, the AllowedAuthentications field in both the /etc/ssh2/sshd2_config file on Remote and in the /etc/ssh2/ssh2_config file on Local should contain the word publickey:
AllowedAuthentications publickey
Other authentication methods can be listed in the configuration file as well.
Create a key pair by executing ssh-keygen2 on Local.
Local> ssh-keygen2
Generating 2048-bit dsa key pair
1 oOo.oOo.o
Key generated.
2048-bit dsa, user@Local, Wed Mar 22 2002 00:13:43 +0200
Passphrase :
Again :
Private key saved to /home/user/.ssh2/id_dsa_2048_a
Public key saved to /home/user/.ssh2/id_dsa_2048_a.pub
Ssh-keygen2 will now ask for a passphrase for the new key. Enter a sufficiently long (20 characters or so) sequence of any characters (spaces are OK). Ssh-keygen2 creates a .ssh2 directory in your home directory (if it is not already present), and stores your new authentication key pair in two separate files. One of the keys is your private key which must never be made available to anyone but yourself. The private key can only be used together with the passphrase. In the example above, the private key file is id_dsa_2048_a. The other file id_dsa_2048_a.pub is your public key, which can be distributed to other computers. Note: Beginning with version 3.0, SSH Secure Shell includes support for RSA keys. They can be generated by specifying the -t flag with ssh-keygen2.
Local> ssh-keygen2 -t rsa
Generating 2048-bit rsa key pair
2 oOo.ooOo.oOo
Key generated.
2048-bit rsa, user@Local, Wed May 02 2002 14:15:41 +0300
Passphrase :
Again :
Private key saved to /home/user/.ssh2/id_rsa_2048_a
Public key saved to /home/user/.ssh2/id_rsa_2048_a.pub
Create an identification file in your ~/.ssh2 directory on Local.
Local> cd ~/.ssh2
Local> echo "IdKey id_dsa_2048_a" > identification
You now have an identification file which consists of one line that denotes the file containing your identification (your private key). For special applications, you can create multiple identifications by executing ssh-keygen2 again. This is, however, not usually needed.
Copy your public key (id_dsa_2048_a.pub) to your ~/.ssh2 directory on Remote.
Create an authorization file in your ~/.ssh2 directory on Remote. Add the following line to the authorization file:
Key id_dsa_2048_a.pub
This directs the SSH Secure Shell server to use id_dsa_2048_a.pub as a valid public key when authorizing your login. If you want to login to Remote from other hosts, create a key pair on the hosts (steps 1 and 2) and repeat steps 3, 4, and 5 on Remote. (Remember to specify a different file name for each key pair.)
Now you should be able to login to Remote from Local using SSH Secure Shell. Try to login:
Local>ssh Remote
Passphrase for key "/home/user/.ssh2/id_dsa_1024_a
with comment "2048-bit dsa, created by user@Local
Wed Mar 22 2002 00:13:43 +0200":
After you have entered the passphrase of your private key, a Secure Shell connection will be established.
Who knows what's wrong it?
Thanks a lot!