<html><head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
<title>GSoC Application</title>
<style type="text/css">
body {
width:60%;
text-align:justify;
}
</style>
</head><body>
<h2><a href="http://torproject.org/">Tor Project</a> - DNSEL Rewrite</h2>
<b>Google Summer of Code Student Application</b> <br>
Harry Bock <hbock AT ele DOT uri DOT edu>
<blockquote>
<h2>Abstract:</h2>
<p>
The TorDNSEL project is concerned with identifying individual hosts
as valid and accessible Tor exit relays. Each Tor exit relay has an
associated exit policy governing what traffic may leave the Tor
circuit and go out as requests to the internet. A public database
that can be easily queried or scraped would be of huge benefit to
the Tor community and to services that are interested in whether
clients originate from the Tor network, such as Wikipedia and IRC
networks.
</p>
</blockquote>
<ol>
<li>
<strong>
What project would you like to work on? Use our ideas lists as a
starting point or make up your own idea. Your proposal should
include high-level descriptions of what you're going to do, with
more details about the parts you expect to be tricky. Your
proposal should also try to break down the project into tasks of a
fairly fine granularity, and convince us you have a plan for
finishing it.
</strong>
<p>
My primary interest is in the TorDNSEL rewrite. Currently
unmaintained and written in Haskell, I would like to rework it
from the ground up using Python and the Torflow interface.
</p>
<ul>
<li>
Prior to actually building the new TorDNSEL, some time must be
spent researching and testing strategies for identifying and verifying
recent Tor exit relays.
<ul>
<li>