- tor-dev - lists.torproject.org

Re: [tor-dev] tor-dev Digest, Vol 53, Issue 27
by Cory Pruce 29 Jun '15

29 Jun '15

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(a)lists.torproject.org> wrote: > Send tor-dev mailing list submissions to > tor-dev(a)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(a)lists.torproject.org > > You can reach the person managing the list at > tor-dev-owner(a)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(a)gmail.com> > To: dgoulet(a)torproject.org, nickm(a)torproject.org, > meejah(a)torproject.org, atagar(a)torproject.org, > tor-dev(a)lists.torproject.org > Subject: [tor-dev] List of projects > Message-ID: <5590391D.6020900(a)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(a)torproject.org> > To: Cory Pruce <corypruce(a)gmail.com> > Cc: Damian Johnson <atagar(a)torproject.org>, meejah(a)torproject.org, > tor-dev(a)lists.torproject.org, David Goulet <dgoulet(a)torproject.org > > > Subject: Re: [tor-dev] List of projects > Message-ID: > <CAKDKvuzxLDGjokxZK26_X=_ > H9-J_wMdOYrOakyGv2cs6kdPSig(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Sun, Jun 28, 2015 at 2:12 PM, Cory Pruce <corypruce(a)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(a)gmail.com> > To: Nick Mathewson <nickm(a)torproject.org> > Cc: atagar(a)torproject.org, meejah(a)torproject.org, David Goulet > <dgoulet(a)torproject.org>, tor-dev(a)lists.torproject.org > Subject: Re: [tor-dev] List of projects > Message-ID: > < > CANOqyr7fzF2ADbmYof+Pufd3DGgFwVNqmLkZzvVSKecz_7QywQ(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Awesome, no worries. Thanks! > On Jun 28, 2015 2:35 PM, "Nick Mathewson" <nickm(a)torproject.org> wrote: > > > On Sun, Jun 28, 2015 at 2:12 PM, Cory Pruce <corypruce(a)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 > > >

1 1

Re: [tor-dev] Multithreaded crypto on Tor
by teor 29 Jun '15

29 Jun '15

> Date: Sat, 27 Jun 2015 20:44:02 -0700 > From: Cory Pruce <corypruce(a)gmail.com> > To: tor-dev(a)lists.torproject.org > Subject: [tor-dev] Multithreaded crypto on Tor > Message-ID: <558F6D82.2010400(a)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

1 0

List of projects
by Cory Pruce 28 Jun '15

28 Jun '15

-----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-----

2 2

Multithreaded crypto on Tor
by Cory Pruce 28 Jun '15

28 Jun '15

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 project

1 0

Tor dev meetings schedule changes for July
by Nick Mathewson 27 Jun '15

27 Jun '15

Hello, all! Usually the Tor development team has our weekly online[1] Tor developers meetings at Wednesday 1330 UTC (==0930 EDT), and our weekly online patch workshop time at 1800 UTC (==1400 EDT). (This is for the program 'tor', not for all the other software that happens in the Tor universe) But for the first week of July, a lot of people will be in PETS[2]. And for the second week, I'll be on vacation. So here's the revised schedule. Tuesday, June 30: Patch workshop goes on as scheduled. Nick and a few others will probably be absent. Wednesday, July 1: No weekly dev meeting! Tuesday, July 7: Patch workshop goes on as scheduled. Nick will be absent; others will be back. Wednesday, July 8: Dev meeting goes on as scheduled. Nick will probably be absent, but will send in an update somehow. For the rest of the month, we'll be on a regular schedule. [1] #tor-dev on OFTC [2] https://petsymposium.org/2015/ best wishes, -- Nick

1 0

Fwd: Orbot v15.0.1 beta 3 and NetCipher update
by Nathan Freitas 26 Jun '15

26 Jun '15

----- Original message ----- From: Nathan of Guardian <nathan(a)guardianproject.info> To: guardian-dev(a)lists.mayfirst.org Subject: Orbot v15.0.1 beta 3 and NetCipher update Date: Fri, 26 Jun 2015 10:19:49 -0400 *** Orbot v15.0.1 beta 3 released *** From: https://dev.guardianproject.info/news/233 See our previous news update (https://dev.guardianproject.info/news/231) for the more data or review the changelog here: https://gitweb.torproject.org/orbot.git/tree/CHANGELOG?id=e00f830ecadbca1b0… We've pushed the release to our Google Play beta channel (https://play.google.com/apps/testing/org.torproject.android) and our /release folder here. APK: https://guardianproject.info/releases/Orbot-v15.0.1-beta-3.apk PGP Sig: https://guardianproject.info/releases/Orbot-v15.0.1-beta-3.apk.asc You can also use FDroid to subscribe to our nightlies repo here (please uninstall any other version of Orbot first): https://dev.guardianproject.info/debug/org.torproject.android/fdroid/repo *** NetCipher library updated (v1.2) *** We've also updated our NetCipher library to support the update Intent API in Orbot that supports background starting, improved status messages via broadcasts and more. NetCipher also includes clearer code for support HttpUrlConnection proxying, TLS socket hardening, and has been re-organized a bit for clarity. https://github.com/guardianproject/NetCipher The sample app shows how to use these classes: https://github.com/guardianproject/NetCipher/tree/master/sample -- Nathan of Guardian nathan(a)guardianproject.info

1 0

update obfs4proxy in deb.torproject.org
by s7r 24 Jun '15

24 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, An update is needed in http:// deb.torproject.org/torproject.org obfs4proxy main to version 0.0.5 (we currently have 0.0.4). armel and amrhf packages for obfs4proxy would be nice too, for mobiles/tablets/raspberrys etc. Also, why do we have tor-experimental-0.2.6.x-$dist_codename and tor-nightly-0.2.6.x-$dist_codename - any difference between them? I know 'nightly master' is for latest alpha dev release, but what's the experimental used for? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBCAAGBQJVhzu8AAoJEIN/pSyBJlsRIXgH/1v01c0oArU6E/xyzfi4DLN6 6bLK9emfzTAimtwgIQfH1POL+GR3xqpLl5TURN0wGEdI1Sm1vBK6wg0/mnsjNJAD +yulRlfJlbjLn+H2TJ1XFsKNQudIRpstdjQ0hyrA4SmOV3V42rk6taQSdM/b+zwG 2v54+P05Th/bbq63UDKoLjbzal/sMUe+2l1lYxO1BbxiXL9JkGU5qCTnG8uM+yXK IEXCdDlZpEdmov6ueP3PdiCrhS9v5HsZ7TIGKqVuuie6Kf1yrxIgBP5rlKsdJgqI V1bnHyhs1zvME+Klw+DF8Axqb1PqPY/dV5WoIo+s++H3+phA1TSmG46ebj5WG6E= =R2Kk -----END PGP SIGNATURE-----

2 1

Re: [tor-dev] The future of GetTor
by Adam Pritchard 23 Jun '15

23 Jun '15

> > I'm currently the maintainer of GetTor [1], and together with Nima and > Sukhbir we have been talking about the future of it. If this conversation moves elsewhere, I would really like to be kept in the loop. I'm the primary maintainer of Psiphon's email auto-responder, which was initially modeled on Tor's approach. Psiphon is, obviously, also extremely interested in robust ways of making our tools available in censoring regions. (So, Satori, etc., are also interesting.) Relatedly... When doing Logjam, etc., testing on our responder I found testssl.sh[1] to be a handy tool. Used like so: ./testssl.sh --mx torproject.org CheckTLS[2] is also good for actually doing email send and receive tests. We're currently struggling a bit with just how hardcore we can be in securing our server communications. Right now Postfix is configured[3] to only connect out using TLS and only accept incoming TLS connections from servers with a verifiable cert. That seems reasonable, except... we're getting complaints that Chinese mail services don't meet those criteria, and Chinese users can't/won't/don't use Gmail/Hotmail/Yahoo. ...As an example of the sort of shared hurdles we might encounter. [1]: https://testssl.sh/ [2]: https://www.checktls.com/ [3]: https://bitbucket.org/psiphon/psiphon-circumvention-system/src/2d052db9597d… -- Adam Pritchard Psiphon Inc.

2 4

small patch to allow gcc -fno-common for better ASAN coverage
by starlight.2015q2＠binnacle.cx 23 Jun '15

23 Jun '15

Per https://code.google.com/p/address-sanitizer/wiki/Flags one benefits from compiling with -fno-common when -fsanitize=address is active The attached patch converts the single common variable to a global/extern variable. Seems a good idea to me. Have run this with no issues, but more ASAN coverage is better than less.

1 0

How bad is not having 'enable-ec_nistp_64_gcc_128' really? (OpenBSD)
by nusenu 23 Jun '15

23 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, since enable-ec_nistp_64_gcc_128 is disabled by default on OpenBSD due to compiler bugs [1] I wanted to ask how bad is it (in relay context) to ignore the usual tor log entry: > We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, > but with a version of OpenSSL that apparently lacks accelerated > support for the NIST P-224 and P-256 groups. Building openssl with > such support (using the enable-ec_nistp_64_gcc_128 option when > configuring it) would make ECDH much faster. Tor's changelog "highly recommends" it [2]. Can this be "translated" to something like "the relay's bandwidth usage and usefulness will be reduced" "latency will be higher" "security will be degraded due to fallback to DH-1024" ? thanks, nusenu [1] http://article.gmane.org/gmane.os.openbsd.misc/218944 [2] https://gitweb.torproject.org/tor.git/plain/ReleaseNotes?id=tor-0.2.5.10 -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJViDmDAAoJEFv7XvVCELh0Fi0QAKF0/7eVWgL5gExyGcCugz66 9CJOaNGVdeqb8LDxH/KEW4xC+MLhqMQ/+dL7iVOZIOtCM6i4vTpD3u4ZVnFhcGfx luyX78TqXDW3riV3izBWYScYxQdeHGv3XFXQlbGi7WQYfRt0AdorchmP2xuxD7Cg zGZFk4Bggj3qnW1sd/G3JvJL0bUi7iBKrQwPTDlnK3YSGbTYpU6lS3dQqbHqNYin yrwtlNSCi9DFjbQm5g4yjvaawnmOuxf8dlm54Ltjdn2cIHsXaPqQ6kXICiukrJhE ZLfTnPBd3yngyoq9xe7bW9P4mNVkTNmAU3VqGgEq1gSUJQObXkzOKAz63z9WAqQl GBvZFtwkbdBM4pjfWaG5FjDRc+awXxP/8K/d2vF2r6KAwkbh9Fw2uhjC6yu5c6hB KtQaovd+we+Ag4vDdE6lbQPLiCbPBiFdB6qYjkWbVflYcrsYQPoCgwjaodbV7I/Y 8Kb3Lx2C8+HFLtktEh19tOk34iKVliQk7FjE2FoiKkWryRYtY5KUAfFS8hOCfBqr 2XYtWGqQ9eh14RqvBu7CuN1cKCc0EQLcr6BF9uvd6EYtKZsa5rQC+y9Bbbd65MwB qU7lLckEkG+qwzgvuyOBvGwN8JmMmTBQASsdalAUscQFbPq7wySp9tz21pu8mOje NRRdnL1/3X9KcCMLMCVk =Oa2Z -----END PGP SIGNATURE-----

4 4