VNC client over pure HTTPS via Piping Server on Web browser
OTHER License
VNC client over pure HTTPS via Piping Server
This project requires the latest Google Chrome with enable-experimental-web-platform-features flag for fetch() upload streaming feature (origin trial now).
chrome://flags/ > Experimental Web Platform features > Enabled
This project is highly based on noVNC. Thanks to the original authors!
e.g. https://piping-vnc.nwtgck.org/vnc.html#?cs_path=aaa&sc_path=bbb.
Use #?
, which does not send parameters to the hosting server: piping-vnc.nwtgck.org.
password
: VNC passwordserver
: Piping Server URLcs_path
: Server-to-client pathsc_path
: Client-to-server pathvnc_server_port
: VNC server port for command hintheaders
: HTTP headers to Piping Server
[["X-MyExtra1", "myvalue1"], ["Content-Type", "application/myapp"]]
)e2ee
: E2E encryption option
{ "cipher_type": "openssl-aes-256-ctr", "pass": string, "pbkdf2": { "iter": number, "hash": "sha1" | "sha256" | "sha512" } }
)cd <this repo>
git submodule update --init --recursive # (once)
npm ci # (once)
npm run build-openssl-aes-ctr-stream # (once)
python3 -m http.server
Then, open http://localhost:8000.
VNC server sides need a VNC server, netcat (nc) and curl.
See AUTHORS for a (full-ish) list of authors. If you're not on that list and you think you should be, feel free to send a PR to fix that.
Core team:
Previous core contributors:
Notable contributions:
Included libraries: