From: Eli Zaretskii <eliz@gnu.org>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: overseers@sourceware.org
Subject: Re: Git over SSH access problem
Date: Thu, 18 Jul 2019 14:40:00 -0000 [thread overview]
Message-ID: <83ftn3wgmz.fsf@gnu.org> (raw)
In-Reply-To: <20190718142633.GI3519528@elastic.org> (fche@elastic.org)
> Date: Thu, 18 Jul 2019 10:26:33 -0400
> From: "Frank Ch. Eigler" <fche@elastic.org>
> Cc: overseers@sourceware.org
>
> > 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.
What about the one below?
> > 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.
Thanks.
---- BEGIN SSH2 PUBLIC KEY ----
Comment: "rsa-key-20190718"
AAAAB3NzaC1yc2EAAAABJQAAAgBqqWa7E3D4DpCewcoYm659RG95GEEhwkVRNRps
jVXXtG3xKkcp0fl2IZngf4q01skSkVVYdexgxyENwaEitcQUH/A/6p7MLFDt7sQi
UATabMB5J3VhLuNDLqL6SScRBXV0cx0uORw42bo1U5V/4nYTrFHZ984MBahbL3+g
3lIUfVVN4iaaYaDOmB5zKfLiuvZngHhXZ0tVR5h0djtbkTfvd6la3LdkEC0qfJnv
LXq9hw22rM24Hzes++HuV63mJV/ecpUfKuAw3xHr+/CuINCPWnpJ/+XVt0mWwOGL
wRtWAvmy4cMSU9vuapfXYGfQqE2Ca114R2qac8QkY+D4CXDbXV9HR+QekJPBulBK
XMW6hYossuMZTRja7T6D65Xi65xcK52Vap9sUcANosCZRVM0YqhGFVhVIW4/PUh1
GEdRI0EuFFuHSuoT/J16bBSKdSeQaVFSWIoojqGBmR5XjDdfb+uK4WIqUanukFM2
MMPPwP7csgHGpiezcBOb0oJ8YdxiaYt6MhuWEI8Poq1ujy36SS5IAQvGXt/AloJE
4ZIdktFaJ3Cu0I4UuIJETDHUZJK4de7Imhif2jT7Ya5f025Vsro4ehmEdb3g/q0N
ryCaB0cnSH/IF3hDSsMlJxPsXYP4ZLHPwg/rFcgi2S9asBvAt2NI2HqpoSm2FxK0
3hXykQ==
---- END SSH2 PUBLIC KEY ----
next prev parent reply other threads:[~2019-07-18 14:40 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 [this message]
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
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=83ftn3wgmz.fsf@gnu.org \
--to=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).