While testing my torrc with 0.2.3.18-rc, I tried adding the IsolateDestAddr flag to the SocksPort line, as in
SocksPort 9050 IsolateDestAddr
A "tor --verify-config" claimed that I was trying to specify more than one port on that line, which would be an error. Are the SocksPort flags listed in the tor man page for 0.2.3.18-rc not yet implemented?
Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at cs.niu.edu * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************
On Sun, Jul 8, 2012 at 4:19 AM, Scott Bennett bennett@cs.niu.edu wrote:
While testing my torrc with 0.2.3.18-rc, I tried adding the
IsolateDestAddr flag to the SocksPort line, as in
SocksPort 9050 IsolateDestAddr
A "tor --verify-config" claimed that I was trying to specify more than one port on that line, which would be an error. Are the SocksPort flags listed in the tor man page for 0.2.3.18-rc not yet implemented?
Just tried it with 0.2.3.18-rc (as tagged in git), using only that option. It worked for me. Could you have had some other tor in your path as "tor", or something like that?
yrs,
On 7/11/12 5:33 PM, Nick Mathewson wrote:
On Sun, Jul 8, 2012 at 4:19 AM, Scott Bennett bennett@cs.niu.edu wrote:
While testing my torrc with 0.2.3.18-rc, I tried adding the
IsolateDestAddr flag to the SocksPort line, as in
SocksPort 9050 IsolateDestAddr
A "tor --verify-config" claimed that I was trying to specify more than one port on that line, which would be an error. Are the SocksPort flags listed in the tor man page for 0.2.3.18-rc not yet implemented?
Just tried it with 0.2.3.18-rc (as tagged in git), using only that option. It worked for me. Could you have had some other tor in your path as "tor", or something like that?
Does this flag apply also for connections going to Tor HS?
-naif
tor-relays@lists.torproject.org