Package: privoxy
Version: 3.0.9-1
Severity: normal

By default on new debian installs, localhost is not 127.0.0.1, but
instead 127.0.1.1. [1]

Privoxy is configured to listen on 127.0.0.1 only, by default.

gnome-network-preferences has a proxy config that defaults to localhost
port 8118. 

So, a quick try at getting privoxy working with gnome will result in 
the web browser connecting to the wrong address, which privoxy is not
listening on.

Since there are still plenty of systems where localhost is 127.0.0.1
(old installs, manual hosts file edits, etc), changing the IP address
in the default config doesn't seem wise. Why not just configure it as
follows:

listen-address  localhost:8118

That seems to work ok.

-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.27-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages privoxy depends on:
ii  adduser                3.110             add and remove users and groups
ii  libc6                  2.7-18            GNU C Library: Shared libraries
ii  libpcre3               7.8-2             Perl 5 Compatible Regular Expressi
ii  logrotate              3.7.7-2           Log rotation utility
ii  zlib1g                 1:1.2.3.3.dfsg-12 compression library - runtime

Versions of packages privoxy recommends:
ii  doc-base                      0.8.19     utilities to manage online documen

privoxy suggests no packages.

-- no debconf information

-- 
see shy jo

[1] netcfg has done this since 2005

  * If there is no permanent IP address with which the system hostname
    (i.e., that which is returned by the "hostname" command) can be
    associated in /etc/hosts then associate it with address 127.0.1.1
    rather than 127.0.0.1.  Associating the system hostname with the
    latter had the unwanted effect of making 'localhost.localdomain'
    the canonical hostname associated with the system hostname.
    That is, 'hostname --fqdn' returned 'localhost.localdomain'.
    (Closes: #316099)
    Programs that access local services at the IP address obtained by
    resolving the system hostname SHOULD NOT DO THIS, but those that
    do so will not be disappointed: most services that listen locally
    listen on all 127/8 addresses, not just on 127.0.0.1.

Attachment: signature.asc
Description: Digital signature

Reply via email to