I've been running a relay on a Beaglebone black for about two weeks
now and I'm wondering where to take this thing. The Beaglebone black
is a 1GHz armhf System on a Chip, with 512 MB RAM. At the moment,
it's a dedicated relay running Ubuntu (raring) but Debian is equally
as easy to setup. I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/09/13 15:33, Lunar wrote:
> Ximin Luo:
>> I assume people will be interested in creating Debian packages for
>> these too. I am wondering if we should adopt a naming convention like
>> tor-pt-sshproxy, tor-pt-flashproxy, tor-pt-obfsproxy etc -
On Sun, Sep 8, 2013 at 10:12 PM, Nick Mathewson wrote:
>> $ time /tmp/fluxcapacitor/fluxcapacitor ./go.sh
>>
>> real0m11.450s
>> user0m2.340s
>> sys 0m2.120s
>>
>> Running stuff under fluxcapacitor is not deterministic, sometimes it
>> takes 8 seconds, sometimes 15 but it generally wor
On Sun, Sep 8, 2013 at 12:35 PM, Marek Majkowski wrote:
> Tor ships with some testing facilities (tor/src/test/test), but they
> are not comprehensive. (I'm aware there's an ongoing effort on
> improving these tests).
>
> To test anything non trivial it is necessary to run a tor node as a
> part
Marek Majkowski wrote
Sun, 8 Sep 2013 17:35:24 +0100:
| In past I wrote this thing called fluxcapacitor [3], it's a tool that
| speeds up tests. After a few fixes I was able to run chutney on it:
|
| $ time /tmp/fluxcapacitor/fluxcapacitor ./go.sh
|
| real0m11.450s
| user0m2.340s
| sys
George asked me for tips on testing flash proxy infrastructure.
You will need to run a websocket-server
(https://gitweb.torproject.org/flashproxy.git/tree/HEAD:/websocket-transport)
in front of a relay:
ServerTransportPlugin websocket exec /usr/local/bin/websocket-server
--port 9901
Or yo
Tor ships with some testing facilities (tor/src/test/test), but they
are not comprehensive. (I'm aware there's an ongoing effort on
improving these tests).
To test anything non trivial it is necessary to run a tor node as a
part of a tor network. There is another tool called chutney [1] that
can
Ximin Luo:
> I assume people will be interested in creating Debian packages for
> these too. I am wondering if we should adopt a naming convention like
> tor-pt-sshproxy, tor-pt-flashproxy, tor-pt-obfsproxy etc - like how
> mozilla extensions are all called xul-ext-*. (We could even start a
> worki
I assume people will be interested in creating Debian packages for these too. I
am wondering if we should adopt a naming convention like tor-pt-sshproxy,
tor-pt-flashproxy, tor-pt-obfsproxy etc - like how mozilla extensions are all
called xul-ext-*. (We could even start a working group too.)
AT