libgit2 / libgit2/libgit2sharp
Certificate Verification Failed "unknown certificate lookup failure"
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
Description
I recently updated libgit2sharp (v0.26.2) to the latest v0.30.0.
Some of my product users are located in Taiwan, some are in China, and some are from Europe and the United States.
Before the upgrade, the company's internal repository could be accessed normally through the Repository.Clone API.
(URL and WorkDir only, no other options)
After the upgrade, users located in China will fail and get an error about SSL/TLS being unable to verify, as shown below.
We tried to troubleshoot other network issues and confirmed that all users were on the same OS version and supported TLS 1.2/1.3 only.
And do cross comparison with git CLI (git v2.43.0).
Everyone can download normally through the CLI, and will not encounter SSL/TLS verification errors when using libgit2sharp v0.26.2.
Only users located in China will encounter SSL/TLS verification failure in libgit2sharp v0.30.0.
Version of LibGit2Sharp (release number or SHA1)
v0.30.0
Operating system(s) tested; .NET runtime tested
Windows11
OS Build 22631.3593
Windows Feature Experience Pack 1000.22700.1003.0
.NET Framework 4.7.2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Repository.Clone API and compare certificate-verification behavior between libgit2sharp v0.26.2 and v0.30.0. Reproduce the failure on Windows 11 with .NET Framework 4.7.2 in the affected environment; done means the internal repository can be cloned without the SSL/TLS verification error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- devtools, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100