Tuesday, 10 December 2024

vnc

Two generations of my computer face off. And an instance of https://github.com/stylehouse/jamola



Install something,

$ ssh v x11vnc -storepasswd .local/share/vnc/passwd

If you want a modicum of security, use a password, despite having ssh just there... The two cannot be combined as tightly as you would hope for secure access. Probably because we just use ssh.

server?

port 5900

$ ssh v x11vnc -display :0 -localhost -forever -shared -rfbauth .local/share/vnc/passwd 

Or possibly: 

$ ssh v x11vnc -display :0 -localhost -forever -shared -nopw 

these seem to hang around over there if I Ctrl+C (sigint?) them or disconnect.

client

Via the web

For vnc clients in your pocket, make that available via html and bring its port over:

$ ssh -L 6082:localhost:6082 v novnc_proxy --listen localhost:6082 --vnc localhost:5900

vnc, remotely

web can be a bit slow for testing things, even locally, so bring the vnc port over instead:

$ ssh -L 5900:localhost:5900 v
$ vncviewer localhost

Bold commands are forever run, in their own terminal.

If the vnc screen is all black and uninteractive... I had to unlock the computer in real life, then it reveals.

You get to keep looking at your sensors or etc during a crash, since the last image hangs in the client...

It's a bit laborious to keep doing these things.

If you're suggesting some kind of remote-able supervisor that brings up various systems and does the plumbing... It would need to find running instances of its commands from before network changes, etc, see "seem to hang around".

usually

I just type 'nico' at the terminal, which is bin/nico:
#!/bin/bash
cd ~/src/nicotine-docker
docker compose up -d
vncviewer localhost:59234 &
./upnp-and-run.sh
The upnp part also ensures port forwarding, which at least one peer must have to initiate a connection, and re-ups.

Copy paste

Is clunky in novnc. You paste in a web UI drawer's <textarea> first.

In vncviewer it can seem dodgy.
Middle-click (aka the PRIMARY buffer, the latest text selection buffer) works better than the regular C-C C-V (CLIPBOARD buffer), which involves content type negotiation.

I noticed it depends on the application you copy the text from
eg gnome-terminal and Strawberry (all Qt applications?)
will need that text copied somewhere else (eg your browser's address bar) first, then over VNC.

I suspect it also monitors your buffer for changes to sync, so you have to do the copy after it has seen something else in your buffer.

So it worked for me!

Thanks!

No comments:

Post a Comment