On Thu, Jul 5, 2018 at 7:47 PM, Nick Mathewson wrote:
> Hello, friends!
Oh no! I hit send too early. More info follows below.
> For quite a while now, the program "tor" has been built from source
> code in just two directories: src/common and src/or.
>
> This has become more-or-less untenable,
Hello, friends!
For quite a while now, the program "tor" has been built from source
code in just two directories: src/common and src/or.
This has become more-or-less untenable, for a few reasons -- most
notably of which is that it has led our code to become more
spaghetti-ish than I can endorse w
> On 5 Jul 2018, at 20:06, nusenu wrote:
>
> Roger Dingledine:
>> It looks like around 844 Guard relays are listening on port 443 right now,
>> out of the 1858 available Guard relays.
>
> guard probability for all guards having ORPort on 80 or 443:
> 45.99%
>
> guard probability per ORPort:
>
Roger Dingledine:
> It looks like around 844 Guard relays are listening on port 443 right now,
> out of the 1858 available Guard relays.
guard probability for all guards having ORPort on 80 or 443:
45.99%
guard probability per ORPort:
+-+---+
| or_port | guard_probabil
No problems here, and if tor handles blocked ports and port blocking
firewalls without issue then it's not something to worry about. But it
might not hurt to have a text box explaining this for those who are
concerned about what ports they are using.
On Thu, Jul 5, 2018 at 12:14 AM Roger Dingledi
On Wed, Jul 04, 2018 at 11:20:31PM -0700, Keifer Bly wrote:
> So tor will automatically use port 80 or 443 if Those are the only ones open?
Tor will choose Guard relays at random until one of them works(*).
It looks like around 844 Guard relays are listening on port 443 right now,
out of the 1858