From: Olivier Hainque <hainque@adacore.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: Olivier Hainque <hainque@adacore.com>,
Overseers mailing list <overseers@sourceware.org>
Subject: Re: sourceware.org ssh key update
Date: Thu, 24 Sep 2020 17:14:43 +0200 [thread overview]
Message-ID: <51E7295E-58E8-4DAB-81BA-B49FEDCCD93D@adacore.com> (raw)
In-Reply-To: <20200924144042.GD76609@elastic.org>
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
Hello Franck,
> On 24 Sep 2020, at 16:40, Frank Ch. Eigler <fche@elastic.org> wrote:
>
> Hi -
>
>> Could you please install a new one for me?
>> What would be the correct way to transmit it to you?
>
> Please send us an rsa4096 or similar rhel8-friendly ssh pubkey.
Attached. Thanks for your super fast answer.
Olivier
[-- Attachment #2: id_rsa.pub --]
[-- Type: application/octet-stream, Size: 761 bytes --]
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQD19stbngWOoS4O1zpVTK2rpfpzUqplAr8A5hbFwtgnYhPlZpzmDKIpfA7NNHVeCjvkTZGurwiBGI/Jx9qDRbMTKHNHFoOPyTHtyBp1frC4dYVoYta1/RQ10H1ywfuceJiza66m+NEpSWyT1Vev2wPL1MxdWx9I4skrRZcoVs7PQIRL/8vEP8ZS4Fr1ayMgzBySn9iAiXDabwAsKYq1V6T3lcxB1r0aUCuKGAHg/nlmwkMhSo+g/8p5pPWSoMsPr6qPQBj+n26GvgSEyLaggKzVMJUo58xGAwIwTMRITu/nd3mR1lM6sn5ITEO3nRXWg0OOsAau424yfoUIzGovphWDlwNCf/2WOVLfIO5CBmauf4gFd2z0+ksMRoo1Lvy6VY2ftRHPO+UVQ006wDVI4ZQ7sdbsuOSxpKxbJ3lPzYpwYdkYW8AJb2KniwwccKojhppszGRC252glXejXFfIJfwT4QNYHw20PTu0AEYKBuQ/lZ7pEtAhyPoERfjP2UrXIKymLRnxj8ifVvcmb4qV3NtbUrAIvY5h8IfQrPacEITDWgXWC9x1gdgNcd8uBtRmiEO76fxTo6kQINrLPDn9Q28nDUEk1DWDfVnOeEILDCGOqP4ez5TnGxAqHyT19w3eJbQzr4G2rWNXiDbPuosvh5Eb1IWDQWW9FNqcvcLg2+MbJw== hainque@dhcp-guest-25.act-europe.fr
next prev parent reply other threads:[~2020-09-24 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 14:23 Olivier Hainque
2020-09-24 14:40 ` Frank Ch. Eigler
2020-09-24 15:14 ` Olivier Hainque [this message]
2020-09-24 16:24 ` Frank Ch. Eigler
2020-09-24 16:44 ` Olivier Hainque
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=51E7295E-58E8-4DAB-81BA-B49FEDCCD93D@adacore.com \
--to=hainque@adacore.com \
--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).