libgit2 / libgit2/libgit2sharp
Unable to load shared Lib "git2-106a5f2" or one of its dependencies & "Negotiate" authentication is not supported
還沒有人認領這個 Issue。
- 主要語言
- C#
- 星號
- 3.5k
- 分支
- 925
- PR 合併指標
- 30 天內沒有已合併 PR
描述
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
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
首先,在所述的 .NET 6 Linux 容器中使用 LibGit2Sharp 0.26.2 和 0.27.0-preview-0182,按照重現步驟進行操作。檢查使用 DefaultCredentials 的 CloneOptions 回呼,並比較這些版本之間原生程式庫載入失敗和 Negotiate 失敗的情況。當相關失敗可以重現,且其受支援的解決方案或限制已記錄在案時,即視為完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- csharp, git, linux
- 領域
- authentication, backend, operating-systems
- Issue 類型
- 缺陷
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 35/100