Git Fetch fails with could not decrypt tls message when TLS 1.3 is allowed
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- csharp, git
- Domain
- networking, security
Research direction
Start by running the reported LibGit2Sharp.Tests reproduction on Windows 10 with TLS 1.3 enabled, then trace the HTTPS fetch path that produces the “could not decrypt tls message” error. Done means the fetch completes without that error and the regression is covered by the existing test suite.
Written by the indexing model from the issue text.
Description
Reproduction steps
On windows 10 create keys "TLS 1.3\Client" under "Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols"
and two DWORDS "DisabledByDefault" with value 0 and Enabled with value 1.
Then create a repository and add a remote with https://github.com/libgit2/libgit2sharp.git and run a git fetch.
Expected behavior
No error fetch is executed
Actual behavior
Error "could not decrypt tls message"
Version of LibGit2Sharp (release number or SHA1)
LibGit2Sharp 0.30.0 but can also be reproduced with 0.27.2
Operating system(s) tested; .NET runtime tested
Win 10 22H2 x64 .NET 4.8
This issue can also reproduced with the LibGit2Sharp.Tests
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
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.
More from libgit2/libgit2sharp
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
libgit2/libgit2sharp#2193 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
libgit2/libgit2sharp#2192 · 1 comment ·
-
Website is down Open
Difficulty 4/5 3-5 days Newbie friendliness 20/100
libgit2/libgit2sharp#2191 · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
libgit2/libgit2sharp#2189 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
libgit2/libgit2sharp#2187 · 2 comments ·
All issues in libgit2/libgit2sharp
Similar issues
-
Status: Waiting triage Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
nanoframework/Home#1857 ·
-
kind/bug kind/regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
unoplatform/uno.toolkit.ui#1646 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nightscout/nocturne#1379 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
elastic/esql-dotnet#47 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100