Opened 11 years ago

Closed 11 months ago

#952 closed defect (wontfix)

Torbutton does not block access to non-default Tor-related ports

Reported by: keb Owned by:
Priority: Medium Milestone:
Component: Applications/Torbutton Version: 1.2.0
Severity: Normal Keywords:
Cc: keb, arma, mikeperry, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by gk)

https://www.torproject.org/torbutton/design/
The 3.1 Browser overlay section on network.security.ports.banned
assumes that no one changes the default ports.
The tor(1) man page and config documentation on the website
gives those values as defaults but does not warn users about
a torbutton dependency.
Is there a way to have torbutton check (perhaps only on install)
that the ports are as expected?

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (4)

comment:1 Changed 11 years ago by keb

i just noticed section 5.1 which tests proxy settings.
oops

comment:2 Changed 8 years ago by rransom

Priority: minornormal
Summary: default network.security.ports.bannedTorbutton does not block access to non-default Tor-related ports
Type: enhancementdefect

As of commit 77193828ed6d4ab7749bb61b10df4bf628155ecd (current Git master), Torbutton still does not adjust network.security.ports.banned or extensions.torbutton.banned_ports to include the user's Tor proxy ports if they are not in the default ‘banned’ port list.

comment:3 Changed 22 months ago by teor

Cc: keb,arma,mikeperry,nickmkeb, arma, mikeperry, nickm
Severity: Normal

Set all open tickets without a severity to "Normal"

comment:4 Changed 11 months ago by gk

Description: modified (diff)
Resolution: Nonewontfix
Status: newclosed

Bug from the toggle area. The functionality is long gone from Torbutton.

Note: See TracTickets for help on using tickets.