Uploaded sslwrap 2.0.6-3.1 (m68k) to non-us
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sat, 17 Mar 2001 11:47:09 -0800
Source: sslwrap
Binary: sslwrap
Architecture: m68k
Version: 2.0.6-3.1
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon <buildd@kullervo.informatik.uni-erlangen.de>
Changed-By: Luca Filipozzi <lfilipoz@debian.org>
Description:
sslwrap - Simple TCP service encryption using TLS/SSL
Closes: 81562 81913 87350 87479 89403
Changes:
sslwrap (2.0.6-3.1) unstable; urgency=low
.
* Non-maintainer upload (closes 1 grave, 1 serious, and 3 normal bugs)
* debian/control: modified Build-Depends to use libssl-dev
* debian/control: removed openssl from sslwrap's Depends
* debian/rules: removed dh_suidregister (obsolete)
* debian/config: removed bashism
note: other bashisms appear to be fixed already (Closes: #87479)
* debian/postrm: /etc/sslwrap is removed on purge (Closes: #81562)
* debian/init & debian/postinst: moved some stuff from init to postinst
- the ssl certificate should only need to be (re)generated on configure
(i.e., the init script should not be creating the ssl certificate)
- the ssl certificate generated is valid for 365 day (Closes: #89403)
- the inetd.conf file should only need to be (re)populated on configure
(i.e., the init script should not be modifying /etc/inetd.conf)
the individual inetd entries are enabled|disabled by the init script
* debian/preinst: modified to handle the new templates file
* debian/template: question sslwrap/overwrite_corrupted_certfile changed from
a select to a boolean to facilitate in making sslwrap not abuse debconf
* debian/config: no longer abuses debconf (Closes: #87350)
* debian/conffiles: debian_config is no longer a conffile
* removed the maintainer's patch to s_server.c because start-stop-daemon
has enough features to handle the brokeness of the upstream code and
the maintainer's patch was somewhat broken
- the maintainer's patch caused sslwrap to generate a pidfile *before*
sslwrap tested if the port was already in use, which resulted in the
pidfile for the already running sslwrap to be overwritten!
- the maintainer's patch caused sslwrap to generate a pidfile;
start-stop-daemon has a --make-pidfile option for cases like these
- the maintainer's patch provided sslwrap with a signal handler but
start-stop-daemon can be told which signal to use (i.e., --signal 9)
- the maintainer's patch caused sslwrap to go into the background;
start-stop-daemon has a --background option for cases like these;
.
**** IMPORTANT NOTE **** (you should read the rest, too!)
NOTE: removing this patch has the implication that people who were calling
sslwrap directly (not via inetd or via the init script) will be required
to put the process in the background themselves using '&';
if this is a problem, the maintainer's patch, or portions thereof, can
be reapplied ... let me know
*** IMPORTANT NOTE ****
.
- the maintainer's patch is contained in debian/s_server.c.patch
* applied my own, very minor, patch, to s_server.c to deal with the fact
that the openssl library does not have the anonymous DH ciphers enabled
by default; sent the patch to the upstream author (Closes: #81913)
my patch is contained in debian/s_server.c.patch-lfilipoz
* only two problems remain:
1) the certificate file is not regenerated when debconf settings change
2) an init script shouldn't really be modifying inetd.conf, imo
Files:
58822d0ac149c73f44d9c336c62abee3 30070 non-US/main/net optional sslwrap_2.0.6-3.1_m68k.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard <http://www.gnupg.org/>
iEYEARECAAYFAjrIRNwACgkQcS3JWD3FdvdRgQCcCo/ZbSW2x7dtmcPYT8xJJqRW
qMQAn0IRxH71EUToh6fF7o0fVnJ6hXiB
=bA96
-----END PGP SIGNATURE-----
Reply to: