Re: how to connect desktop and netbook through router?
OK, I'm confused. I've been thinking for some minutes, and I just don't quite understand.
1. Which "hosts.allow" file do I modify? Server or client? I'm sure it's obvious to you, but not at all to me.
2. You speak of restarting the network. WHAT network? I can restart the SSH server - THAT I know how to do, but without a link to or from the client, how can there be a network? So, I assume you mean that I needs to restart the SSH server. That implies that the answer to #1 is "server". And, my understanding would be that the "ssh" command, on the client machine, is what makes that connection.
So, I'll try that. If you intercept this and see need to correct me, please do.
-----
Update: Here's what happened. I added the line you suggest to the "hosts.allow" of my desktop server. I restarted the server. I tried to access it from my laptop with "ssh -v tomc@tomc-desktop" - this looks promising initially, but then fails:
I've seen this message before, so I don't think modifying hosts.allow mattered. I don't understand why I'm getting this authentication business - given the changes I made to my
file (as previously detailed):
I'm just try to access my desktop from my laptop, all from behind a router. Can't I just do this with any password nonsense at all? I can certainly go study "authentication", but...this just seems to go on forever. I'll do it when I can find the time, I guess.
For now...why am I being caught up in this nonsense when I specifically requested NOT to in my config file (on the server)? I have no theory about that. Any ideas?
Originally posted by toad
Well, for my ssh to work I've got to add the following line:
Best restart both the network and the ssh demon afterwards 
Code:
sshd: ALL
1. Which "hosts.allow" file do I modify? Server or client? I'm sure it's obvious to you, but not at all to me.
2. You speak of restarting the network. WHAT network? I can restart the SSH server - THAT I know how to do, but without a link to or from the client, how can there be a network? So, I assume you mean that I needs to restart the SSH server. That implies that the answer to #1 is "server". And, my understanding would be that the "ssh" command, on the client machine, is what makes that connection.
So, I'll try that. If you intercept this and see need to correct me, please do.
-----
Update: Here's what happened. I added the line you suggest to the "hosts.allow" of my desktop server. I restarted the server. I tried to access it from my laptop with "ssh -v tomc@tomc-desktop" - this looks promising initially, but then fails:
Code:
$ ssh -v tomc@tomc-desktop OpenSSH_5.1p1 Debian-6ubuntu2, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to tomc-desktop [192.168.1.2] port 22. debug1: Connection established. debug1: identity file /home/tomc/.ssh/identity type -1 debug1: identity file /home/tomc/.ssh/id_rsa type -1 debug1: identity file /home/tomc/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-6ubuntu2 debug1: match: OpenSSH_5.1p1 Debian-6ubuntu2 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-6ubuntu2 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'tomc-desktop' is known and matches the RSA host key. debug1: Found key in /home/tomc/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/tomc/.ssh/identity debug1: Trying private key: /home/tomc/.ssh/id_rsa debug1: Trying private key: /home/tomc/.ssh/id_dsa debug1: No more authentication methods to try. Permission denied (publickey).
Code:
ssh_config
Code:
RSAAuthentication no PubkeyAuthentication no . . . PasswordAuthentication no . . . AllowUsers tomc@tomc-laptop
For now...why am I being caught up in this nonsense when I specifically requested NOT to in my config file (on the server)? I have no theory about that. Any ideas?
Comment