-
Notifications
You must be signed in to change notification settings - Fork 252
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
[Cross-Platform Sign Verify] Unexpected error NU3018 show after restoring project on Linux #10328
Comments
fyi @heng-liu, @kartheekp-ms |
Triage: Assigning to @kartheekp-ms |
I could not repro for two test cases mentioned above: I could only repro for test case: "Cross-platform verify: signed package with expired signing certificate" |
If we build the chain for the expired self-issued certificate by using the following policy setting:
The chain build on Linux is different from other platforms: But if we build the chain for the expired leaf certificate issued by intermediate CA by using the same policy setting, Since we use self-issued certificate for testing, but the packages on nuget.org uses a leaf certificate issued by intermediate certificate. It means the test fails but the real world works. |
Raised an issue in dotnet/runtime#48794 |
@heng-liu, @v-luzh - Closing as dupe of dotnet/runtime#48794 |
Details about Problem
NuGet version: NuGet Client Dev\5.9.0.6972
VS Version: Main\30726.31
OS: Windows-10-Enterprise-19h2
Detailed repro steps
nuget spec
.nuget pack <packagename>.csproj
, create a new test certificate:.\CreateTestCertificate.ps1 -AddAsTrustedRootAuthority -GenerateCerFile
.NuGet.exe sign <PackageFilePath> -CertificatePath <PfxFilePath> -Timestamper http://timestamp.entrust.net/TSS/RFC3161sha2TS
.openssl x509 -inform DER -in <.cer file path> -out <.crt file path>
.<patchedSDKPath>./dotnet nuget locals all –clear
.<patchedSDKPath>./dotnet restore
.Expected Result
There were no errors or warnings, and restore is successful.
Actual Result
Unexpected error NU3018 show as below.
Notes
The text was updated successfully, but these errors were encountered: