Ubuntu
ziproxy package

Fails to start when Address/OnlyFrom set in ziproxy.conf

Bug #569611 reported by Francisco Arteaga
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ziproxy (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: ziproxy

Simply uncommenting Address/OnlyFrom in /etc/ziproxy/ziproxy.conf results in failure to start claiming an invalid host name. Similarly if I set NextProxy/NextPort with with out the above being set results in "404" "Unknown host" error pages. I have apt-get purged and apt-get cleaned a few times and I get the same error. Looks like the config is getting mangled somehow but I can't figure out how.

<snip>
Address = "127.0.0.1"

## Accepts conections only from that address.
## WARNING: Remember to restrict the access to Ziproxy
## if your machine is directly connected to the Internet.
OnlyFrom = "127.0.0.1"
</snip>

$ sudo /etc/init.d/ziproxy start
Starting ziproxy: Invalid address or host name '127.00..1'

lsb_release -rd
Description: Ubuntu 10.04 LTS
Release: 10.04

apt-cache policy ziproxy
ziproxy:
  Installed: 2.7.2-1.1ubuntu1
  Candidate: 2.7.2-1.1ubuntu1
  Version table:
 *** 2.7.2-1.1ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/universe Packages
        100 /var/lib/dpkg/status

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ziproxy (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.