scp error.

bruse · 08-31-2005, 06:38 AM

mandrake 10.0

i have error during copy the file.

[staff@ws061 staff]$ scp wine-20041019-mdk.i586.rpm 10.255.240.102://home/staff/
No RSA host key is known for 10.255.240.102 and you have requested strict checking.
Host key verification failed.
lost connection
[staff@ws061 staff]$

what this error means?
how to overcome this?
thanks.

druuna · 08-31-2005, 07:16 AM

Hi,

The RSA host key cannot be found (first connect to this host? was that host newly reconfigured?).

Due to the strict checking you enabled (or someone else did) ssh (scp) will not trust this host.

There's a lot of info on the net about this........

First goolge hit: http://www.securityfocus.com/infocus/1806

Hope this helps.

bruse · 08-31-2005, 07:37 AM

good luck.

i have transfered that file using fish:// in konqueror.

IT IS TIME TO KNOW THAT WHAT WHAT IS THE PROTOCOL USED BY FISH PROGRAM FOR A BETTER AND FASTER TRANSFER.

earlier i thought fish using scp to transfer the file.
now it is proved that it is using some other?

pls tell me what is the way fish using?

druuna · 08-31-2005, 08:01 AM

Hi,

Never used (or even heard of) fish. Cannot help you there.

BUT: Using google (your homepage, rigth

) you can find info (that fish is using ssh to name just one).

bruse · 08-31-2005, 08:31 AM

very good .

thanks.

koodoo · 08-31-2005, 04:01 PM

Quote:

Originally posted by bruse

[staff@ws061 staff]$ scp wine-20041019-mdk.i586.rpm 10.255.240.102://home/staff/
[staff@ws061 staff]$

Hey! Just noticed one thing, I always did scp with a single '/'.
I mean instead of using 10.255.240.102://home/staff/ I use 10.255.240.102:/home/staff/
Is there any difference or was the earlier one a typo.

Thanks.

Rinish · 09-01-2005, 02:12 AM

If Iam not wrong, Fish uses port 22 (ssh/scp) but they does'nt check any Authentication keys such as RSA and DSA by default.

/ Rinish (rinishriju)

koodoo · 09-02-2005, 01:23 PM

Quote:

Originally posted by Rinish
If Iam not wrong, Fish uses port 22 (ssh/scp) but they does'nt check any Authentication keys such as RSA and DSA by default.

/ Rinish (rinishriju)

This is what I get when I try to access some unknown host (say 10.10.11.32) via FISH :

Code:

The authenticity of host '10.10.11.32 (10.10.11.32)' can't be established.
RSA key fingerprint is 36:db:e9:17:73:dd:79:8c:8f:f5:bf:90:5c:2a:9b:35.
Are you sure you want to continue connecting (yes/no)? 

                                 Yes                      No

and this is the default behaviour on my system.

svenwinkle · 09-02-2005, 02:17 PM

Hey, here's how you fix your problem. ssh grabs information from the computer that you are connecting to and stores it in a file. If the computer you are connecting to ever reboots or reconfigures its keys, the stored key you have on your computer will no longer work. When this happens, the easiest way (I have found) to resolve the issue is to go into that file where the key information about the other computer is stored and erase that computer's entry. You can then re-connect and get new key information that your computer will accept.

The file is called known_hosts. It is stored in your user's home directory inside a folder called .ssh. You won't see this folder during a normal directory listing (ls), but if you use ls -a you will see it. So the full path is then /home/<username>/.ssh/known_hosts

Use your editor of choice (mine is vi) to access that file. You will see an entry for every computer you have ever used ssh to access. For each computer there will be an entry similar to the following:

192.168.50.188 ssh-rsa AAAAB3NzaC1yc2EAAAABIwBBBIEA4j3rP1kgqZNKmk198dp9ZatqAV7KnPmI
7ZfDSWYrmYx6HpS316wrx+jpUHBjyWe7eCMLiNm2jaU8MEoJBWZNsYj8HX3z+v7ataE8zvZ7EUmnNY3F
Fhvb1DWdeIUqa4kSKE5RuADAaAa/eVyOs7wf+MGYrdZW4ZX1kk1i9I46x/k=

This is all one entry. You can identify the entry belonging to the computer in question by the IP address. Delete that entire line(in vi you just move the cursor to the line and type dd). Save the file and exit (in vi the command for that is :wq!) .

When you are finished with that, you can connect into the remote computer again with ssh. You will have to type 'yes' again when it asks if you want to accept the host key. At that point it should be working properly.

Good luck!

koodoo · 09-02-2005, 03:44 PM

Quote:

Originally posted by svenwinkle
Hey, here's how you fix your problem. ssh grabs information from the computer that you are connecting to and stores it in a file. If the computer you are connecting to ever reboots or reconfigures its keys, the stored key you have on your computer will no longer work. When this happens, the easiest way (I have found) to resolve the issue is to go into that file where the key information about the other computer is stored and erase that computer's entry. You can then re-connect and get new key information that your computer will accept.

The file is called known_hosts. It is stored in your user's home directory inside a folder called .ssh. You won't see this folder during a normal directory listing (ls), but if you use ls -a you will see it. So the full path is then /home/<username>/.ssh/known_hosts

Use your editor of choice (mine is vi) to access that file. You will see an entry for every computer you have ever used ssh to access. For each computer there will be an entry similar to the following:

192.168.50.188 ssh-rsa AAAAB3NzaC1yc2EAAAABIwBBBIEA4j3rP1kgqZNKmk198dp9ZatqAV7KnPmI
7ZfDSWYrmYx6HpS316wrx+jpUHBjyWe7eCMLiNm2jaU8MEoJBWZNsYj8HX3z+v7ataE8zvZ7EUmnNY3F
Fhvb1DWdeIUqa4kSKE5RuADAaAa/eVyOs7wf+MGYrdZW4ZX1kk1i9I46x/k=

This is all one entry. You can identify the entry belonging to the computer in question by the IP address. Delete that entire line(in vi you just move the cursor to the line and type dd). Save the file and exit (in vi the command for that is :wq!) .

When you are finished with that, you can connect into the remote computer again with ssh. You will have to type 'yes' again when it asks if you want to accept the host key. At that point it should be working properly.

Good luck!

Correct me if I am wrong.

I also have experienced the problem you have mentioned i.e. if the host computer changes it's keys (not reboots) you get such an error and the best solution is to delete the entry corresponding to that particular I.P. from the ~/.ssh/known_hosts file.
But in that case the error you get is somewhat like this (I do not remember the exact error, though) : Remote key for concerned host has been changed. Host key verification failed. This might mean that somebody is spying on you, if this is not the case, edit the file ~/.ssh/known_hosts.

But in case of Bruse, he is getting the error : No RSA host key is known for 10.255.240.102 and you have requested strict checking.
Host key verification failed.
lost connection

This indicates that the RSA key does not exist (not changed), and since the user has requested strict checking Host key verification has failed.

I may be wrong though as I do not remember exactly what error you get in case of changed RSA keys.
My Apologies if that is the case

Hope this helps.