From: Ian Lance Taylor <ian@airs.com>
To: bud davis <bdavis9659@comcast.net>
Cc: overseers@gcc.gnu.org
Subject: Re: gcc cvs access via ssh
Date: Mon, 25 Apr 2005 01:26:00 -0000 [thread overview]
Message-ID: <m34qdvabpm.fsf@gossamer.airs.com> (raw)
In-Reply-To: <1114389564.15719.2.camel@localhost.localdomain>
bud davis <bdavis9659@comcast.net> writes:
> after a new OS install i can't access cvs for gcc.
>
> here is the error messages:
>
> [bdavis@localhost ~/gfc]$ cvs -z9 co gccc
> The authenticity of host 'gcc.gnu.org (12.107.209.250)' can't be
> established.
> RSA key fingerprint is 1d:1e:46:7f:4d:73:8d:10:20:c3:4c:5a:34:14:44:23.
> Are you sure you want to continue connecting (yes/no)? cvs [checkout
> aborted]: received interrupt signal
> [bdavis@localhost ~/gfc]$ cvs -z9 co gcc
> The authenticity of host 'gcc.gnu.org (12.107.209.250)' can't be
> established.
> RSA key fingerprint is 1d:1e:46:7f:4d:73:8d:10:20:c3:4c:5a:34:14:44:23.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'gcc.gnu.org,12.107.209.250' (RSA) to the
> list of known hosts.
> Permission denied (publickey,keyboard-interactive).
> cvs [checkout aborted]: end of file from server (consult above messages
> if any)
> [bdavis@localhost ~/gfc]$ echo CVSROOT
> CVSROOT
> [bdavis@localhost ~/gfc]$ echo $CVSROOT
> :ext:bdavis@gcc.gnu.org:/cvsroot/gcc
I note that your .ssh/known_hosts file changed. Do you still have
your private SSH keys?
I note that your authorized SSH key on gcc.gnu.org is a v1 RSA key.
You may need to put something like this in your .ssh/config file:
host gcc.gnu.org
protocol 1
Ian
prev parent reply other threads:[~2005-04-25 1:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 0:39 bud davis
2005-04-25 1:26 ` Ian Lance Taylor [this message]
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=m34qdvabpm.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=bdavis9659@comcast.net \
--cc=overseers@gcc.gnu.org \
/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).