[tor-bugs] #11638 [Tor]: Backport raising of #9731 fixes.

[Tor Bug Tracker & Wiki]

#11638: Backport raising of #9731 fixes.
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:
  robgjansen             |     Status:  closed
         Type:  defect   |  Milestone:  Tor: 0.2.4.x-final
     Priority:  normal   |    Version:  Tor: 0.2.4.21
    Component:  Tor      |   Keywords:  tor-relay, shadow, infinite, loops,
   Resolution:  wontfix  |  arma-backport-02422
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+-------------------------------------------------

Comment (by robgjansen):

 Replying to [comment:16 arma]:
 > I talked to Rob about bootstrapping issues at PETS. We didn't get to the
 bottom of his questions. Rob, yes, sounds like a new ticket for that would
 be useful once you have details (including the debug logs from startup).
 >

 I discovered an --Address config error that was the cause of those
 problems. After setting the correct address of my node, everything worked
 swimmingly.

 > It sounds like we should close this ticket, since 0.2.5.x is what Shadow
 uses, and nobody else is encountering these problems in 0.2.4.x.
 >
 > Please reopen if I'm wrong.

 This decision means that no one will ever be able to experiment with
 0.2.4.x in Shadow. It's true that Shadow uses 0.2.5.x by default these
 days, but that doesn't mean that no one ever does research with older Tor
 versions. In fact, I recently told some researchers that they need to port
 their code from 0.2.4.x to 0.2.5.x because of the bug described in this
 ticket, and haven't heard from them since...

 I'm OK with not fixing it as long as we agree that its worth more to save
 the cost of fixing this than to obtain the ability to simulate 0.2.4.x.

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