- tor-dev - lists.torproject.org

Tor on the Beaglebone Black
by Joshua Datko 22 Sep '13

22 Sep '13

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 a post with very basic installations: http://datko.net/2013/08/24/beagleboneblacktor/ So, what next? I looked at the torrouter project and I think I would have to probably have to redo the roadmap to suit the Beaglebone. Also, there is only one onboard NIC, so I'm not sure if that's a show stopper. I was going to do a fresh install of Debian, install Tor and then build an image so that it could be booting (or flashed to the eMMC) from a SD card, but wether that's better than installing tor oneself, I don't know. Anyway, just throwing an idea out there. Thanks everybody for the work on tor and I'm happy to be running a relay now. Josh

2 1

GSoC '13 Status Report - EvilGenius
by Johannes Fürmann 20 Sep '13

20 Sep '13

Hello tor-dev, Since the last report on EvilGenius, I was able to make a few last changes to EvilGenius which is now more or less feature-complete: * Internal routing issues are now solved packets are flowing happily. * Integrated OONI backend and probe * Wrote some user documentation I guess what's left to do for me is to fix some bugs, clean up the code a bit and get the developer documentation up to speed. Additionally, I will proceed to implement some actual censorship providers based on the ones I already had implemented in earlier versions. Have a nice weekend! Johannes

1 0

Pluggable Transport *Biweekly* Meeting, hence no meeting today
by vmonmoonshine＠gmail.com 20 Sep '13

20 Sep '13

Thanks for everybody who participated last week. The summary of the meeting can be found here: https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/meeti… We decided that we are going to have these meetings biweekly till we see if we need more or less frequent meetings. So the next one will be next week. See you all there. Best, Vmon

1 0

entry guards and linkability
by Leif Ryge 19 Sep '13

19 Sep '13

Is the following statement correct? When a user connects to Tor from multiple locations where the network is monitored by the same adversary, their persistent use of the same set of entry guards uniquely identifies them and reveals their location to the adversary. Assuming this is an accurate assessment, wouldn't it make sense to maintain separate sets of entry guards for each network that the user connects from? ~leif

2 3

What to read to analyze Tor's use of NTor?
by Roger Dingledine 19 Sep '13

19 Sep '13

Hi Nick, Ian, I've been pointing people to "Section 6 of http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.228.6223" when they ask what NTor is. But then I realized that that's not the best (single) place to send cryptographers when I ask them to analyze whether we've designed or built it right. Then I found https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/216-ntor-han… which looks great but then I also found https://gitweb.torproject.org/torspec.git/blob/HEAD:/tor-spec.txt#l852 which looks crisper. So the questions: A) Which combination and order of these three resources should I point people at? That is, does the tor-spec stanza replace proposal 216 completely, or is there still some use to looking at the proposal too, or is the proposal wrong now because you fixed stuff since then but didn't change the proposal, etc? Did I miss any good resources? B) What are the sketchiest parts -- the parts of the design or the implementation that you most want review on, or that you think would be most fruitful for finding issues? C) What else should I be asking you, in terms of how to get this thing reviewed the mostest and the bestest? We rolled out NTor quicker than we rolled out TAP, relatively speaking, and now it would count as breaking a widely deployed system so I bet we can get some more people evaluating it. Thanks! --Roger

2 1

Using TorPS to estimate chances of all-TAP paths
by Roger Dingledine 19 Sep '13

19 Sep '13

Hi Aaron, Sathya, I have another use for your fine path simulator. :) See https://trac.torproject.org/projects/tor/ticket/9777 The first question is: for a recent consensus, what's the chance that your middle hop and your exit hop will both be running 0.2.4.7-alpha or earlier? The extra credit for question one is to generate the answers to question one for each of the past n consensuses (where n is, say, the past month) so somebody can graph them. The second question is: if we change path selection to try again if we choose such a path, what does that do to our anonymity, for various definitions of anonymity like the ones in the upcoming CCS paper? The extra credit for question two, if you haven't guessed it already, is to get some data points for question two from the past as well. I'm guessing getting 24*30 of them will be no fun, so whatever isn't no fun is fine. What can I do to help make it happen? If the answers are "actually not all that high" and "oh hey those curves aren't all that different" respectively, I want to put #9777 into 0.2.4 and enable it. If those aren't the answers, we'll need to sort out a better plan. Thanks! --Roger

1 0

OnionMail First Test
by Liste 19 Sep '13

19 Sep '13

Work complete for the version 0.0.0Beta http://anopticon.ws/13c03c09/OnionMail-0.0.0.B.zip to create user: telnet 127.0.0.1 9100 C = client S = Server S: +OK ControlPort 1.0 sfl‚4£$£"f C: server alice hackme <- default password S: +OK KESIA [example] `example` C: addusr test <-- local part S: +OK New user created S: Mail=test(a)your.onion S: User=test S: SMTPPasswd=lunc6){><uFXSpaoWnJHl1px S: POP3Passwd=kfzb};VW,NKwLz"JM2Hmrwot S: Server=your.onion S: MsgSize=2000000 S: MaxMsg=128 S: MsgOld=40 S: Inet= S: QFDN=your.onion S: . C: quit S: +OK Closing smtp server (tls if available) 127.0.0.1 25 user test etc...etc... pop3 port 110 (tls if available) 127.0.0.1

5 6

BSD 2/3-Clause License (was: Torperf)
by Karsten Loesing 18 Sep '13

18 Sep '13

On 9/16/13 2:51 PM, Sathyanarayanan Gunasekaran wrote: > I'm currently using BSD 3-Clause License (used by Tor) for torperf2. > Kevin ported ooni's setup script and made it work with torperf2, but > ooni uses a BSD 2-Clause License (both are copyrighted to The Tor > Project). Kevin and I think they are compatible, but I wanted to check > in with you before I merged the changes. Thoughts? I have, honestly, no idea. Cc'ing tor-dev@ in the hope that someone else can answer this question. All the best, Karsten

3 2

Liberte-Linux cable-communication
by josef.winger＠email.de 17 Sep '13

17 Sep '13

Was there a discussion about the 'cables-communication' approach from Liberte-Linux in the mailing list? What's the general oppinion here? Is it trustable/secure/relyable? best /jo

1 0

Message to obfsproxy maintainers: New obfsproxy/pyptlib releases
by George Kadianakis 16 Sep '13

16 Sep '13

Hey people, some days ago I pushed new releases for obfsproxy and pyptlib. Latest releases are obfsproxy-0.2.3 and pyptlib-0.0.4: https://gitweb.torproject.org/pluggable-transports/pyptlib.git https://gitweb.torproject.org/pluggable-transports/obfsproxy.git Please upgrade the packages if you are interested :) The new releases add some nice features and bugfixes (see ChangeLog files). Also, obfsproxy-0.2.3 depends on pyptlib-0.0.4 so it would be great if you could upgrade both packages. (There is probably going to be another release in the next two weeks. I will keep you posted when it happens.) Thanks! PS: I have CCed the obfsproxy maintainers for Debian, FreeBSD, Arch and Gentoo. Sorry if I forgot someone else.

1 0