Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Andrew Cagney" <ac131313@redhat.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: ssh CVS access from another machine
Date: Tue, 25 Feb 2003 20:27:00 -0000	[thread overview]
Message-ID: <005801c2dd0c$d5b06b10$2a00a8c0@dash> (raw)
In-Reply-To: <3E5BCF66.6050005@redhat.com>

Here's the output....doesn't look like anything is wrong....  Strange.  Oh
well, I guess I'll wait until I'm back in tomorrow.

cheers,

Kris

$ ssh -v sources.redhat.com
OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090607f
debug1: Reading configuration data /home/kewarken/.ssh/config
debug1: Applying options for sources.redhat.com
debug1: Rhosts Authentication disabled, originating port will not be
trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to sources.redhat.com [66.187.233.205] port 22.
debug1: Connection established.
debug1: identity file /home/kewarken/.ssh/identity type -1
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.1p1
debug1: match: OpenSSH_3.1p1 pat OpenSSH_2.*,OpenSSH_3.0*,OpenSSH_3.1*
debug1: Local version string SSH-1.5-OpenSSH_3.4p1
debug1: Waiting for server public key.
debug1: Received server public key (768 bits) and host key (1024 bits).
debug1: Host 'sources.redhat.com' is known and matches the RSA1 host key.
debug1: Found key in /home/kewarken/.ssh/known_hosts:2
debug1: Encryption type: 3des
debug1: Sent encrypted session key.
debug1: cipher_init: set keylen (16 -> 32)
debug1: cipher_init: set keylen (16 -> 32)
debug1: Installing crc compensation attack detector.
debug1: Received encrypted confirmation.
debug1: Doing challenge response authentication.
debug1: No challenge.
Permission denied.
debug1: Calling cleanup 0x419440(0x0)

----- Original Message -----
From: "Andrew Cagney" <ac131313@redhat.com>
To: "Kris Warkentin" <kewarken@qnx.com>
Cc: <gdb@sources.redhat.com>
Sent: Tuesday, February 25, 2003 3:17 PM
Subject: Re: ssh CVS access from another machine


> It's the .ssh/identity file that is the `key'.  Try `ssh -v ...' and
> very carefully read the output.  The protection of that key may be wrong
> for instance.
>
> Andrew
>
>


  reply	other threads:[~2003-02-25 20:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25 20:06 Kris Warkentin
2003-02-25 20:13 ` Daniel Jacobowitz
2003-02-25 20:15 ` Andrew Cagney
2003-02-25 20:27   ` Kris Warkentin [this message]
2003-02-25 20:27   ` Kris Warkentin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='005801c2dd0c$d5b06b10$2a00a8c0@dash' \
    --to=kewarken@qnx.com \
    --cc=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox