Version 17 (modified by atagar, 7 years ago) (diff)

Adding second round of status reports that have come in so far

The following is a page to help with GSoC coordination. You're welcome to peruse the page but please don't edit this unless you're one of the org admins.

GSoC 2013

Student Primary Mentor Backup Mentor IRC Nick Passed Project
Kostas Jakeliunas Karsten Damian wfn Searchable Tor descriptor archive
Chang Lan Steven George clan Build Better Pluggable Transports
Hareesan Sukhbir Moritz hareesh Steganography Browser Addon
Cristian Toader Nick Andrea ctoader Run With Limited Capabilities Project
Lisa Micah Dan lisacyao HTTPS Everywhere Mixed Content Detection and Handling
Robert Mike Aaron ra Improvements on latency, bandwidth and anonymity in the Tor network
Johannes Fürmann Arturo Moritz waaaaargh Create an Internet Censorship Virtual Machine Based Simulator


  • 1st status update: June 28th
  • 2nd status update: July 12th
  • 3rd status update: July 26th
  • GSoC midterms: July 29th - August 2nd
  • 4th status update: August 9th
  • 5th status update: August 23th
  • 6th status update: September 6th
  • 7th status update: September 20th
  • GSoC finals: September 23rd - 27th

Status Reports

  • Kostas Jakeliunas (Searchable Tor descriptor archive)
  • Robert (Improvements on latency, bandwidth and anonymity in the Tor network)

GSoC 2012

Student Primary Mentor Backup Mentor IRC Nick Passed Project
Ravi Padmala Damian Sathyanarayanan neena yes Stem Improvements and Arm Port
Feroze Naina Tomás Sebastian feroze yes Implementing Hidden Service Configuration
Michele Orrù Arturo George maker-kun yes Anonymous Python Application Framework
Brandon Wiley George Nick blanu yes Pluggable Transports in Python
vmon Zack Weinberg Roger vmon yes Stegotorus
Julien Voisin intrigeri anonym jvoisin no Tails Server

Status Reports

Org Admin Checklist

The following is a cheat sheet for being an org admin for Google Summer of Code. Please add things that we're missing as we go along through the year.

  • Org Application Phase
  • Org Acceptance
  • Student Selection
    • Initial pass through applications
      • Flag spam applications
      • Make summary of the projects and assign potential primary mentor
      • Ask potential mentors to look them over and give feedback
    • Schedule meeting on IRC to discuss applications
    • Deduplication IRC meeting
  • Student Acceptance
    • Welcoming email
    • Details when about to start (last year's subject: "Start of GSoC")

Org Application

Organization Name

The Tor Project


The Tor Project is a free-software non-profit project to build an anonymity toolkit used by individuals, companies, governments, and law enforcement around the world. The Tor network has grown since its start in 2002 to several hundred thousand active users pushing over 17 Gbps of traffic. The Tor Project has a staff of 28 developers, researchers, and advocates, plus several dozen volunteers who help out on a daily basis.

Home page

Main Organization License

New and Simplified BSD licenses

Backup Admin

arma (include seb_hahn if they allow more than one)

If you chose "veteran" in the dropdown above, please summarize your involvement and the successes and challenges of your participation. Please also list your pass/fail rate for each year.

We participated in GSoC 2007 through 2012. In 2007 we had a pretty successful group of four students. We had one student working on making Tor servers scale better (and not crash!) on Windows, one working on a library and tool to choose paths through the network according to various rules like "cross at most one ocean", one working on a fuzzing library to look for parsing problems (it's found three so far), and one working on a new way to improve scalability and privacy for Tor hidden services. All four passed and have produced useful code.

The 2008 GSoC was a success, too. One of our successful GSoC 2008 students has written a nice blog post reviewing how GSoC went for him, for the other students, and for the project in general:

In 2009, we had 5 students to work on Tor, plus 1 more working for The Electronic Frontier Foundation. We had to pick these 6 out of 32 applications, which was a pretty hard process for us. In retrospect, there were at least 2 more students that we'd really have wanted to work on Tor but that we were not able to pick. Fortunately, they stuck with the project anyway, writing a neat relay monitor and helping reimplement Tor in Java for mobile devices. We wrote a wrap-up report how GSoC 2009 went for us here:

In 2010 we had 4 students work on Tor and 2 more with the EFF. Unfortunately one disappeared shortly after being accepted, but all the rest were successful and greatly benefited the projects they worked on (jtor, soat, torbel, metrics, and switzerland). A couple of these students also wrote blog posts summarizing their summer:

In 2011 we had 6 students to work on Tor and 1 more with the EFF. Two of those students (George and Sathyanarayanan) stayed afterward and became core Tor developers. Everyone was successful and some blogged about their experiences at...

In 2012 we had 6 students work with Tor. One had to leave the program soon after acceptance for personal reasons, but the rest were all successful. Starting this year we had students write bi-weekly status reports, you can find them on...

Stats for the success rate in prior years is: 4/4 in 2007, 4/7 in 2008, 5/6 in 2009, 5/6 in 2010, 7/7 in 2011, and 5/6 in 2012

Why is your organization applying to participate in GSoC 2013? What do you hope to gain by participating?

Tor has many open development tasks that are well-suited to summer projects, and also many students who are excited to work on them. GSoC can help these students work on important new free software work while also paying rent. In recent years The Tor Project has continued to grow, offering interesting new opportunities for summer projects. We expect to attract smart students as we did in prior years.

What is the URL for your Ideas list?

What is the main development mailing list for your organization?

What is the main IRC channel for your organization?


What criteria did you use to select your mentors for this year's program? Please be as specific as possible.

Seth Schoen, Peter Eckersley, and Micah Lee, and Dan Auerbach are EFF Staff as listed on The remaining individuals have each worked with Tor, most of them for several years, and most of them are in the "core development team" listed on Each individual has been leading his or her own projects related to Tor, and they are the most suited for mentoring students working on those modules. Note that five of our mentors and two of our admins are former GSoC students.

What is your plan for dealing with disappearing students?

We hope to minimize the chances of disappearing students by picking students who have already demonstrated commitment and/or interest to our community. Further, having multiple mentors per student can hopefully give us a better shot at keeping the students' interest.

We want to learn about disappearing students as early as possible. Therefore, we are planning to require our students to write bi-weekly status updates to keep us informed of their progress.

What is your plan for dealing with disappearing mentors?

Our plan is to assign two mentors per student to provide redundancy in case anything goes wrong. In general, our chosen mentors are EFF's staff or have been working on Tor for multiple years now (and for many of them, it's their full or part time job), so they're unlikely to just disappear.

What steps will you take to encourage students to interact with your project's community before and during the program?

Tor already has an active community on IRC and the mailing lists, and there's also an active research community of scientists trying to improve security of systems like Tor. We can draw on this community---the current active Tor volunteers as well as the graduate and undergraduate students at the research institutions. Further, we require our students to introduce themselves to the community, and to make periodic status reports available in a public format.

What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes?

In past years the students that stuck around afterward were the ones most invested in their project and our development community. We plan to encourage them to actively participate in discussions and connect with the community to improve their chances of staying on after the summer has ended.