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

Connection authentication #57

Closed
o-sdn-o opened this issue Dec 6, 2020 · 2 comments
Closed

Connection authentication #57

o-sdn-o opened this issue Dec 6, 2020 · 2 comments
Assignees

Comments

@o-sdn-o
Copy link
Collaborator

o-sdn-o commented Dec 6, 2020

Pipe ACL not applied for connection authentication under windows.

The ACLs in the default security descriptor for a named pipe grant full control to the LocalSystem account, administrators, and the creator owner. They also grant read access to members of the Everyone group and the anonymous account.

@o-sdn-o o-sdn-o self-assigned this Dec 6, 2020
@o-sdn-o o-sdn-o changed the title Win32: connection authentication Connection authentication Dec 6, 2020
@o-sdn-o
Copy link
Collaborator Author

o-sdn-o commented Dec 6, 2020

Connection authentication (checking pipe credentials) added in preview v0.2.2 for Linux.

broker:vtm <-pipe-> desktop:vtmd

Linux:

  • Initiator and root are only allowed to connect to the broker channel

@o-sdn-o
Copy link
Collaborator Author

o-sdn-o commented Dec 8, 2020

Win32 named pipes:
The ACLs in the default security descriptor for a named pipe grant full control to the LocalSystem account, administrators, and the creator owner. They also grant read access to members of the Everyone groupand the anonymous account. Without write access, the desktop is not accessible to non-owners.

Updated in preview v0.2.2 for Windows.

@o-sdn-o o-sdn-o closed this as completed Dec 8, 2020
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

No branches or pull requests

1 participant