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.

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

FR: Ability to specify different impersonation levels for named pipe clients #297

Closed
dblohm7 opened this issue Aug 8, 2023 · 0 comments · Fixed by #302
Closed

FR: Ability to specify different impersonation levels for named pipe clients #297

dblohm7 opened this issue Aug 8, 2023 · 0 comments · Fixed by #302

Comments

@dblohm7
Copy link
Contributor

dblohm7 commented Aug 8, 2023

I'd like to be able to use impersonation levels other than SECURITY_ANONYMOUS; can we expose an override somewhere?

I'm happy to implement this provided that it would be accepted...

dblohm7 added a commit to dblohm7/go-winio that referenced this issue Aug 16, 2023
I would like to use impersonation on the server side of the pipe, but I
currently cannot because all pipes are connected using the anonymous
impersonation level.

This patch adds a new function that provides the ability to explicitly
specify the desired impersonation level.

Fixes microsoft#297

Signed-off-by: Aaron Klotz <[email protected]>
dblohm7 added a commit to dblohm7/go-winio that referenced this issue Sep 28, 2023
I would like to use impersonation on the server side of the pipe, but I
currently cannot because all pipes are connected using the anonymous
impersonation level.

This patch adds a new function that provides the ability to explicitly
specify the desired impersonation level.

Fixes microsoft#297

Signed-off-by: Aaron Klotz <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant