We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In addition to authorized connections, it would be nice to add connection requests for privacy. Some x0vnc QueryConnect analog.
The text was updated successfully, but these errors were encountered:
There could be an option to call a user defined command upon connection, which would determine if the connection is accepted or not.
Sorry, something went wrong.
Now that we have an IPC mechanism in wayvncctl, maybe this would be easier to do.
I'd suggest a new IPC command like event-receive that would register a client to be an auth-handler.
event-receive
Then the client could expect to receive an auth-attempt IPC call, and would be expected to respond with a allow/disallow response.
auth-attempt
Care must be taken to deal with the server's behavior with multiple IPC clients, and what to do in the event of nonresponse arriving.
This is probably a good enough solution:
wayvncctl
wayvncctl client-auth-accept
wayvncctl client-auth-reject [reason]
No branches or pull requests
In addition to authorized connections, it would be nice to add connection requests for privacy. Some x0vnc QueryConnect analog.
The text was updated successfully, but these errors were encountered: