Opened 14 years ago

#255 closed defect (Won't implement)

TorCP doesn't use 'ControlPort' setting in torrc

Reported by: imIts Owned by:
Priority: Low Milestone:
Component: Tor - Tor Control Panel Version: 0.1.0.16
Severity: Keywords:
Cc: imIts Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

TorCP (under Windows XP SP2) doesn't use the 'ControlPort' setting from torrc.

Even after 'ControlPort' setting has been changed in torrc, TorCP still uses the Control Port setting listed
under the General settings tab to override it.

While this isn't a showstopper - it is weird (and annoying) behaviour. TorCP should either updated torrc to reflect the
General tab setting or use the torrc setting to update the General tab setting.

[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]

Child Tickets

Change History (1)

comment:1 Changed 14 years ago by edmanm

flyspray2trac: bug closed.
Reading the ControlPort value from the torrc means having the controller parse the user's torrc file. Realistically, the user shouldn't be manually editing their torrc, but rather using the controller to configure their Tor. So, having the controller parse the torrc itself is a road I don't see much value (or sanity) in going down.

Note: See TracTickets for help on using tickets.