I've been experimenting with a private tor setup - I've managed to setup a
couple directory authorities, six routers/exit nodes (which seemed to be
the minimum to bootstrap everything), and a client. Its a pretty normal
setup (aside from everything running on my development box) and passes
traffic
On Mon, Apr 20, 2015 at 03:18:06PM -0400, A. Johnson wrote:
I think new users might not appreciate the difference between similarly
named terms and then choose the wrong one to their detriment. It seems
better that they should later learn of shared technology that's not clear
from the
Date: Tue, 21 Apr 2015 02:13:48 -0400
From: CJ Ess zxcvbn4...@gmail.com
I've been experimenting with a private tor setup - I've managed to setup a
couple directory authorities, six routers/exit nodes (which seemed to be
the minimum to bootstrap everything), and a client.
With the latest
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Improved documentation and process of setting up Onionoo would be
welcomed by more people, including myself. Busy setting up Compass and
with Atlas and Globe mirrors active the cherry on the pie would be an
own Onionoo instance (if needed also as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Karsten,
Though it's very likely easier to parse those directly (possibly
using Stem) rather than setting up an Onionoo instance for the
exact time you're interested in.
can you say something about what amount of minimal memory and disk
Chutney sounds really cool, but this is more of a learning exercise so I'll
keep at it manually for a bit.
I read someplace that test instances on the public tor are near useless,
so I tried setting TestingTorNetwork 0 on all he routers and one of the
directory servers in case there was some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/04/15 22:06, nusenu wrote:
Hi Karsten,
Though it's very likely easier to parse those directly (possibly
using Stem) rather than setting up an Onionoo instance for the
exact time you're interested in.
can you say something about what
