Document exposing VNC port securely via SSH - #6
Open
pascalw wants to merge 1 commit into
Open
Conversation
Owner
|
Thanks, @pascalw (sorry for the delay---I've been busy with non-rM work)! I entirely forgot that one could just pass arguments to libvncserver like that, honestly. This looks wonderful---I'll merge it later today or over the weekend. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hey @pl-semiotics thanks for this fantastic piece of software. It absolutely crushes https://github.com/rien/reStream in terms of latency and throughput, great work!
I noticed you recommend restricting the VNC port with iptables. I'm not sure if iptables even runs on the Remarkable (not out of the box at least). Fortunately libvncserver allows to bind on localhost only, which combined with an SSH tunnel allows to securely connect to the VNC server without exposing it publicly. I don't observe any increased latency running this way, it's still lightning fast (even via WiFi)!
Perhaps this can be mentioned in the README.