Re: [tor-dev] "identity digest" and "hash of a router's identity key"

[Frank Young <pfcodes@xxxxxxxxx>]

Yes you are right, after decoding that value from base64 and
re-encoding it in base16, it can be used to get the router's
descriptor.
What i'm trying to get is the list of HSDIR responsible for a hidden service.
After calculating the descriptor for the hidden service, i need to
know the identity digest of all the HSDIR in the consensus, so that i
can sort them and get the three which are responsible for the
descriptor id.
I base64 decoded the digest fields of HSDIR in the consensus and
assume those are the identity digest which i can sort.
I'm i correct?


On 4/27/13, Damian Johnson <atagar@xxxxxxxxxxxxxx> wrote:
>> In a consensus, the item after nickname is  base64 encoded "hash of a
>> router's identity key"
>> If this item is base64 decoded, is it the same as the "identity
>> digest" of the router?
>
> Hi Frank. That field is the relay's fingerprint. Here's the code stem
> uses for parsing that line...
>
> https://gitweb.torproject.org/stem.git/blob/HEAD:/stem/descriptor/router_status_entry.py#l469
> _______________________________________________
> tor-dev mailing list
> tor-dev@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
>
_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev