On Thu, 14 Aug 2014 23:25:46 +, Ben Healey wrote:
...
> When the key generator I've been trying produced an address 90% of the time
> the browser does nothing.
That has to do with the fact that each letter/digit represents
five bits, while a-z0-9 are 36 values, and so tor does not use
(afaik)
On Fri, Aug 15, 2014 at 5:07 AM, Ben Healey wrote:
> Below is they address changed into numbers.
> Letters changed into numbers starting with a-1 through z-26.
> The numbers are the numbers 1.2.3..
>
> I then added all them together.
>
> Then divided the totals by 2.
>
> Results:
> -
> 8 2
Message: 4
Date: Thu, 14 Aug 2014 21:07:30 -0600
From: Ben Healey
To: "tor-talk@lists.torproject.org"
Subject: [tor-talk] Pattern In Tor Addresses
Message-ID:
Content-Type: text/plain; charset="iso-8859-1"
Hello,
I started by trying to figure out tor(find websites and s
On 14/08/14 22:24, Drake Wilson wrote:
> You need more mathematics training, grasshopper. Almost all integers
> have that property (or all, if you don't halt upon reaching 1).
(Except zero, because I was originally thinking of positive naturals
and got it mixed up in editing. Wow, that's embarra
On 08/14/2014 09:07 PM, Ben Healey wrote:
> Hello,
>
> I started by trying to figure out tor(find websites and so on.)
> Noticed there are 16 keys per address. Almost all I've seen have at
> least 1 number.
>
> I then started generating keys. They were hit and miss to even try to
> connect.
>
>
On 14/08/14 22:07, Ben Healey wrote:
> Below is they address changed into numbers.
> Letters changed into numbers starting with a-1 through z-26.
> The numbers are the numbers 1.2.3..
>
> I then added all them together.
>
> Then divided the totals by 2.
>
> They all seem to at some point end
Hello,
I started by trying to figure out tor(find websites and so on.)
Noticed there are 16 keys per address.
Almost all I've seen have at least 1 number.
I then started generating keys. They were hit and miss to even try to connect.
I've now looked at the combinations of numbers and letters and
