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.

Sign up for GitHub

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

Jump to bottom

dotnet-mage gets caught in an infinite loop when NCryptEnumKeys is not implemented by the crypto provider. #309

Open
e455a81e-d3ba-41a2-bc6d-7aafb1d9a5cd opened this issue Nov 7, 2023 · 0 comments
Open

dotnet-mage gets caught in an infinite loop when NCryptEnumKeys is not implemented by the crypto provider. #309

e455a81e-d3ba-41a2-bc6d-7aafb1d9a5cd opened this issue Nov 7, 2023 · 0 comments
Labels
area-ClickOnce

Comments

@e455a81e-d3ba-41a2-bc6d-7aafb1d9a5cd
Copy link

Description

The crypto provider function NCryptEnumKeysFn is optional and may respond with NTE_NOT_SUPPORTED. Using dotnet-mage with such a crypto provider traps the application in the while loop of the Certificate.GetContainersFromCngProvider method.

Configuration

I am using dotnet-mage 7.0.0 on Windows 10 with a custom KSP implementation like this:
dotnet-mage -Sign TestClickOnce.exe.manifest -CertFile .\ACME.cer -CryptoProvider "MyKSP" -KeyContainer "MyKeyContainer"

Regression?

I don't think so.

Other information

None
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-ClickOnce
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@e455a81e-d3ba-41a2-bc6d-7aafb1d9a5cd @MichaelSimons @NikolaMilosavljevic