From: "Laszlo Ersek" <lersek@redhat.com>
To: "Ni, Ray" <ray.ni@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
Leif Lindholm <leif@nuviainc.com>,
"'Andrew Fish (afish@apple.com)'" <afish@apple.com>,
Liming Gao <gaoliming@byosoft.com.cn>
Subject: Re: Does anyone meet the github SSH access issue?
Date: Thu, 4 Feb 2021 10:22:36 +0100 [thread overview]
Message-ID: <8ef771c1-9152-9de6-ea22-b4bd87bf47fe@redhat.com> (raw)
In-Reply-To: <CO1PR11MB4930D54BDF8EFF2E76A986728CB39@CO1PR11MB4930.namprd11.prod.outlook.com>
On 02/04/21 06:47, Ni, Ray wrote:
> I met the following errors when trying to pull content from github:
> --------------
> E:\Work\edk2>git pull upstream master
> kex_exchange_identification: Connection closed by remote host
> Connection closed by UNKNOWN port 65535
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> ----------------
>
> After a broader using of my computer, I found that not just github, but also
> some of other websites/services (Like Webex) cannot work normally.
> All they complained is about the invalid certification.
>
>
I've not encountered this issue.
It may not be a certificate problem on your part, but your crypto
libraries / configuration could be too old, and the TLS negotiation
could fail, if github now requires stronger crypto than what your system
supports (or is configured to permit).
Thanks
Laszlo
prev parent reply other threads:[~2021-02-04 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 5:47 Does anyone meet the github SSH access issue? Ni, Ray
2021-02-04 9:22 ` Laszlo Ersek [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-list 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=8ef771c1-9152-9de6-ea22-b4bd87bf47fe@redhat.com \
--to=devel@edk2.groups.io \
/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