-
Notifications
You must be signed in to change notification settings - Fork 5.3k
[release/5.0-preview5] Ignore the private key handle cert property for persisted keys #36312
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
Conversation
When a CERT_CONTEXT value has both property 2 (prov info) and property 78 (ncrypt key handle), prefer to load based on the property 2 state. This avoids a scenario where calling Get[Algorithm]PrivateKey sets the 'CLR IsEphemeral' property on a persisted key, preventing future loads of that key. An alternative approach of preferring the loaded key over the cold-load was not selected to avoid value contamination of ephemeral properties set on the CngKey object directly after the caller calls Get[Algorithm]PrivateKey.
joperezr
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Package index changes port looks good
mkArtakMSFT
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
|
@mkArtakMSFT can you please let us know, when your vendors have successfully validated? |
|
@danmosemsft they run validation on daily builds - similar to how other CTI vendors do. So this should be merged to get a preview 5 build, so they can validate it |
|
Thanks yes, I saw @Anipik close it and thought it got merged 😋 |
|
some of the branches were hung, so i reopen it to run the start thiose again |
Its already approved by servicing cc @danmosemsft
Ports #36287
Fixes #36273
cc @javiercn @mkArtakMSFT