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
..
__init__.py	test: each app keeps its tests in a tests package	2026-10-12 15:17:30 +03:00
test_cli_parsers.py	test: each app keeps its tests in a tests package	2026-10-12 15:17:30 +03:00
test_live_serial.py	test: live tests with one host for TCP and SSH, and order-independent migration fakes	2026-10-18 11:53:06 +03:00
test_socketiod.py	fix(console): a serial console worker holds only its own terminal	2026-10-26 19:01:02 +03:00
test_socketiod_child.py	refactor(console): socketiod on gunicorn threads instead of eventlet	2026-10-17 20:36:58 +03:00
test_sshtunnels.py	fix(console): an SSH compute's VNC console goes through ssh -W	2026-10-26 19:21:22 +03:00
test_views.py	fix(console): an SSH compute's VNC console goes through ssh -W	2026-10-26 19:21:22 +03:00