-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Allow multiple private key references in Unix PFXes #55425
Conversation
Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq, @GrabYourPitchforks Issue DetailsFixes #44535. Windows has a complicated state for when a PFX contains two certificates that link to the same private key:
When the Unix PFX loader was written it was based on the EphemeralKeySet behavior, because that's what the tests used (to avoid disk penalties and problems). Trying to maintain a balance between Herculean efforts of bug-for-bug compatibility and OS variability, this change takes a simpler approach:
|
Is there a way I can test this branch myself? |
@mark-raymond You should be able to checkout pull/55425/head, or do something like the merge command line instructions suggests:
Then the usual build and such |
There are docs on using your build here: https://github.com/dotnet/runtime/blob/main/docs/workflow/testing/using-your-build.md. |
Looks like there's an "Apple is different" case that I missed: In TwoCerts_CrossedKeys I believe the Keychain APIs won't bind the wrong private key to the cert, so we get back a cert where HasPrivateKey is false. Making sure the fix works on a mac before pushing it. |
Fixes #44535.
Windows has a complicated state for when a PFX contains two certificates that link to the same private key:
When the Unix PFX loader was written it was based on the EphemeralKeySet behavior, because that's what the tests used (to avoid disk penalties and problems).
Trying to maintain a balance between Herculean efforts of bug-for-bug compatibility and OS variability, this change takes a simpler approach: