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.