From: Ian Lance Taylor <ian@airs.com>
To: Andy Wingo <wingo@igalia.com>
Cc: overseers@sourceware.org
Subject: Re: Request from Andy Wingo
Date: Wed, 11 Mar 2015 12:30:00 -0000 [thread overview]
Message-ID: <m3oanz90nz.fsf@pepe.airs.com> (raw)
In-Reply-To: <877funn725.fsf@igalia.com> (Andy Wingo's message of "Wed, 11 Mar 2015 11:48:34 +0100")
Andy Wingo <wingo@igalia.com> writes:
> I received the sourceware.org account creation mail but it seems
> something went wrong with the SSH key setup:
>
> $ ssh -vv sourceware.org
> [...]
> debug1: Offering RSA public key: /home/wingo/.ssh/id_rsa
> debug2: we sent a publickey packet, wait for reply
> debug1: Authentications that can continue: publickey
> debug1: Offering RSA public key: wingo@rusty
> debug2: we sent a publickey packet, wait for reply
> debug1: Authentications that can continue: publickey
> debug2: we did not send a packet, disable method
> debug1: No more authentication methods to try.
> Permission denied (publickey).
>
> My local username is "wingo", which AFAIK is the same as the
> sourceware.org name, so that shouldn't be the issue. Could it be that I
> mangled the SSH pubkey? I am attaching my public key again.
The SSH public key is correct.
Note that you do not have full SSH access. Try sending a command, as in
ssh sourceware.org alive
If that doesn't help, send us the full "ssh -vv" output. In the
fragment you sent it looks like sourceware is not responding at all.
Ian
prev parent reply other threads:[~2015-03-11 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 7:35 wingo
2015-03-09 15:08 ` Christopher Faylor
2015-03-09 18:27 ` Andy Wingo
2015-03-09 18:40 ` Christopher Faylor
2015-03-11 10:48 ` Andy Wingo
2015-03-11 12:26 ` Andy Wingo
2015-03-11 12:32 ` Ian Lance Taylor
2015-03-11 12:44 ` Andy Wingo
2015-03-11 12:30 ` 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=m3oanz90nz.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=overseers@sourceware.org \
--cc=wingo@igalia.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).