catborise 294b008811 fix(console): an SSH compute's VNC console goes through ssh -W ... - The tunnel is `ssh -W` to the console's address or Unix socket: the compute needs no nc and runs no shell. The old tunnel, copied from virt-manager, built a shell script with the console's address and socket path in it and eval'd it on the compute, and always passed "-p 22", overriding a Port in the SSH configuration. - On an SSH compute the console always goes through the tunnel, also when it listens on a network address: it was sent there unencrypted. - ssh never prompts (BatchMode) and gives up connecting after 10 seconds; when it fails, what it said is logged. The tunnel ends with the session.		2026-10-26 19:21:22 +03:00
..
migrations	Add app	2015-02-27 14:25:41 +02:00
templates	fix(console): the console page connects only to the panel's own proxy	2026-10-26 16:14:37 +03:00
tests	fix(console): an SSH compute's VNC console goes through ssh -W	2026-10-26 19:21:22 +03:00
__init__.py	Add app	2015-02-27 14:25:41 +02:00
models.py	ci: replace super-linter with ruff	2026-10-04 01:08:11 +03:00
novncd	fix(console): an SSH compute's VNC console goes through ssh -W	2026-10-26 19:21:22 +03:00
socketiod	fix(console): a serial console worker holds only its own terminal	2026-10-26 19:01:02 +03:00
sshtunnels.py	fix(console): an SSH compute's VNC console goes through ssh -W	2026-10-26 19:21:22 +03:00
tokens.py	feat(console): a working serial console	2026-10-17 19:43:09 +03:00
views.py	fix(console): a VNC console connects to the VM its page was opened for	2026-10-26 19:01:02 +03:00