Opened 9 years ago

Closed 4 years ago

#2351 closed defect (wontfix)

polipo-1.0.4.1 logs port 2050 instead of 8118

Reported by: jchau Owned by:
Priority: Medium Milestone:
Component: Polipo Version: Polipo: 1.0
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I am using net-proxy/polipo-1.0.4.1 with net-misc/tor-0.2.1.28 on Gentoo Linux.

I configured polipo with the configuration file from <https://gitweb.torproject.org/torbrowser.git/blob_plain/HEAD:/build-scripts/config/polipo.conf> with the following modifications, which enable logging and enables cachedIsShared:
0a1,4

# Taken from <https://gitweb.torproject.org/torbrowser.git/blob_plain/HEAD:/build-scripts/config/polipo.conf>
# (for use with Tor)
# Modified by Jimmy C. Chau 2010 Jan 05

3a8,11

# Add logging to syslog
logSyslog = true
logLevel = 0xFF

29c37
< cacheIsShared = false
---

cacheIsShared = yes

When I start polipo, it consistently logs the following (regardless of whether I start polipo as myself (using the command "polipo" without arguments) or use the init.d script to start it as user polipo):
Established listening socket on port 2050.

This is problematic because I have not configured polipo to use port 2050 for anything. As shown below, I don't ever mention 2050. Below is the output of "polipo -v | grep -i port":
allowedPorts intlist 1-65535 Ports to which connections are allowed.
parentProxy atom (none) Parent proxy (host:port).
proxyPort integer 8118 The TCP port on which the proxy listens.
socksParentProxy atom localhost:9050 SOCKS parent proxy (host:port)
tunnelAllowedPorts intlist 1-65535 Ports to which tunnelled connections are allowed.

Furthermore, I can't find any open port 2050 open on my computer; "netstat -n -l" shows:
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8118 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN
udp 0 0 0.0.0.0:631 0.0.0.0:*

(Listing of UNIX domain sockets follow, but no 2050 shows there either.)

Tor with Torbutton appears to work properly despite this polipo claiming to use port 2050. Still, this confusing log message makes me think that something is wrong.

I tried looking at the polipo source, but I still can't figure out why it would output 2050. Does anyone else notice this?

Attached is /etc/polipo/config.

Child Tickets

Attachments (1)

config (4.0 KB) - added by jchau 9 years ago.
/etc/polipo/config: configuration file used by polipo

Download all attachments as: .zip

Change History (3)

Changed 9 years ago by jchau

Attachment: config added

/etc/polipo/config: configuration file used by polipo

comment:1 Changed 8 years ago by phobos

Resolution: wontfix

Polipo bugs should be opened at http://sourceforge.net/projects/polipo/

comment:2 Changed 4 years ago by arma

Severity: Normal
Status: newclosed

(Somehow Andrew managed to set the ticket to wontfix without actually closing it? Nice. Now closing.)

Note: See TracTickets for help on using tickets.