#20761: Tor Browser 6.5a4 is ignoring additional SocksPorts ---------------------------------------+----------------------------------- Reporter: gk | Owner: brade Type: defect | Status: needs_information Priority: Medium | Milestone: Component: Applications/Tor Launcher | Version: Severity: Normal | Resolution: Keywords: TorBrowserTeam201612 | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: ---------------------------------------+-----------------------------------
Comment (by arthuredelstein): Replying to [comment:8 mcs]: > > It seems clear we don't want to save an ephemeral `SocksPort /one/time/path` line to the torrc file. So I suppose one (somewhat awkward) option, instead of using `SAVECONF`, would be to load the settings into a string using `GETINFO CONFIG-TEXT`, remove the line with the unix-domain SocksPort (that was created for this session only), and then write the torrc file directly from JavaScript. > > That is an interesting idea but possibly fragile, since it might be tricky to figure out for sure which lines to filter out before rewriting torrc. Kathy and I will think about this a little more. Because you know the domain socket path (in `socksPortInfo.ipcFile`), I think you can use an exact match to filter that line out. One alternative solution would be to remove old unix-domain SocksPort settings from the config settings before you issue `saveconfig`. You could read them all in using `getconf socksport` and then set all but the obsolete ones using `setconf socksport a socksport b` again. There would need to be a way to distinguish obsolete Tor Launcher SocksPorts from user-added SocksPorts, however, which might be difficult. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20761#comment:10> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs