Your message dated Sun, 01 Nov 2009 00:16:13 +0000
with message-id <[email protected]>
and subject line Bug#553411: fixed in ssvnc 1.0.24-1
has caused the Debian Bug report #553411,
regarding SSVNC's SSL support should not be disabled by default.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
553411: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553411
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: ssvnc
Source-Version: 1.0.24-1
We believe that the bug you reported is fixed in the latest version of
ssvnc, which is due to be installed in the Debian FTP archive:
ssvnc_1.0.24-1.diff.gz
to main/s/ssvnc/ssvnc_1.0.24-1.diff.gz
ssvnc_1.0.24-1.dsc
to main/s/ssvnc/ssvnc_1.0.24-1.dsc
ssvnc_1.0.24-1_amd64.deb
to main/s/ssvnc/ssvnc_1.0.24-1_amd64.deb
ssvnc_1.0.24.orig.tar.gz
to main/s/ssvnc/ssvnc_1.0.24.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Magnus Holmgren <[email protected]> (supplier of updated ssvnc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sat, 31 Oct 2009 21:02:42 +0100
Source: ssvnc
Binary: ssvnc
Architecture: source amd64
Version: 1.0.24-1
Distribution: unstable
Urgency: low
Maintainer: Magnus Holmgren <[email protected]>
Changed-By: Magnus Holmgren <[email protected]>
Description:
ssvnc - Enhanced TightVNC viewer with SSL/SSH tunnel helper
Closes: 544250 553411
Changes:
ssvnc (1.0.24-1) unstable; urgency=low
.
* New upstream release.
* ssvnc -help now prints a help message instead of passing -help to the
tcl interpreter.
* confusing_-h.dpatch (new): Improve upstream's handling of -help a bit
(Closes: 544250).
* ultraftp_path.dpach (new): Use hardcoded (and correct for this
package) path to ultraftp.jar if SSVNC_ULTRA_FTP_JAR is unset, so that
file transfers work even if ssvncviewer is executed directly.
* bashisms.dpatch (new): Fix most bashisms (all that matter).
* Drop no_openssl.dpatch and build ultravnc_dsm_helper; OpenSSL
exception has been granted. Build-depend on libssl-dev.
* Promote stunnel4 from Recommends to Depends (Closes: #553411), depend
directly on openssl, depend on tk instead of tk8.4, and tweak java
recommendations.
* Add README.source.
* Bump Standards-Version to 3.8.3.
Checksums-Sha1:
319f4bf553db526cf62e4acea74911a541767ea9 1159 ssvnc_1.0.24-1.dsc
97a807eedef4556e51df9b9a4a116d98deb414c5 498389 ssvnc_1.0.24.orig.tar.gz
01feb6d45d3e2a5c0d311f619f9b47ae2c9bda6e 6928 ssvnc_1.0.24-1.diff.gz
9797b3c0e690de9362c619fdb91ac7cfb94422ab 575934 ssvnc_1.0.24-1_amd64.deb
Checksums-Sha256:
a9590dc69acb757ba2c4c2c59169e27e1d394f631aaca1dd4ed6dce3eac08d77 1159
ssvnc_1.0.24-1.dsc
25b66f7e9a7738628f014e3f0a136a561306d019470bf8cee094a62382239eba 498389
ssvnc_1.0.24.orig.tar.gz
7308e2a0754db1e9b4bafe8b709d03e99709172f261427f2edef0b1d6bd82eb4 6928
ssvnc_1.0.24-1.diff.gz
445db7472ed5fe6b9f5d497ce750e3723077d4dd48a525b91f168c950b8fdf64 575934
ssvnc_1.0.24-1_amd64.deb
Files:
547ee74b991f72899706fb853de2a467 1159 net extra ssvnc_1.0.24-1.dsc
a8e7ff94d7fbb45f8dac098c1230f10c 498389 net extra ssvnc_1.0.24.orig.tar.gz
650270e4e1de1f99503f7311e707516e 6928 net extra ssvnc_1.0.24-1.diff.gz
addfe8ed3c6e839e683e1fe327a4b7df 575934 net extra ssvnc_1.0.24-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkrsnTkACgkQk7mRNn1h4+bKoACgz1Lnh+7RFfd6mY/sfBPoz9zr
yaEAn10Cfp1BtvlnY75Jw7v1dtkBqBFJ
=fWau
-----END PGP SIGNATURE-----
--- End Message ---
