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

Is there support for a native client? #132

Open
infokiller opened this issue Jan 23, 2023 · 4 comments
Open

Is there support for a native client? #132

infokiller opened this issue Jan 23, 2023 · 4 comments
Labels
enhancement New feature or request

Comments

@infokiller
Copy link

Hi and thanks for the project!
My main goal is running a remote OS with a native experience, including window management, OS keyboard shortcuts, etc. (similar to what RDP provides on Windows).
Is it possible to achieve it with KasmVNC?
I believe it requires having a native client

Thanks

@mmcclaskey
Copy link
Collaborator

KasmVNC does not have a native client, it is web native from the client side. You can create a PWA client pretty easily, electronjs client, or the easiest is running Chrome in app mode. Most shortcuts will work, but there are a few exceptions. Clipboard works seamlessly if using a Chromium based browser or chromium based solution like ElectronJS for a native app. Creating a native app is not currently scheduled, but it is a request we are tracking.

@mmcclaskey mmcclaskey added the enhancement New feature or request label Jan 23, 2023
@infokiller
Copy link
Author

Thanks a lot for the quick response!

@Niek
Copy link

Niek commented Jan 30, 2023

Related to this: does legacy VNC mode still work? Looking at the docs it seems that this should be possible (using -rfbport or -rfbunixpath) but I can't get it working.

@mmcclaskey
Copy link
Collaborator

You can technically turn on the RFB TCP port, however, we have strayed from the RFB spec and continue to increase the distance between our spec and the RFB spec. We don't test VNC clients, but even if they would connect, they would crash as soon as you clicked anywhere, because our mouse button down message has more bits to allow for additional mouse buttons. There are other changes, but that's the one that would likely come up first, assuming a VNC client would even connect to begin with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants