[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #2403 [Tor Client]: Tor can choose a relay as both entry and exit node for a circuit
#2403: Tor can choose a relay as both entry and exit node for a circuit
------------------------+---------------------------------------------------
Reporter: rransom | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Tor Client | Version:
Keywords: | Parent:
------------------------+---------------------------------------------------
> 2011-01-17 02:28 <piebeer> Every time when i'm going to remove
"consider_exit_family = 0; goto retry;" for choose_random_entry(), I
thoung that it's something wrong with me, not with a func. Till today. I
found reason why that with "smartlist_add(exit_family, chosen_exit)" is a
fail.
> 2011-01-17 02:28 <piebeer> "EntryNodes"+"StrictEntryNodes" is non
recomended, so we can ignore such case. Bridge that has allowed exit
policy is a bug, so we can ignore that too.
> 2011-01-17 02:29 <piebeer> But. We have a 1776 that allowed to use any
guard as bridge. for some time exit relay can be guard.
> 2011-01-17 03:25 <piebeer> Hi. What can I do if circuit have the first
node the same as the last node?
> 2011-01-17 03:48 <piebeer> I'm sure: 1. used entrynodes+strict*nodes
(why need it allowed if it danger) 2. bridge addr_of_fast_relay (it's exit
too)
> 2011-01-17 04:17 <piebeer> "then be flexible about families" and chosen
exit. Better to have every build try to success and if
choose_random_entry() returned chosen_exit so what, it's a price for
success.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2403>
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