-
Notifications
You must be signed in to change notification settings - Fork 785
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
Misc access control enhancements #591
Comments
websockify is a bit of a toy server, so it lacks many features you'd expect from a production server. Like this one. It does support only doing WebSocket proxying, though. Simply don't include the |
According to the help screen (and my experience) leaving out the --web argument does not disable the web server, it just defaults the directory to the current directory. I have worked around this for now by pointing it to an almost empty folder, but it requires vnc.html to exist, so I created an empty vnc.html file. That's not an ideal solution though.
|
Running with these arguments definitely does NOT disable the web server. Note there is no --web. novnc_proxy --vnc 127.0.0.1:5900 --ssl-only --listen 192.168.0.254:6080 |
Here is some of the rather persistent code that insists on having a vnc.html and loading a web server...
|
Proposed patch...
|
This adds the ability to set --web NONE to disable the web server, otherwise the web folder defaults to the folder where the software is installed as it does now. If you specify --web NONE it also alters the startup message. |
Now I just need to figure out (if I can) how to restrict access to a specific list of source IPs. For now I am just binding the server to a non-internet network interface. |
The |
I have already developed a patch to add the option not to start the web server to the novnc_proxy script and posted it here. As I did so I realized that I could probably have called the other script directly, but I already finished my changes. That however, still leaves the question specifying an access list. |
Is your feature request related to a problem? Please describe.
There is no access control to restrict access to the proxy.
It would also be nice to be able to completely disable the web server portion and just enable the wss: proxy only.
Describe the solution you'd like
Maybe support for running the proxy from inetd/xinetd then TCP wrappers could be leveraged.
Describe alternatives you've considered
Or add built-in support to restrict the client IPs that are allowed to connect.
Additional context
I am trying to improve the security of this excellent software! :)
The text was updated successfully, but these errors were encountered: