Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add CurrentUserOnly flag support to ServerFactory on .NET Framework #47

Merged
merged 1 commit into from
Feb 24, 2023
Merged

Add CurrentUserOnly flag support to ServerFactory on .NET Framework #47

merged 1 commit into from
Feb 24, 2023

Conversation

AArnott
Copy link
Member

@AArnott AArnott commented Feb 24, 2023

This makes named pipes set up on .NET Framework as safe as on .NET.

There are two sides to this:

  1. The server, which can ACL its own pipe to ensure its security.
  2. The client, which has to connect to the pipe first and then check the ACL in order to verify it is owned by a server with the expected ACLs.

@AArnott
Add CurrentUserOnly flag support to ServerFactory on .NET Framework
c5c519f 
This makes named pipes set up on .NET Framework as safe as on .NET.
@AArnott AArnott added the enhancement New feature or request label Feb 24, 2023
@AArnott AArnott merged commit f31dfc4 into microsoft:main Feb 24, 2023
@AArnott AArnott deleted the addCurrentUserOnlyCheckToNetFx branch February 24, 2023 22:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@RyanToth3 RyanToth3 RyanToth3 approved these changes

Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@AArnott @RyanToth3