[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #1776 [Tor]: Allow regular relays (if they have a dirport open) to be used as bridges
#1776: Allow regular relays (if they have a dirport open) to be used as bridges
-------------------------+-------------------------------------------------
Reporter: | Owner: asn
Sebastian | Status: closed
Type: defect | Milestone: Tor: 0.2.6.x-final
Priority: major | Version:
Component: Tor | Keywords: regression crash tor-bridge
Resolution: fixed | 026-triaged-1
Actual Points: | Parent ID:
Points: |
-------------------------+-------------------------------------------------
Changes (by isis):
* cc: isis (added)
Comment:
I have suspected that #11301 is due to normal relays getting used as
"bridges", and they appear to jump from the `bridge_list` in entryguards.c
to the normal routerlist, possibly when `entry_guards_compute_status()` is
called, when it's discovered that the chosen "bridges" don't have
`ROUTER_PURPOSE_BRIDGE`. After that, there is a weird catch-22 state where
no DirectoryGuards exist
to fetch the other "bridge" descriptors, or something else that I'm not
sure about yet.
Arma also pointed out that #14216 could also be related to this behaviour
of sorting tables of routers, with different tables for each purpose, and
not allowing one router to exist in multiple tables simultaneously. Either
way, there are definitely still some bugs when using normal relays as
bridges.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1776#comment:85>
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