This repository was archived by the owner on Jan 23, 2023. It is now read-only.
Ignore CTRequired when building an X509 chain#35246
Merged
safern merged 1 commit intodotnet:masterfrom Feb 12, 2019
vcsjones:35224_ignore_require_ct
Merged
Ignore CTRequired when building an X509 chain#35246safern merged 1 commit intodotnet:masterfrom vcsjones:35224_ignore_require_ct
safern merged 1 commit intodotnet:masterfrom
vcsjones:35224_ignore_require_ct
Conversation
bartonjs
approved these changes
Feb 11, 2019
Member
|
Merged since we were hitting failures in other PRs and these PR was green on both, Jenkins and Azure legs. |
Member
Member
|
@danmosemsft, that change was already merged ;-) |
Member
|
Yeah, I know, sometimes it's just a convenient place to ask questions.. |
Member
No, I mean the |
Member
|
Ah - I see, in another PR. cool. thanks. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes #35224
/cc @bartonjs @stephentoub