NuGet/Home

Add CLI option for `disableTLSCertificateValidation` property

Open

#14,061 建立於 2025年1月22日

在 GitHub 查看
 (1 留言) (2 反應) (0 負責人)HTML (1,459 star) (292 fork)batch import
Priority:3Type:Featurehelp wanted

描述

NuGet Product(s) Involved

NuGet.exe, dotnet.exe

The Elevator Pitch

Some time ago the property disableTLSCertificateValidation was added to nuget config sources (#12996, #13023, #13478). But this property is not represented by any CLI option so it needs to be added manually in the NuGet config file.

Similar to how allowInsecureConnections has a CLI option, I would suggest adding a CLI option to set the disableTLSCertificateValidation when using nuget sources add and dotnet nuget add source.

Additional Context and Details

No response

貢獻者指南

技術棧
csharp
領域
clisecurity
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
C#NuGet internalsCLI design
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
Examine the existing implementation of 'allowInsecureConnections' CLI option in NuGet sources (see PRs #12996, #13023, #13478). Look at how the 'disableTLSCertificateValidation' property is used in config files and how the CLI option for 'allowInsecureConnections' was added. The relevant code is likely in the NuGet.Client repository under src/NuGet.Clients or similar. Focus on the command handlers for 'nuget sources add' and 'dotnet nuget add source' to understand the pattern for adding new options.
Add CLI option for `disableTLSCertificateValidation` property · NuGet/Home#14061 | Good First Issue