[tor-bugs] #21415 [Core Tor/Tor]: tor_bug_occurred_: Bug: src/or/entrynodes.c:1845: select_entry_guard_for_circuit: Non-fatal assertion !(!guard_has_descriptor(guard)) failed.

[Tor Bug Tracker & Wiki]

#21415: tor_bug_occurred_: Bug: src/or/entrynodes.c:1845:
select_entry_guard_for_circuit: Non-fatal assertion
!(!guard_has_descriptor(guard)) failed.
-----------------------------+------------------------------------
 Reporter:  cypherpunks      |          Owner:  nickm
     Type:  defect           |         Status:  reopened
 Priority:  Medium           |      Milestone:  Tor: 0.3.0.x-final
Component:  Core Tor/Tor     |        Version:  Tor: 0.3.0.3-alpha
 Severity:  Normal           |     Resolution:
 Keywords:  review-group-16  |  Actual Points:
Parent ID:                   |         Points:
 Reviewer:  asn              |        Sponsor:
-----------------------------+------------------------------------

Comment (by asn):

 Some thoughts forward:

 a) Should Tor create two entry guard entries for this bridge at `[::1]`
 and `127.0.0.1`? I say probably yes.

 b) However, we can't expect the bridge two create two descriptors, right?
 So maybe Tor should accept that bridge descriptor and assign it to both
 entry guard entries? Instead of rejecting it because "we already have" it?

 c) If the test is ipv6-only and the bridge is only configured as ipv6, why
 does the client prefer the ipv4 address of the bridge? That's regarding
 `[notice] Bridge 'test003br' has both an IPv4 and an IPv6 address.  Will
 prefer using its IPv4 address (127.0.0.1:5003) based on the configured
 Bridge address.`

 What else is going weird in this test?

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