[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #29989 [Core Tor/Tor]: Add a flag to set chosen_exit_optional to false for MapAddress torrc option (and controller?)
#29989: Add a flag to set chosen_exit_optional to false for MapAddress torrc option
(and controller?)
-------------------------------------------------+-------------------------
Reporter: babyfarkmcgeezaxxon | Owner: (none)
Type: enhancement | Status: new
Priority: Medium | Milestone: Tor:
| unspecified
Component: Core Tor/Tor | Version: Tor:
| 0.3.5.8
Severity: Normal | Resolution:
Keywords: security-low?, tor-client, tor-exit | Actual Points:
Parent ID: | Points: 1
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by babyfarkmcgeezaxxon):
Bypassing exitnodes to access DDG isn't the goal. I was just using it as
an example.
I make a living fixing bugs. We don't require a stack trace unless we are
having trouble reproducing the issue. In this case, have TOR devs made
any attempt to reproduce it? I suspect it's very easily reproducible
using the instructions I gave.
Why can't I manually specify an exit node that was selected by ayefiles?
We know those nodes are allowed to connect to ayefiles. What is going on
here? This seems like a serious issue, but no TOR dev is responding to
it?
What I'm not understanding is TOR must be involved in the selection of the
exitnode, so how does ayefiles allow a particular node when it picks it,
but not when I select it? And how is it "picking it" in the first place?
This is very maddening that I can't force the use of the very exit node
that I saw a website using.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29989#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs