Re: Basic setup help

From: Dimitri Maziuk (dima@127.0.0.1)
Date: 04/16/02


From: Dimitri Maziuk <dima@127.0.0.1>
Date: Mon, 15 Apr 2002 23:24:03 +0000 (UTC)

begin 666 <ahall@no-spam-to-world.std.com>:
>
> I compiled ssh on Solaris and tried to
> connect to my ISP.
>
> I created an rsa key, and copied the public
> key to my ~/.ssh/id_rsa.pub (just a guess).
>
> Then I entered the following command on the
> machine I compiled and created the keys on and
> got the following results:
>
> ahall <9> ssh -l ahall -X -i ~/.ssh/id_rsa -2 -v -v -v shell.theworld.com
> OpenSSH_3.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090603f
> debug1: Reading configuration data /home/ahall/ssh/etc/ssh_config
> debug3: Seeing PRNG from /home/ahall/ssh/libexec/ssh-rand-helper
> debug1: Rhosts Authentication disabled, originating port will not be trusted.
> debug1: restore_uid
> debug1: ssh_connect: getuid 4084 geteuid 4084 anon 1
> debug1: Connecting to shell.theworld.com [199.172.62.252] port 22.
> debug1: temporarily_use_uid: 4084/30 (e=4084)
> debug1: restore_uid
> debug1: temporarily_use_uid: 4084/30 (e=4084)
> ssh: connect to address 199.172.62.252 port 22: Connection timed out
> debug1: restore_uid
> ahall <10>
>
>
> Where should I be creating the keys, and where should I
> be putting the public key.

"Connection timed out" means "there's a firewall between you and
shell.theworld.com, and it's configured to drop all packets to port
22 on the floor", most likely. Nothing to do with the keys.

Is it your firewall, or your ISP's?

Dima ("no server listening" or "firewall rejects connections" result
in "connection refused", BTW)

-- 
We're sysadmins. Sanity happens to other people.                  -- Chris King



Relevant Pages

  • public key problems
    ... I have two accounts on the destination machine (Solaris 7, ... ssh-agent keys and prompts me for a password. ... < debug1: bits set: 1587/3191 ... < debug2: userauth_pubkey_agent: no message sent ...
    (comp.security.ssh)
  • Re: x.509 & key_verify() error
    ... server use rsa+cert as hostkey; ... client and server config contain X509rsaSigType=sha1 option; ... >and matching of keys can get kind of complicated... ... >debug1: Server will not fork when running in debugging ...
    (SSH)
  • Re: Basic setup help
    ... >> I compiled ssh on Solaris and tried to ... debug1> Rhosts Authentication disabled, originating port will not be trusted. ... >> Where should I be creating the keys, ...
    (comp.security.ssh)
  • rsa authentication working in RH 7.2 but not RH 9.0
    ... I could ssh to my Linux box running RH 7.2 with rsa keys and no ... password authentication. ... debug1: Rhosts Authentication disabled, ... # Kerberos TGT Passing only works with the AFS kaserver ...
    (comp.security.ssh)
  • Re: scp only in one way
    ... >> make it work with the keys... ... > The same as in the posting, I'm still asked for the password. ... > debug1: Rhosts Authentication disabled, ... Remote protocol version 1.99, ...
    (comp.security.ssh)