-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>
> If you can read Python and shell script, then checking I haven't made
any obvious coding errors in my changes would help. But that might
require becoming familiar with the codebase - which may take some effort.
>
> The diffs are here, or you can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>
> Well, you could test my latest branches for #14175:
Hey Tim, I got the branch of chutney and tor and made sure that the
commands you run in the comments of the issue exist. What do you think
would be a good way to start testing? Begin with a sta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Well, you could test my latest branches for #14175:
>
> https://trac.torproject.org/projects/tor/ticket/14175#comment:8
>
> There's a branch which modifies src/test/test-network.sh in tor,
> and another with the performance measurement code in chut
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>
> Well, your ideal scenario is a separate box / VM, with at least 2
separate cores, for each of the tor instances you're pushing data
through (2-3 with a path length of 1, 4-5 with a path length of 3, as
you'll need to account for cannibalization).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>
> Yes, and testing locally gives you much better control of all the
factors which affect performance.
>
Can I set everything up using vm's or maybe just a single relay?
>
> Yeah, that was 8 optimistic, uninterrupted hours. Otherwise known as
"fa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/04/2015 06:19 PM, teor wrote:
>
> make test-network is dominated by the 25 second delay waiting for the
Tor test network to bootstrap. So it's not going to help much.
>
> I'm working on a chutney branch to measure bandwidth on "chutney
verify"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
One more thing for right now: how should I do benchmarks with chutney.
Should I measure the averages of how long it takes to complete the make
test-network command?
- - Cory
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBAgAGBQJVmDe/AAoJEB7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/04/2015 12:11 AM, teor wrote:
>
> The CHUTNEY_PATH variable needs to point to a directory containing a
chutney executable.
>
> So you seem to have it right the first time. What do you get when you run:
> ls -l ~/tor/chutney/
>
> I would expect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Tim,
I see that I may need to set some environment variables as told by the
git readme but the error message is on a different env var:
cory@Nulix ~/tor/tor =) make test-network
make all-am
make[1]: Entering directory `/home/cory/tor/tor'
make[
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/30/2015 09:26 AM, teor wrote:
> I think that our emails may have sent at about the same time.
> Was my last email to tor-dev the kind of advice you were expecting?
>
> https://lists.torproject.org/pipermail/tor-dev/2015-June/008988.html
Aweso
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yep, you got it!
People find it easiest to read mailing list posts if the subjects match.
And the threading works better that way, too.
Any time you reply to and quote a previous email, cut out the extra
stuff the mailing list adds in. And cutting o
nclude
-#include
+#include "tor_readpassphrase.h"
#include
#include
#include
and after I changed the linked header, I was good to go :-) Perhaps
this should be reflected on git?
On Mon, Jun 29, 2015 at 7:49 AM, Cory Pruce wrote:
> Thanks teor, that'd be awesome! I've
pecific
> than "Re: Contents of tor-dev digest..."
>
>
> Today's Topics:
>
>1. List of projects (Cory Pruce)
>2. Re: List of projects (Nick Mathewson)
>3. Re: List of projects (Cory Pruce)
>4. Re: Multithreaded crypto on Tor (teor)
>
>
&g
Awesome, no worries. Thanks!
On Jun 28, 2015 2:35 PM, "Nick Mathewson" wrote:
> On Sun, Jun 28, 2015 at 2:12 PM, Cory Pruce wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Hey,
> >
> > I see now that the multith
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey,
I see now that the multithreading on the crypto operations is at least
partly resolved (#9682) but there still exists more to be done. I could
help on the condition variables and possibly more with that project or
another one from the project id
Hi!
Let me start by introducing myself. My name is Cory Pruce, am an
Information Technology - Information Security Master's student at
Carnegie Mellon, and would like to get more involved in Tor! I have done
a bit of programming in C and have a pretty substantial crypto
background. I'm
16 matches
Mail list logo
