Add CreateNamedPipeServerStream to named pipes options #56567
Merged
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
JamesNK
added
the
area-networking
JamesNK
requested review from
halter73,
BrennanConroy and
mgravell
as code owners
JamesNK
force-pushed
the
jamesnk/namedpipes-endpoint-security
branch
from
2053b36 to
5adbdc8
Compare
|
API is approved. Ready for review. |
amcasey
approved these changes
Jul 9, 2024
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.
Fixes #53306
Fixes #56568
Named pipes transport allows pipe security to be configured, but it's applied to all of server's named pipe endpoints.
This PR adds
CreateNamedPipeServerStreamfunc to options, allowing advanced users to customize creating endpoints. They can choose to specify differentPipeSecurityoptions on a per-endpoint basis.This feature is modeled after
SocketTransportOptions.CreateBoundListenSocket.