Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: X.509 trust store isn't initialized in dotnet add package and SDK resolver code paths #11956

Closed
dtivel opened this issue Jul 8, 2022 · 0 comments · Fixed by NuGet/NuGet.Client#4720

Comments

@dtivel
Copy link
Contributor

dtivel commented Jul 8, 2022

NuGet Product Used

dotnet.exe

Product Version

latest

Worked before?

no

Impact

I'm unable to use this version

Repro Steps & Context

  1. On Red Hat 9, use the https://github.com/NuGet/Entropy/tree/main/SDKPatchTool to install the latest .NET 6.0.4xx SDK using NuGet build 6.3.0.117 for patching.
  2. Create a test console project using the patched SDK.
  3. Using the patched SDK, execute dotnet add package Nuget.Common --version 5.0.0

Results:

  1. The operation will fail with certificate warnings.
  2. As of writing this, [release/6.0] OpenSslX509ChainProcessor: ignore NotSignatureValid on last element. dotnet/runtime#70343 was also a factor.

Verbose Logs

No response

@dtivel dtivel self-assigned this Jul 8, 2022
@dtivel dtivel changed the title [Bug]: X.509 trust store isn't initialized in dotnet add package code path [Bug]: X.509 trust store isn't initialized in dotnet add package and SDK resolver code paths Jul 8, 2022
dtivel added a commit to NuGet/NuGet.Client that referenced this issue Jul 12, 2022
dtivel added a commit to NuGet/NuGet.Client that referenced this issue Jul 13, 2022
@jeffkl jeffkl added this to the 6.3 milestone Jul 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment