Comment 1 for bug 569611

This bug was fixed in the package ziproxy - 3.1.3-1

---------------
ziproxy (3.1.3-1) unstable; urgency=low

  * New upstream release (LP: #569611)
  * debian/patches/02_ziproxy_3.1.1_speedup.diff
    - Removed, merged upstream.
  * debian/preinst
    - Removed, old command moved to postinst (Closes: #566589)
      - Thanks piuparts ;-)
  * debian/control
    - Standards-Version updated
  * Disabled Nameservers option (Closes: #591417) (LP: #539874)
    - Thanks to all in 591417@ and the upstream!
    - debian/README.Debian
      - Reason for it added.
    - New patch: debian/02_off_nameservers_opt.diff

ziproxy (3.1.1-1) unstable; urgency=low

  * New upstream release (Closes: #587039) [CVE-2010-2350]
    - Thanks to Moritz Muehlenhoff
  * debian/patches/02_ziproxy_genhtml_stats-bashism.diff
    - Removed, merged upstream.
  * debian/control
    - Renamed Vcs* address
  * debian/patches/02_ziproxy_3.1.1_speedup.diff
    - New patch for fix CPU load problem
  * debian/ziproxy.init
    - Removed $local_fs from Required-{Start,Stop}

ziproxy (3.1.0-1) unstable; urgency=low

  * New upstream release (LP: #569611) (Closes: #584933) [CVE-2010-1513]
  * Fixed bashisms in ziproxy_genhtml_stats.sh (Closes: #581153)
    - Thanks to Raphael Geissert.
  * Updated debian/copyright
  * debian/ziproxy.init:
    - Added Required-* $remote_fs
    - Now using pidfile option from daemon
  * User/group name now in debian/ziproxy.default
  * Removed patch for Russian man page
    - Upstream removed Russian man pages due to lack of maintainer
  * config.* is now updating with debhelper
  * Changed maintainer mail
 -- David Sugar <email address hidden> Fri, 22 Oct 2010 15:36:55 +0000