[tor-dev] tor-dev Digest, Vol 53, Issue 27
Cory Pruce
corypruce at gmail.com
Mon Jun 29 15:10:32 UTC 2015
So I found
[tor/master] Whoops; fix linux build again
commit f491aed8d03810271f800a04ed1d5f9e76f5af1f
Author: Nick Mathewson <nickm at ...
<http://gmane.org/get-address.php?address=nickm%2dNhLh2kY%2b9XYkk94PDnYflw%40public.gmane.org>>
Date: Sat Jun 27 22:41:39 2015 -0400
Whoops; fix linux build again
---
src/ext/readpassphrase.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/ext/readpassphrase.c b/src/ext/readpassphrase.c
index 7bdecaf..ab71935 100644
--- a/src/ext/readpassphrase.c
+++ b/src/ext/readpassphrase.c
<at> <at> -30,7 +30,7 <at> <at>
#include <signal.h>
#include <ctype.h>
#include <fcntl.h>
-#include <readpassphrase.h>
+#include "tor_readpassphrase.h"
#include <errno.h>
#include <string.h>
#include <unistd.h>
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 <corypruce at gmail.com> wrote:
> Thanks teor, that'd be awesome! I've been able to resolve most of the
> dependencies easily until the file "readpassphrase.h" (and thus .o) was
> shown to be missing during make. Are you still using the git branch? I'll
> definitely take a look into the throughput tool once I get set up :D
>
> - Cory
>
> On Mon, Jun 29, 2015 at 5:00 AM, <tor-dev-request at lists.torproject.org>
> wrote:
>
>> Send tor-dev mailing list submissions to
>> tor-dev at lists.torproject.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
>> or, via email, send a message with subject or body 'help' to
>> tor-dev-request at lists.torproject.org
>>
>> You can reach the person managing the list at
>> tor-dev-owner at lists.torproject.org
>>
>> When replying, please edit your Subject line so it is more specific
>> 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)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Sun, 28 Jun 2015 11:12:45 -0700
>> From: Cory Pruce <corypruce at gmail.com>
>> To: dgoulet at torproject.org, nickm at torproject.org,
>> meejah at torproject.org, atagar at torproject.org,
>> tor-dev at lists.torproject.org
>> Subject: [tor-dev] List of projects
>> Message-ID: <5590391D.6020900 at gmail.com>
>> Content-Type: text/plain; charset=utf-8
>>
>>
>> -----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 ideas on the Tor volunteer page. For
>> example, I've worked with the Stem library before doing primarily
>> traffic analysis in a class at Carnegie Mellon. If no one has worked on
>> the first option, I could do that as well. Please let me know if any of
>> you are willing to discuss these with me! I'd like to hear back knowing
>> that I'm talking to other human beings :-) Sorry if this isn't the way I
>> should be contacting. If so, let me know!
>>
>> - - Cory
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1
>>
>> iQIcBAEBAgAGBQJVkDkdAAoJEB7DuCIJauCg7q0P/0KNxwoLPo1ZlsO7X5/p+yC5
>> qHDHrAuVworNkER/t35xEQPJmGy9hTp7XaxHm2JWwbKpkWtS9dbTVA5LPD5esRsz
>> z5dhJOwKOXh9BIQ3qjBk22OPg1YbUJ8ykwTiwUY5BM/Tilk6UZqmjZDCOlpp5ufv
>> F4w9tUL9ug+K6VRnM/XksZhYjx1Wnhei5PesfZoTBiggj4T0q/16amduIhyALilm
>> HY5hHVCxo9mvmBBwzUwkRhi+kQ39eeLCggRbBqQv+WsYH8FNesoUcxFjy/AGzTGT
>> 4Ul4M8E41oHudtvmFIqzEgMmV5TjZaSR5X52aW+7mQAXRAH6IzxX8E+ji5CJIWLo
>> pE2zPV3dX+AsYx1lkU/x0hZvX2537wt8pNWka0ORTn7HKLnb/6NoaC7gYHr8ZftR
>> gcbSru49xyWNmzjfXSok7Unfih37MQY8Y1nGNqauHo8lZ38qmAnsdaGzAB409RgP
>> R30G82hg2QRFBA1486IqP/LtSxhk1UdEyWWvVlXWOYRvVF68l3g1mHVswIxT3k4G
>> z3a+0EmwF52xxvzgmMwTlxeWfa1/3uQA3w2el9e92/Xtc5lw66nE/k+kX7Mpg7GM
>> kDFZ0UkBgxXATy0kuCdU7enZjzpn6M1vDwhfmovpGAMDVaaMZzzII17KEJyVv8Sp
>> G7Wxg+lZjr9SOvRIOxf1
>> =Ebps
>> -----END PGP SIGNATURE-----
>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Sun, 28 Jun 2015 17:35:47 -0400
>> From: Nick Mathewson <nickm at torproject.org>
>> To: Cory Pruce <corypruce at gmail.com>
>> Cc: Damian Johnson <atagar at torproject.org>, meejah at torproject.org,
>> tor-dev at lists.torproject.org, David Goulet <
>> dgoulet at torproject.org>
>> Subject: Re: [tor-dev] List of projects
>> Message-ID:
>> <CAKDKvuzxLDGjokxZK26_X=_
>> H9-J_wMdOYrOakyGv2cs6kdPSig at mail.gmail.com>
>> Content-Type: text/plain; charset=UTF-8
>>
>> On Sun, Jun 28, 2015 at 2:12 PM, Cory Pruce <corypruce at gmail.com> wrote:
>> >
>> > -----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 ideas on the Tor volunteer page. For
>> > example, I've worked with the Stem library before doing primarily
>> > traffic analysis in a class at Carnegie Mellon. If no one has worked on
>> > the first option, I could do that as well. Please let me know if any of
>> > you are willing to discuss these with me! I'd like to hear back knowing
>> > that I'm talking to other human beings :-) Sorry if this isn't the way I
>> > should be contacting. If so, let me know!
>>
>> Hi, Cory, and sorry about the delay! I saw your earlier two messages,
>> and I just thought I'd send you a quick note today to say, "Yup, we
>> got them!" I'm going to be a little more slow responding than I would
>> like, since I'm preparing for a trip to PETS
>> (https://petsymposium.org/2015/), but I'll try to write back some
>> actual useful info as soon as I can.
>>
>> cheers,
>> --
>> Nick
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Sun, 28 Jun 2015 14:37:07 -0700
>> From: Cory Pruce <corypruce at gmail.com>
>> To: Nick Mathewson <nickm at torproject.org>
>> Cc: atagar at torproject.org, meejah at torproject.org, David Goulet
>> <dgoulet at torproject.org>, tor-dev at lists.torproject.org
>> Subject: Re: [tor-dev] List of projects
>> Message-ID:
>> <
>> CANOqyr7fzF2ADbmYof+Pufd3DGgFwVNqmLkZzvVSKecz_7QywQ at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Awesome, no worries. Thanks!
>> On Jun 28, 2015 2:35 PM, "Nick Mathewson" <nickm at torproject.org> wrote:
>>
>> > On Sun, Jun 28, 2015 at 2:12 PM, Cory Pruce <corypruce at gmail.com>
>> wrote:
>> > >
>> > > -----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 ideas on the Tor volunteer page. For
>> > > example, I've worked with the Stem library before doing primarily
>> > > traffic analysis in a class at Carnegie Mellon. If no one has worked
>> on
>> > > the first option, I could do that as well. Please let me know if any
>> of
>> > > you are willing to discuss these with me! I'd like to hear back
>> knowing
>> > > that I'm talking to other human beings :-) Sorry if this isn't the
>> way I
>> > > should be contacting. If so, let me know!
>> >
>> > Hi, Cory, and sorry about the delay! I saw your earlier two messages,
>> > and I just thought I'd send you a quick note today to say, "Yup, we
>> > got them!" I'm going to be a little more slow responding than I would
>> > like, since I'm preparing for a trip to PETS
>> > (https://petsymposium.org/2015/), but I'll try to write back some
>> > actual useful info as soon as I can.
>> >
>> > cheers,
>> > --
>> > Nick
>> >
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> http://lists.torproject.org/pipermail/tor-dev/attachments/20150628/939960de/attachment-0001.html
>> >
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Mon, 29 Jun 2015 10:27:27 +1000
>> From: teor <teor2345 at gmail.com>
>> To: tor-dev at lists.torproject.org
>> Subject: Re: [tor-dev] Multithreaded crypto on Tor
>> Message-ID: <703C2B27-DD87-422B-B2F1-12CC589E3A28 at gmail.com>
>> Content-Type: text/plain; charset="us-ascii"
>>
>>
>> > Date: Sat, 27 Jun 2015 20:44:02 -0700
>> > From: Cory Pruce <corypruce at gmail.com>
>> > To: tor-dev at lists.torproject.org
>> > Subject: [tor-dev] Multithreaded crypto on Tor
>> > Message-ID: <558F6D82.2010400 at gmail.com>
>> > Content-Type: text/plain; charset="utf-8"
>> >
>> > 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 not in the Google summer of code but would really like
>> > to complete this project :D (see screenshot) Please let me know if
>> > anyone is currently working on this and if Nick, David, or anyone would
>> > like to give me some advice and be someone I can bounce ideas off of :-)
>> >
>> > Thanks and I hope to hear back soon!
>> >
>> > - Cory
>> >
>> > P.S. I have cloned the repo and have been looking through relay.* and
>> > cpuworker.* files. I just would like to speak with someone before I jump
>> > in :p
>>
>> Hi Cory,
>>
>> Multithreaded crypto is a *very* popular request on the tor-relays
>> mailing list, as many relays have multiple cores, and significant network
>> bandwidth. Tor limits the number of relays per IPv4 address to 2 to
>> mitigate sybil attacks, so the best way for relay operators to increase
>> their throughput is multithreaded crypto.
>>
>> I'm not familiar with the specifics of tor's multithreading
>> implementation, but please contact me if you need assistance setting up a
>> local test network. I've made some recent changes to the chutney test tool
>> which allow throughput to be measured. These changes work on Linux and OS
>> X, but they're still under review, and the git branch isn't as organised as
>> I would like.
>>
>> teor
>>
>> teor2345 at gmail dot com
>> pgp 0xABFED1AC
>> https://gist.github.com/teor2345/d033b8ce0a99adbc89c5
>>
>> teor at blah dot im
>> OTR D5BE4EC2 255D7585 F3874930 DB130265 7C9EBBC7
>>
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: signature.asc
>> Type: application/pgp-signature
>> Size: 832 bytes
>> Desc: Message signed with OpenPGP using GPGMail
>> URL: <
>> http://lists.torproject.org/pipermail/tor-dev/attachments/20150629/64170a0e/attachment-0001.sig
>> >
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> tor-dev mailing list
>> tor-dev at lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
>>
>>
>> ------------------------------
>>
>> End of tor-dev Digest, Vol 53, Issue 27
>> ***************************************
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20150629/3e045e2e/attachment-0001.html>
More information about the tor-dev
mailing list