Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
mahmood@server:~$ ssh client
get_socket_address: getnameinfo 8 failed: Name or service not known
get_socket_address: getnameinfo 8 failed: Name or service not known
cannot get sockname for fd
ssh_keysign: no reply
key_sign failed
mahmood@client's password:
Linux harrier 2.6.32-24-server #39-Ubuntu SMP Wed Jul 28 06:21:40 UTC 2010 x86_64 GNU/Linux
Ubuntu 10.04 LTS
Welcome to the Ubuntu Server!
* Documentation: http://www.ubuntu.com/server/doc
Last login: Sun Mar 27 08:16:06 2011 from server
mahmood@client:~$
Something is still off. I just reviewed your posts and in none of the configs you posted there is a key mentioned as is in the manual.
That's why you get:
Quote:
ssh_keysign: no reply
key_sign failed
this error I imagine. Check with sss-keyscan what the key is for the remote machine and add it to your config file. Then restart SSH and try again.
Nothing happened.
On the serve side, I ran "ssh-keysign client" and added that to /etc/ssh/ssh_known_hosts. After running "/etc/init.d/ssh restart", I still get the same prompt and message.
No, not ssh-keysign, but ssh-keyscan host. From the man page of ssh-keyscan:
Quote:
ssh-keyscan is a utility for gathering the public ssh host keys of a number of
hosts. It was designed to aid in building and verifying ssh_known_hosts files.
ssh-keyscan provides a minimal interface suitable for use by shell and perl
scripts
That should get you the key you need to put in the configuration file in order to connect.
for each client machine from which you want to allow password-less logins.
Check for more differences between Reuti's manual and this one. I didn't find the way to get the key in Reuti's manual so looked at Google for help and that site came up. Seems pretty straightforward to me.
restarting the ssh service on server and rebooting the client....
still get the same messages:
Code:
mahmood@server:~$ ssh client
get_socket_address: getnameinfo 8 failed: Name or service not known
get_socket_address: getnameinfo 8 failed: Name or service not known
cannot get sockname for fd
ssh_keysign: no reply
key_sign failed
mahmood@client's password:
Have you checked point 4 on the site I pointed to?
Quote:
Make the account of each permitted user accept password-less logins, on the server. For this, you typically will not need administrator access. For our Linux example, log in as the user who will be logging in without a password, and then add this line to the ~/.shosts file:
after restarting the service and rebooting the client:
Code:
mahmood@server:~$ ssh client
get_socket_address: getnameinfo 8 failed: Name or service not known
get_socket_address: getnameinfo 8 failed: Name or service not known
cannot get sockname for fd
ssh_keysign: no reply
key_sign failed
mahmood@client's password:
No problem at all, I'm glad to help but this is really confusing me. At first I thought you were suffering from a bug that exists in an older version, that's why I asked for your version of SSH. But that seems to be out of the question. One last thing comes to mind. Did you add for both computers 'IP computername' to the /etc/hosts file?
The way I understand it you've set up everything to allow connection FROM client TO server yet you are connecting to the client???? Try connecting from the client to the server.
mahmood@server:~$ ssh client
get_socket_address: getnameinfo 8 failed: Name or service not known
get_socket_address: getnameinfo 8 failed: Name or service not known
cannot get sockname for fd
ssh_keysign: no reply
key_sign failed
mahmood@client's password:
Linux client 2.6.32-24-server #39-Ubuntu SMP Wed Jul 28 06:21:40 UTC 2010 x86_64 GNU/ Linux
Ubuntu 10.04 LTS
Welcome to the Ubuntu Server!
* Documentation: http://www.ubuntu.com/server/doc
Last login: Sun Mar 27 09:40:19 2011 from server
mahmood@client:~$
So I am in the client. Now:
Code:
mahmood@client:~$ ssh server
buffer_get_ret: trying to get more bytes 257 than in buffer 251
buffer_get_string_ret: buffer_get failed
buffer_get_bignum2_ret: invalid bignum
key_from_blob: can't read rsa key
key_read: key_from_blob AAAAB3NzaC1yc2EAAAABIwAAAQEAuBCfN+TMtNok1WezSr7aj7LqFm01NAlITG gLBRN4juw1yfj+lbqkPaWQZg9bHUyH5iBge7HqjM0eFf0a8KRxL0yYB3nfcWJebWJ+XuEBIRPTAoZkJdsi26om Y8fStN8fzqXsgVNCnrY8k16zTXMltcN+MNPG7x9nutZQu9uvNIteshthRLJyD34KzOIqf4anW1A2MRfGkQUJEc 9Kwg/FYRSS2Y6irAaQq3dgO7hlwnesdXNJZRPeI1JmaxT20NVgWbZn4gbozuxrj21gFXKLJTioTy1FtKleY9mj PlCRBZJGw1MKfKtvhmSfyno8fvPV35iB0m+LMRYI/Q==
failed
buffer_get_ret: trying to get more bytes 257 than in buffer 251
buffer_get_string_ret: buffer_get failed
buffer_get_bignum2_ret: invalid bignum
key_from_blob: can't read rsa key
key_read: key_from_blob AAAAB3NzaC1yc2EAAAABIwAAAQEAuBCfN+TMtNok1WezSr7aj7LqFm01NAlITG gLBRN4juw1yfj+lbqkPaWQZg9bHUyH5iBge7HqjM0eFf0a8KRxL0yYB3nfcWJebWJ+XuEBIRPTAoZkJdsi26om Y8fStN8fzqXsgVNCnrY8k16zTXMltcN+MNPG7x9nutZQu9uvNIteshthRLJyD34KzOIqf4anW1A2MRfGkQUJEc 9Kwg/FYRSS2Y6irAaQq3dgO7hlwnesdXNJZRPeI1JmaxT20NVgWbZn4gbozuxrj21gFXKLJTioTy1FtKleY9mj PlCRBZJGw1MKfKtvhmSfyno8fvPV35iB0m+LMRYI/Q==
failed
The authenticity of host 'server (192.168.1.1)' can't be established.
RSA key fingerprint is 98:16:bc:1c:f9:a7:a8:76:37:20:13:97:24:b1:58:8b.
Are you sure you want to continue connecting (yes/no)?
Interesting. The message of server->client is different from client->server.
And after you accepted the authenticity when connecting from client to server? What happened then? Did you get connected? Also check the permissions on the file you created, this looks like a permission issue.
Of course output from server to client is different then from client to server because you only have set up your server to accept host based authentication. If you want to work it both ways you'll have to repeat the necessary steps on the client machine for the SSH server part (sshd_config) and on the server machine for the client part (ssh_config). If I'm not mistaking you've only set it up one way, from your client to your server.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.