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

[Feature]: Nuget Sign Support for CSP's and thus HSM's outside of the Windows Store #11437

Open
iamjplant opened this issue Dec 7, 2021 · 0 comments
Labels
Functionality:Signing Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Type:Feature

Comments

@iamjplant
Copy link

iamjplant commented Dec 7, 2021

NuGet Product(s) Involved

NuGet.exe

The Elevator Pitch

Over at #5907 (comment) the parameters for CryptographicServiceProvider and KeyContainer were removed. I would like those added back.
Certificates are inherently ephemeral things. As it stands, I have to add my signing certificate to the Windows Cert Store as part of my Jenkins pipeline. Setting up my HSM is accomplished as part of setting up my Jenkins agent, which is fine. I would like to be able to inject my certificate dependency as part of my pipeline. Then I could just have a simple "nuget sign -CryptographicServiceProvider 'some_hsm_provider' -KeyContainer 'mycontainer' -CertificatePath 'mypath'"
The discussion on #5907 is not wrong in that the same goal can be accomplished with the use of the Windows Cert Store, which is what I'm doing. It would be nicer for the CI/CD setting to have a more direct way to sign packages.

Additional Context and Details

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Functionality:Signing Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Type:Feature
Projects
None yet
Development

No branches or pull requests

5 participants