Package: ssvnc
Version: 1.0.23-1
Severity: normal
The debian ssvnc package puts 'stunnel4' on its recommends list instead
of its depends list.
This leads to a situation that confuses nearly all users that start up
the SSVNC encryption gui (i.e. the main 'ssvnc' command), namely that
SSVNC's default mode of encryption is SSL and all of its documentation
assumes that SSL is it not disabled.
However, if a user tries to make an SSL connection (e.g. to GNOME desktop
vino) he will quickly find that it fails right away because the stunnel
command is not found. It will likely not be clear to them how to get
encryption to work.
Any VNC server supporting normal SSL (e.g. x11vnc -ssl or a server using
an SSL tunnel tool) or any VNC server supporting VeNCrypt or Anon TLS
could be directly connected to by SSVNC if only 'stunnel4' were installed.
Many server support these SSL modes, and the number is increasing:
VeNCrypt: QEMU, Xen, ggi, libvirt, virt-manager
Anon TLS: vino
I request that these two debian packages:
stunnel4
openssl
be placed on ssvnc's depends list so that SSL/TLS connections to the
above VNC servers and others is enabled by default.
Thank you,
Karl Runge
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
