extern/KasmVNC
1
0
Fork 0
mirror of https://github.com/kasmtech/KasmVNC.git synced 2024-11-22 08:04:04 +01:00
Code Issues Packages Projects Releases Wiki Activity

Updated Differences From TigerVNC (markdown)

Kasm 2021-03-31 15:40:24 -04:00
parent 2c666f1811
commit 8982c9fa7f
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Differences-From-TigerVNC.md

@ -1,7 +1,7 @@
Kasm is focused on being a web native remote desktop server and client. We did not want to be tied down to conforming to the VNC protocol and wanted a single unified application rather than 3 separate components (TigerVNC, noVNC, websockify). Kasm is focused on being a web native remote desktop server and client. We did not want to be tied down to conforming to the VNC protocol and wanted a single unified application rather than 3 separate components (TigerVNC, noVNC, websockify).
# VNC Protocol # VNC Protocol
KasmVNC gets rid of the VNC service which by default listens on port 5901. While you can configure KasmVNC to enable that service, we provides no guarantees that we will keep VNC protocol compatibility. We also do not guarantee that we will upstream changes from TigerVNC that are not applicable to our goals. KasmVNC gets rid of the VNC service which by default listens on port 5901. While you can configure KasmVNC to enable that service, we provide no guarantees that we will keep VNC protocol compatibility. We also do not guarantee that we will upstream changes from TigerVNC that are not applicable to our goals.
# Authentication # Authentication
TigerVNC uses the VNC protocol's password based authentication, which has a limit of 8 characters. We have completely removed the VNC password and replaced it with HTTP Basic Authentication. Eventually we will replace basic auth with a more comprehensive authentication and session handling approach. TigerVNC uses the VNC protocol's password based authentication, which has a limit of 8 characters. We have completely removed the VNC password and replaced it with HTTP Basic Authentication. Eventually we will replace basic auth with a more comprehensive authentication and session handling approach.