[tor-relays] descriptor-id calc tool?

[nusenu]

Ivan Markin:
> On Tue, Feb 28, 2017 at 02:09:00AM +0000, nusenu wrote:
>>>> Is there a tool out there that tells me which HSDir is/will probably be
>>>> responsible for a given onion address (and at what time)?
>>>
>>> There's no tool, unless you can reverse SHA1.
>>> (Or brute-force a set of popular onion addresses.)
>>
>> I probably was not very clear in my question. I'm not aiming for the
>> reverse path, just the normal calculation a tor client does given an
>> onion address but instead of just calculating the current descriptor-id,
>> print descriptor-ids for the future N days for onion address M (for the
>> pre-prop224 world).
> 
> FYI https://gist.github.com/nogoegst/895dde228496e04f409fc6d160a5de5a
> 
> $ go run onion-desc-advance.go -time 1488288001 yrcfcqhja2ide7yh
> 
> prints descriptor IDs for the given time for replica #1 and #2.

Thanks for this.

Shouldn't the first 2 or 3 hex digits of your output (after converting
them to hex) without time option and the actual intro point FPs match
when run at roughly the same time?

example for duckduckgo:

./get-intro-points.py 3g2upl4pq6kufc4m  [1]
3g2upl4pq6kufc4m:56782537778BEFC5A48080B58BE01E814AF9B5D3
3g2upl4pq6kufc4m:769DBA4C0C992FCEA080618833FD7BF5AC1F4F41
3g2upl4pq6kufc4m:744B753C7F5E0C6BDD240EE5D879A36C650D2B00


go run descriptor-id-calc.go 3g2upl4pq6kufc4m
replica #0: sv5uuknuqvjgquf4hu4m6tvcyuyiyvw7
-> hex: 957B4A29B485526850BC3D38CF4EA2C5308C56DF

replica #1: crpc4lkarusgflm5nblslpopg5qpvw7i
-> hex: 145E2E2D408D2462AD9D685725BDCF3760FADBE8

they start with 95.. and 14.. but the actual intro points start with
56.., 76.. and 74.. ?

thanks

[1] https://gist.github.com/nusenu/8339cfd5351b64c47676241a40ee2942



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20170302/ec544c99/attachment.sig>