-
stunnel4 (3:4.18-2) unstable; urgency=low
* Updated chroot default path in configuration file
* Added LSB section in init script
-- Ubuntu Archive Auto-Sync <email address hidden> Thu, 09 Nov 2006 17:51:58 +0000
-
stunnel4 (3:4.18-1) unstable; urgency=low
* New upstream release
stunnel4 (3:4.17-2) unstable; urgency=low
* Check if pids are valid before trying to use kill
(Closes: #388379)
stunnel4 (3:4.17-1) unstable; urgency=low
* New upstream release
stunnel4 (3:4.16-1) unstable; urgency=low
* New upstream release
-- Ubuntu Archive Auto-Sync <email address hidden> Wed, 08 Nov 2006 19:44:01 +0000
-
stunnel4 (2:4.150-7) unstable; urgency=low
* Fixed a bug when pid is not given in configuration file :
init.d script was looking for /var/run/stunnel4/stunnel4.pid but
stunnel was creating /var/run/stunnel4.pid
(Closes: #384275)
* Added check during start to encourage users to fill the pid= section
of configuration file when start failed (for example if you use two
configuration files without pid= option)
stunnel4 (2:4.150-6) unstable; urgency=low
* Updated to debian policy 3.7.2
* Fixed lintian warnings
stunnel4 (2:4.150-5) unstable; urgency=low
* Fixed typo in postinst :
/var/lib/stunnel4/stunnel.log instead of /var/log/stunnel4/stunnel.org
(Closes: #381127)
stunnel4 (2:4.150-4) unstable; urgency=low
* Create /var/lib/stunnel4 if it does not exist in postinst
(Closes: #377074)
stunnel4 (2:4.150-3) unstable; urgency=low
* Fixed another problem with stunnel3 compatibility script
(call to /usr/sbin/stunnel4 instead of /usr/bin/stunnel4) and added
a check in debian/rules (Closes: #340113)
stunnel4 (2:4.150-2) unstable; urgency=low
* Fixed stunnel3 compatibility script problem (infinite loop)
Thanks to "Martin Schwenke" <email address hidden> for bug report.
* Added a check in debian/rules to ensure that stunnel3 compatibility script
does not contains infinite loop
stunnel4 (2:4.150-1) unstable; urgency=low
* New upstream release
stunnel4 (2:4.140-6) unstable; urgency=low
* Added check/creation of /var/run/stunnel4 directory in init.d script instead of
postinst in order to be FHS compliant when /var/run is cleared at startup
(note that /var/run/stunnel4 cleanup does not allow to have a chroot
in /var/run/stunnel4)
Thanks to Jim Helm : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343882;msg=25
-- Barry deFreese <email address hidden> Tue, 29 Aug 2006 19:36:01 +0100
