Add missing -ProtectPrivateKey parameter to Import-PfxCertificate documentation#3977
Open
Synertry wants to merge 1 commit intoMicrosoftDocs:mainfrom
Open
Add missing -ProtectPrivateKey parameter to Import-PfxCertificate documentation#3977Synertry wants to merge 1 commit intoMicrosoftDocs:mainfrom
Synertry wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
…rivateKey parameter and example
Author
|
@microsoft-github-policy-service agree |
Contributor
|
Learn Build status updates of commit e06c290: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
This file contains hidden or 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
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.
PR Summary
Add missing

-ProtectPrivateKeyparameter to the Import-PfxCertificate cmdlet documentation.Parameter functionality is synonymous with the import option "Protect private key using virtualized-based security(Non-exportable)" in the Certificate Import Wizard:
Functionality of the option is explained by Crypt32 (Vadims Podans), creator of PSPKI:
https://security.stackexchange.com/a/186523/268642
Explanation for enum option
vsmis hinted in the documentation for Virtualization-based Security (VBS).Virtual Secure Mode (VSM) capabilities were introduced in Windows 10 and Windows Server 2016, that is why the update only ranges until there.
PR Checklist