[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-talk] Why is 'Wgm' (middle-relay-for-guard weight) not zero?
Just scanned through all the material and did find anything that directly discusses the question:
_specifically_ why is the weight of middle relays for USE AS A GUARD not zero? The 'Wgm' parameter is described as
Wgm - Weight for non-flagged nodes in the guard Position
The fix for bug #17772 causes the guard selection logic to skip over non-guard relays in the set of candidates. I have not reviewed the code in detail, but presumably that set of guard candidates is assembled using the weights published under 'bandwidth-weights' in the hourly consensus document applied to the consensus weights of available relays. Thus the set of guard candidates would consist of about 50% guard-flagged relays and 50% unflagged relays.
One possibility that comes to mind is that the client logic may drop pre-existing guards that have a zero guard probability. It's apparent from various discussions that the preference is for clients to retain as guards, relays that have lost the guard flag so long as they remain useable.
If the client code behaves as such it means that, due to Wgd=0, clients will immediately drop any guard that transitions to operation as an exit.
At 03:14 12/15/2015 +0100, you wrote:
>to your text
>> it seems that middle relays have a weight equal to guard
>relays when guard selection occurs [...]
>> ... understand the purpose
>there are several possible answers for such a purpose
>Improving Tor's anonymity by changing guard parameters
>On the Effectiveness of Traffic Analysis Against Anonymity
>Networks Using Flow Records
>to your subject
>" For all circuits, we weight node selection according to
>if a node's weight is zero there might be not enough router
>bandwidth for (another) Tor user
>you don't want to be the only Tor user who isn't squeezed out of
>this circuit and have to remain for a deanonymization attack
tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx
To unsubscribe or change other settings go to