From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Rical Jasan <ricaljasan@pacific.net>,
Joseph Myers <joseph@codesourcery.com>,
overseers@sourceware.org
Subject: Re: SSH Authentication Failures
Date: Mon, 19 Dec 2016 04:48:00 -0000 [thread overview]
Message-ID: <20161219044838.GA6820@ednor.casa.cgf.cx> (raw)
In-Reply-To: <b060710e-60ad-b4bc-d18f-45e2abfda6b7@pacific.net>
On Sun, Dec 18, 2016 at 07:40:32PM -0800, Rical Jasan wrote:
>Hi,
>
>Sorry it's taken so long to get to this, but I'm having trouble logging
>in to my new account, rj@sourceware.org.
>
>$ /bin/date; ssh sourceware.org
>Sun Dec 18 19:33:26 PST 2016
>Permission denied (publickey).
>
>Not that I expect to have a shell, just showing the problem. Debug
>output doesn't show anything more helpful than that result. Could you
>take a look at the log and see why it's failing?
You can't login to sourceware. You only have git/subversion access.
ssh sourceware.org alive
should tell you if you have access. If you don't you undoubtedly didn't
enter the right ssh key.
next prev parent reply other threads:[~2016-12-19 4:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 3:40 Rical Jasan
2016-12-19 4:48 ` Christopher Faylor [this message]
2016-12-19 5:02 ` Rical Jasan
2016-12-19 6:29 ` Christopher Faylor
2016-12-19 12:13 ` Frank Ch. Eigler
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=20161219044838.GA6820@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=overseers@sourceware.org \
--cc=ricaljasan@pacific.net \
/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).