From: "Xionghu Luo" <yingyuefengyi@163.com>
To: mark <mark@klomp.org>,
"yingyuefengyi--- via Overseers" <overseers@sourceware.org>
Cc: "yingyuefengyi--- via Overseers" <overseers@sourceware.org>
Subject: Re: Request from Xionghu Luo
Date: Tue, 22 Feb 2022 00:47:21 +0800 (GMT+08:00) [thread overview]
Message-ID: <968fa88.19e6.17f1d2e32f6.Coremail.yingyuefengyi@163.com> (raw)
In-Reply-To: <Yg+dOhApiU/v+Csk@wildebeest.org>
Ping?
thanks， i leaved IBM to another company, so I don't have access to the machine lep824e1v.canlab.ibm.com any more, how to handle such kind of circumstance, please?
| |
yingyuefengyi@163.com
|
|
邮箱：yingyuefengyi@163.com
|
---- 回复的原邮件 ----
| 发件人 | Mark Wielaard<mark@klomp.org> |
| 日期 | 2022年02月18日 21:20 |
| 收件人 | Overseers mailing list<overseers@sourceware.org> |
| 抄送至 | Xionghu Luo<yingyuefengyi@163.com> |
| 主题 | Re: Re: Request from Xionghu Luo |
On Fri, Feb 18, 2022 at 02:08:24PM +0800, Xionghu Luo via Overseers wrote:
>
> Sorry Christopher, but I couldn't update the sshkey now with any
> username. What's wrong with this? Thanks.
>
> xionghuluo@XIONGHULUO-MB0:~$ cat ~/.ssh/id_rsa.pub
> ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDJNZxhmax0DKFf9F1PmTwSKBRdV8vf83Y7Ddj2whE0TI47bKCUSHriP00AERLpYrApEPNeyF+9+npy2zoRaxoztRh9jbwTVi/25bWb0iIpUv6jBZJZ0qo0BRppVz0QGCdx7NriDY51LEbzOEKUzANV97SooOP8IQVeA+FTS792WKdWaioAzN8hwIV/TeRWhZIlJT3RO3NtMdOaFLbHI53/gSLoTnhwikOmFPZnVuLZcpDUnOyOzb9jElx2zKhosXWu95aa+tuojdBWxlg1Bl3AF/neP3zL71eWpvjuC/vGJj1+DpM7Y69ohMMh1AIh+gKx+QcNpw1v4/uoTx6HoA3AweDYO6lyH688V2HCyV2cMynUXl/g6B4sZvStoM16FVMKVEyPL3LrRnydiVRaA1UIILp/xVB5PuSvp1+QO143hybgjM2ho2+HKdxnfAxL7ESkoimSxKyBEp3MQKOYTtb/5CcVnNfMCQrV1WO8ue88heFXSWWlsBgi+rqXrzIdXBk= xionghuluo@XIONGHULUO-MB0
> xionghuluo@XIONGHULUO-MB0:~$ ssh sourceware.org updatekey < ~/.ssh/id_rsa.pub
> xionghuluo@sourceware.org: Permission denied (publickey).
> xionghuluo@XIONGHULUO-MB0:~$ ssh xionghuluo@sourceware.org updatekey < ~/.ssh/id_rsa.pub
> xionghuluo@sourceware.org: Permission denied (publickey).
> xionghuluo@XIONGHULUO-MB0:~$ ssh luoxhu@sourceware.org updatekey < ~/.ssh/id_rsa.pub
> luoxhu@sourceware.org: Permission denied (publickey)
Your user is luoxhu, but you need the rsa key associated with
luoxhu@lep824e1v.canlab.ibm.com
Cheers,
Mark
next prev parent reply other threads:[~2022-02-21 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 4:20 yingyuefengyi
2022-02-18 5:21 ` Christopher Faylor
2022-02-18 5:26 ` Christopher Faylor
2022-02-18 6:08 ` Xionghu Luo
2022-02-18 13:20 ` Mark Wielaard
2022-02-18 14:28 ` Xionghu Luo
2022-02-21 16:47 ` Xionghu Luo [this message]
2022-02-22 12:27 ` mark
-- strict thread matches above, loose matches on Subject: below --
2022-02-18 2:10 yingyuefengyi
2022-02-18 2:10 yingyuefengyi
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=968fa88.19e6.17f1d2e32f6.Coremail.yingyuefengyi@163.com \
--to=yingyuefengyi@163.com \
--cc=mark@klomp.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).