Installed fetchmail-ssl 5.9.5-1 (i386 source)

[Henrique de Moraes Holschuh <hmh@debian.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat, 10 Nov 2001 11:32:14 -0200
Source: fetchmail-ssl
Binary: fetchmail-ssl
Architecture: source i386
Version: 5.9.5-1
Distribution: unstable
Urgency: low
Maintainer: Henrique de Moraes Holschuh <hmh@debian.org>
Changed-By: Henrique de Moraes Holschuh <hmh@debian.org>
Description: 
 fetchmail-ssl - SSL-enabled POP3, APOP, IMAP mail gatherer/forwarder
Changes: 
 fetchmail-ssl (5.9.5-1) unstable; urgency=low
 .
   * Auto-generated from the respective fetchmail package
   * The "Very dark skies ahead" release
   * Enjoy NLS while it lasts. Upstream may drop it in the close future,
     and I am not sure I will keep it alive in a Debian fork (I will certainly
     try, however)
   * New upstream source:
     + Finished license cleanup, all licenses in the distribution are now
       officially GPL-compatible.
     + Added a length check to from64tobits() after receiving a warning that
       it might create buffer overflows.  No exploitable overflows were found
       by a careful case-by-case audit, and at minimum an exploit would have
       required that the mailserver be subverted
     + Changed the logging logic along lines suggested by Jan Klaverstijn
     + fetchmailconf looks first in the directory it's running from to find
       fetchmail
     + Make sure we vet a success status correctly from open_smtp_sink()
       and open_bsmtp_sink()
     + Immediately abort if a non-empty QMAILINJECT environment variable is
       found. If it is set and contains f or i, qmail-inject or qmail's
       sendmail `compatibility' wrapper will rewrite From: or Message-ID:
       headers, respectively. En passant, fix the bug that program_name was not
       filled in before used when the user's ID had no PW entry, leading to
       (null) or crash when printing the error message. Patch by Matthias
       Andree
     + Block signals during SockConnect() so we don't get a socket descriptor
       leak if we're hit by an alarm signal during connect(2)
     + Set queryname even when server is inactive; avoids a core-dump bug in
       the fetchids code
   * Add -tt option to strace in the init.d debug-run debug helper
   * Fix all calls to from64tobits so that fetchmail will actually compile,
     I have no idea how it is compiling upstream without this. Maybe my CVS
     tree is weird... oh well, I am using the non-exploitable version, so
     I could care less :P
   * Do not run config.guess anymore, trust output of dpkg-architecture
   * Update fetchmailconf dependency list for the python 2.1 changes
Files: 
 e99451c4257dfe2c7b1a9548b832fd6f 751 non-US optional fetchmail-ssl_5.9.5-1.dsc
 73511862bdec5648e66e1937c311cae0 865980 non-US optional fetchmail-ssl_5.9.5.orig.tar.gz
 f5dd40ec64ee2a41c4e288732b3f3584 322754 non-US optional fetchmail-ssl_5.9.5-1.diff.gz
 ead4a93490d8f0777b72368d098e00f5 383532 non-US optional fetchmail-ssl_5.9.5-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjvtL6cACgkQ7iXePxzbD+MHTwCfdPYRPbZ3ej3pJXGl2qy3sEP1
Z3sAni4WXGIIYiAAtExFgA9cFT2R49R6
=C74E
-----END PGP SIGNATURE-----


Installed:
fetchmail-ssl_5.9.5-1.diff.gz
  to pool/non-US/main/f/fetchmail-ssl/fetchmail-ssl_5.9.5-1.diff.gz
fetchmail-ssl_5.9.5.orig.tar.gz
  to pool/non-US/main/f/fetchmail-ssl/fetchmail-ssl_5.9.5.orig.tar.gz
fetchmail-ssl_5.9.5-1.dsc
  to pool/non-US/main/f/fetchmail-ssl/fetchmail-ssl_5.9.5-1.dsc
fetchmail-ssl_5.9.5-1_i386.deb
  to pool/non-US/main/f/fetchmail-ssl/fetchmail-ssl_5.9.5-1_i386.deb