Open v-luzh opened 3 years ago
@v-luzh I was not able to repro this on Windows.
Can you post the output from dotnet nuget verify
please?
Please copy the console values instead of a screenshot. Thanks!
Hi @nkolev92, sorry, this bug just repro when signing, doesn't repro when verifying. Updated the bug.
As per comments, it would be better to confirm with both NuGet PM and the .NET CLI PMs about the verbosities.
It still reproes on .NET SDK Version: 8.0.400-rtm.24367.3 patched with Dev\6.12.0.33
Details about Problem
NuGet version: NuGet Client Dev\6.0.0.204 VS Version: Main\31617.326 OS: Windows-10-Enterprise-21H1
Detailed repro steps
./patchOnUnix.ps1
.dotnet pack
..\CreateTestCertificate.ps1 -AddAsTrustedRootAuthority -Password password -GenerateCerFile
in powershell.openssl x509 -inform DER -in <.cer file path> -out <.crt file path>
on Linux./dotnet nuget sign <PackageFilePath> --certificate-path <PfxFilePath> --certificate-password password
on Linux.Expected Result
There is certificate info when signing with Dotnet Nuget Sign Command.
Actual Result
No certificate info show when signing with Dotnet Nuget Sign Command as below screenshot.
Notes:
1.It is not a regression since it’s a new feature. 2.It repro on Linux/Windows/Mac. 3.Workaround: add an option “-v n” at the end of the signing command.