From: Martin Sebor <msebor@gmail.com>
To: "Frank Ch. Eigler" <fche@elastic.org>, Eli Zaretskii <eliz@gnu.org>
Cc: overseers@sourceware.org
Subject: Re: Git over SSH access problem
Date: Fri, 19 Jul 2019 14:23:00 -0000 [thread overview]
Message-ID: <72be3184-4fde-3460-bc7f-d75d38ba4de4@gmail.com> (raw)
In-Reply-To: <20190718142633.GI3519528@elastic.org>
On 7/18/19 8:26 AM, Frank Ch. Eigler wrote:
> Hi -
>
>> I have a v2 key pair already. I attach its .pub part below. Is this
>> key okay?
>
> No, it looks like an EC type key, which is not supported by rhel6 ssh
> on sourceware, not an RSA one.
I asked this once before but I don't think I heard back: could
the sourceware account information page be updated with the details
of what kinds of SSH keys are supported? I also had trouble with
my account sometime ago and it was only by trial and error that
I was able to figure out I was using the wrong kind of key.
Thanks
Martin
>
>> If yes, do I need to do anything else, besides configuring on my
>> side to use this key for sourceware?
>
> That part is automatic. Your ssh client will try all the keys it
> knows about.
>
> - FChE
>
prev parent reply other threads:[~2019-07-19 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 12:18 Eli Zaretskii
2019-07-18 13:05 ` Frank Ch. Eigler
2019-07-18 14:08 ` Eli Zaretskii
2019-07-18 14:26 ` Frank Ch. Eigler
2019-07-18 14:40 ` Eli Zaretskii
2019-07-18 14:43 ` Frank Ch. Eigler
2019-07-18 14:46 ` Eli Zaretskii
2019-07-18 14:53 ` Frank Ch. Eigler
2019-07-18 14:57 ` Eli Zaretskii
2019-07-19 14:23 ` Martin Sebor [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=72be3184-4fde-3460-bc7f-d75d38ba4de4@gmail.com \
--to=msebor@gmail.com \
--cc=eliz@gnu.org \
--cc=fche@elastic.org \
--cc=overseers@sourceware.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).