Please please please, find something in your native language about the basics of ssh and asymmetric keys and encryption. If your ssh client is setup correctly then your key set IS the authentication mechanism and the server does NOT ask for a password. However as mentioned before if you set a pass-phrase on your key set when you generated it then you will need to provide that; but the request is local, it is not coming from the server and I have no control over it.
Let me give some examples:
If I try to connect to a system or account where I have not installed a public key I get a request like:
$ ssh joe@squeak.org Password:
This is a request for a password that has been set on the server. But:
$ ssh kencausey@squeak.org Enter passphrase for key '/home/ken/.ssh/id_dsa':
This is the way it should look and this is a request for the pass-phrase you supplied when you created the key set.
If you see the first then you have not installed your private key correctly or are trying to access the wrong account. If instead you are seeing the second then if it is not working then you are supplying the wrong pass-phrase and I can't do anything about that.
Ken
On Mon, 2009-05-04 at 16:45 -0300, Edgar J. De Cleene wrote:
On 5/4/09 11:46 AM, "Ken Causey" ken@kencausey.com wrote:
When you created the ssh keys it asked you for a pass-phrase to associate with the private key. Whenever you then attempt to use the key, as you are now, it requires that you specify the pass-phrase. This restricts access to the private key to only those that know the proper pass-phrase.
Are you specifying the pass-phrase that you used when you created the keys?
Ken
Yes. It's the same as the password I using, but when the server ask for the password , fails to verify. No idea what is happening.
Edgar
box-admins@lists.squeakfoundation.org