[tor-bugs] #29989 [Core Tor/Tor]: Add a flag to set chosen_exit_optional to false for MapAddress torrc option (and controller?)

[Tor Bug Tracker & Wiki]

#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):

 >We'll need to see your tor logs to work out what's going on here.

 Which logs do you need and where are they located?


 > The most likely explanations are:
 > * you have an unreliable network connection,
 Nope. Not sure why that would even come up given the detailed explanation
 I provided above.

 > * ayefiles.com blocks many tor exits, or
 > * many tor exits block ayefiles.com.
 These don't make sense either.  As I explained, I connected to ayefiles,
 rotated the connection and wrote down three exit nodes that were actually
 reported as being used.  I then set those same exit nodes (via
 fingerprint) as MapAddress targets (sequentially in time, not at the same
 time) and they failed.

 So they were obviously not blocked by ayefiles since I was connected to
 ayefiles using those exit nodes.  However, setting them manually, then
 prevents any connection.  So as I said above, something is allowing those
 exit nodes when ayefiles picks them, but not when I pick them.  How is
 that OK?  Can we stop it?

 Also, why would using one those nodes, which are listed as official exit
 nodes, block duckduckgo connections?  Are people who run exit nodes free
 to block any websites they want, even useful and innocuous ones like
 duckduckduckgo? Why?  Seems like you need to upgrade your terms of service
 (or whatever agreement they explicitly or implicitly adopt to run an exit
 node) to prevent these games.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29989#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online