> [...]
>> Maybe there is no automated testing for any Tor projects? At least a
>> quick search on the wiki only found [1] which lists possible ways to
>> test (but was created 7 months ago and apparently not updated since
>> and collecting dust) and [2] discussing a manual test procedure for
>> T
> I also have had success in using the following:
> ControlListenAddress 127.0.0.1:9051
> Which binds the control port to 127.0.0.1 (localhost) and is thus not
> visible to the outside world.
> (Including the people on the internet port scan you just for running a Tor
> node.)
Or set 'ControlPort
nning bigger networks, but I think that here they might not be
> needed, since their focus seems to be on performance measurement.
> Chutney is enough for basic integration testing, and has the advantage
> that it's running unmodified Tor binaries. Stem is interesting here
> to
Hi,
Just thought I would follow up on this.
Arm is a neat tool which allows 'top'-like output on a tor relay, current
bandwith, cpu utilization, connections to other relays etc.
This dose require the control-port to be enabled in your torrc file. eg:
## The port on which Tor will listen for lo
re
too, since it exercises Tor's control port protocol pretty heavily.)
I've uploaded the gcov output for running the unit tests, then running
chutney with the networks/basic configuration, at
http://www.wangafu.net/~nickm/volatile/gcov-20121219.tar.xz .
(Warning, evil archive file! It will
On Wed, Dec 19, 2012 at 1:49 PM, Nick Mathewson wrote:
> On Wed, Dec 19, 2012 at 2:29 PM, Simon wrote:
> [...]
>> Tor seems to have good planning compared to most open source projects.
>> So I would be interested in hearing why testing is apparently 'falling
>> between the cracks'. Why isn't the
On Tue, Dec 18, 2012 at 7:07 PM, Philipp Winter
wrote:
> Hi there,
Hi Philipp,
> Deliverable 6 for sponsor Z says:
>
>> 6. Start a tool that a censored developer can run to discover why their Tor
>> is
>> failing to connect: brainstorm a list of "things to check", and sort them by
>> how useful
On Wed, Dec 19, 2012 at 2:29 PM, Simon wrote:
[...]
> Maybe there is no automated testing for any Tor projects? At least a
> quick search on the wiki only found [1] which lists possible ways to
> test (but was created 7 months ago and apparently not updated since
> and collecting dust) and [2] di
On Wed, Dec 19, 2012 at 5:20 AM, George Kadianakis wrote:
> Philipp Winter writes:
>
>> Hi there,
>>
>> Deliverable 6 for sponsor Z says:
>>
>>> 6. Start a tool that a censored developer can run to discover why their Tor
>>> is
>>> failing to connect: brainstorm a list of "things to check", and
Philipp Winter writes:
> Hi there,
>
> Deliverable 6 for sponsor Z says:
>
>> 6. Start a tool that a censored developer can run to discover why their Tor
>> is
>> failing to connect: brainstorm a list of "things to check", and sort them by
>> how useful they'd be to check / how hard they'd be to
10 matches
Mail list logo
