public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: William Cohen <wcohen@redhat.com>
Cc: overseers@sources.redhat.com
Subject: Re: Problems with read/write cvs access
Date: Tue, 22 Mar 2005 14:19:00 -0000	[thread overview]
Message-ID: <20050316180256.GD30517@redhat.com> (raw)
In-Reply-To: <4238734E.4060701@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 804 bytes --]

wcohen wrote:

> I am not sure whether I should be able to ssh into sources.redhat.com. 

Of course you can - that's how cvs-over-ssh works.  Most accounts are
restricted as to what programs they can run, once they log in.  But
the initial negotiation is the same anyway.

> However, here is what I got:
> $ ssh -v wcohen@sources.redhat.com
> OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003
> [...]
> debug1: Remote protocol version 1.99, remote software version 
> OpenSSH_3.6.1p2
> debug1: match: OpenSSH_3.6.1p2 pat OpenSSH*
> [...]

The "welcome to sourceware" message you received ought to have 
included instructions to use ssh protocol 1 if you supply only
an old-style RSA key.  Put the appropriate clause into your
.ssh/config to force "Protocol 1", and it should work.

- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-03-16 18:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-20 19:11 William Cohen
2005-03-20 23:19 ` Ian Lance Taylor
2005-03-21 17:40   ` William Cohen
2005-03-22  7:55     ` Ian Lance Taylor
2005-03-22 12:56       ` Frank Ch. Eigler
2005-03-22 13:08       ` William Cohen
2005-03-22 13:29         ` Ian Lance Taylor
2005-03-22 14:19         ` Frank Ch. Eigler [this message]
2005-03-22 17:04           ` William Cohen

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=20050316180256.GD30517@redhat.com \
    --to=fche@redhat.com \
    --cc=overseers@sources.redhat.com \
    --cc=wcohen@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).