Support CNG certificates #483
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… specify if CNG should be used when importing pfx. Expose the following extra options: * pfx_exportable - mark private key as exportable * pfx_prefer_cng_ksp - use ksp if preference is not specified * pfx_always_cng_ksp - force ksp certificate Signed-off-by: Taliesin Sisson <[email protected]>
|
as I see def cert_script(persist) implementation doesn't changed, and it deletes private key on second run. |
|
We're in the process of converting the certificate resources to use the win32-certstore gem, which will allow us to add a lot of the functionality here without having to get crazy complex in the resources themselves. That first bit of work landed in #558. Take a look and please let us know if there's anything you need that we can add. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Anything below .Net 4.61 does not have the ability to deal with CNG certificates correctly. This means powershell does not have the ability either. Places with strict security set this to default, so when the cert is created and added it will default to CNG. When trying to set permissions on certificate, powershell can't access private key so it can't set permissions.
Issues Resolved
#481
Check List
README has been updated to include new features
Works on my machine badge. But I haven't run all the tests. Hoping for pull request to flesh out any issues.