-
Notifications
You must be signed in to change notification settings - Fork 254
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
dotnet nuget sign: Unknown error (0xc100000d) #13340
Comments
Hey @edoardo-kolver, Is this consistently reproducible/ |
I opened this issue on the dotnet repo (
dotnet/sdk#39640
) and they closed it and said it was a nuget issue, to open it there
Edoardo Colasante
Regional Manager | Support Engineer
phone: +1 (858) 319 - 6506
www.kolver.com
…On Wed, Mar 27, 2024 at 15:26 Nikolche Kolev ***@***.***> wrote:
Hey @edoardo-kolver <https://github.com/edoardo-kolver>, Is this
consistently reproducible/
Given that this is coming from a runtime package, it's likely something
we'll need to move to the dotnet/runtime repo.
—
Reply to this email directly, view it on GitHub
<#13340 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AU7ZEW3V522DXZBFRHA5II3Y2NBQXAVCNFSM6AAAAABFB2FYSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRUGA4TEMRWGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I saw that, we need to fw it to the dotnet/runtime repo: https://github.com/dotnet/runtime |
moved to https://github.com/dotnet/sign |
dotnet/sign is a separate thing from dotnet nuget sign. dotnet sign aims to be a broader tool. I'd recommend posting in dotnet/runtime. |
Ok my mistake. I reopened on dotnet/runtime#100414 and closed on dotnet sign |
NuGet Product Used
dotnet.exe
Product Version
8.0.101
Worked before?
No response
Impact
It bothers me. A fix would be nice
Repro Steps & Context
Describe the bug
I try to sign a nuget package with my EV2 code signing certificate from Entrust and I get this error:
error: Unknown error (0xc100000d)
To Reproduce
This is the command I'm using (with some info redacted):
dotnet nuget sign "mynugetpackage.nupkg" --certificate-path "mycert.cer" --timestamper "http://timestamp.entrust.net/rfc3161ts2" -v detailed
And this is the output I'm getting (with some info redacted). The information on the certificates matches what I expect for my certificate.
Exceptions (if any)
System.Security.Cryptography.CryptographicException: Unknown error (0xc100000d)
Further technical details
dotnet --info
Verbose Logs
The text was updated successfully, but these errors were encountered: