>> The introduction points are not chosen by calculating the descriptor-id
>> and finding the 3 HSDirs next to it (by sorted fingerprint).
>
> tldr: HSDir != IntroPoint.
>
> Introduction points are chosen by random by an onion service and unknown
> in advance. What is known in advance is only
On Thu, Mar 02, 2017 at 01:11:00PM +, nusenu wrote:
> nusenu:
> > 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:
> >
> >
nusenu:
>
>
> Ivan Markin:
>> On Tue, Feb 28, 2017 at 02:09:00AM +, 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
Ivan Markin:
> On Tue, Feb 28, 2017 at 02:09:00AM +, 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
On Tue, Feb 28, 2017 at 02:09:00AM +, 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
nusenu:
>>> 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
>> 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
