[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #21242 [Core Tor/Tor]: Start-up error
#21242: Start-up error
--------------------------+------------------------------------
Reporter: Felixix | Owner: asn
Type: defect | Status: assigned
Priority: Medium | Milestone: Tor: 0.3.0.x-final
Component: Core Tor/Tor | Version: Tor: 0.3.0.1-alpha
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------+------------------------------------
Comment (by nickm):
Hmmm. That does seem like a sensible analysis. I'll work through the
If we are using a guard in that branch, it came from
`choose_good_entry_server()`, which got it from `guards_choose_guard()` (I
assume. Unless this isn't using a guard, in which case it called
`router_choose_random_node()`.)
Now, `guards_choose_guard()` calls `entry_guard_pick_for_circuit()`, which
*should* yield a yields a negative result (and leave its `node_t **`
argument un-set) whenever node_get_by_id() fails. So we know that
node_get_by_id() returned a node_t for this node. So either we have a
descriptor for it, or we have a routerstatus entry for it. Let's assume we
have a routerstatus entry but no descriptor.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21242#comment:9>
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