Unable to load shared Lib "git2-106a5f2" or one of its dependencies & "Negotiate" authentication is not supported
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp, git, linux
- Domain
- authentication, backend, operating-systems
Research direction
Start with the reproduction steps using LibGit2Sharp 0.26.2 and 0.27.0-preview-0182 in the described .NET 6 Linux container. Inspect the CloneOptions callback using DefaultCredentials and compare the native library-loading and Negotiate failures across those versions. Done means the relevant failure is reproducible and its supported resolution or limitation is documented.
Written by the indexing model from the issue text.
Description
Reproduction steps
Our .net 6 app uses LibGit2Sharp 0.26.2 version . Our git is in Bitbucket which accepts Kerberos via SPNEGO. It all works fine in our windows environment. when we do dotnet publish ...... -r linux-x64 , I see that the 'git2-106a5f2' is also copied. A container is created with Linux/ubi7 to run the app, where we get the Unable to load shared Lib "git2-106a5f2" or one of its dependencies
Later I upgraded it to 0.27.0-preview-0182 which fixed Unable to load shared Lib "git2-106a5f2". However, it start throwing "Negotiate" authentication is not supported when Repo.Clone is called with CloneOptions.
CloneOptions is given a new DefaultCredentials() call back , to work with SPNEGO.
Version of LibGit2Sharp (release number or SHA1)
LibGit2Sharp 0.26.2 - Unable to load shared Lib "git2-106a5f2"
0.27.0-preview-0182 - "Negotiate" authentication is not supported
Operating system(s) tested; .NET runtime tested
.net 6
- 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
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 75/100
sillsdev/languageforge-lexbox#2665 ·
-
bug documentation frontend
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
azurenoops/spin_agent#975 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·