<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce">
    <title>gmane.network.onion-routing.announce</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/20"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/19"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/18"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/17"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/16"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/15"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/14"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/13"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/12"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/11"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/10"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/9"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/8"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/7"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/6"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/5"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/4"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/3"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.onion-routing.announce/2"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/20">
    <title>Tor security advisory: Debian flaw causes weak identity keys</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/20</link>
    <description>SUMMARY:
  This is a critical security announcement.

  A bug in the Debian GNU/Linux distribution's OpenSSL package was
  announced today. This bug would allow an attacker to figure out private
  keys generated by these buggy versions of the OpenSSL library. Thus,
  all private keys generated by affected versions of OpenSSL must be
  considered to be compromised.

  Tor uses OpenSSL, so Tor users and admins need to take action in order
  to remain secure in response to this problem.

  If you are running Debian, Ubuntu, or any Debian-based GNU/Linux
  distribution, first follow the instructions at
    http://lists.debian.org/debian-security-announce/2008/msg00152.html
  to upgrade your OpenSSL package to a safe version. If you're running a
  Tor server or a Tor hidden service, then also follow the instructions
  below to replace your Tor identity keys.

  Also, if you are running Tor 0.2.0.x, you must upgrade to Tor
  0.2.0.26-rc.


WHO IS AFFECTED:
  This advisory applies to Tor 0.2.0.x and/or any Debian/U</description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2008-05-13T15:55:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/19">
    <title>Work on Tor this summer, get paid by Google</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/19</link>
    <description>Hi folks,

We (EFF and Tor working together) have been accepted into Google's
Summer of Code 2008. This means they'll fund several students to work
with us this summer on projects related to Tor. International students
are welcome too.

The deadline for students submitting applications is _MARCH 31_.

I've put up a page with more details here:
https://www.torproject.org/gsoc
and there's a big list of potential projects here:
https://www.torproject.org/volunteer#Projects

Please let us know if you're interested, and spread the word. The
more applications we get, the more likely Google is to give us good
students. So if you haven't filled up your summer plans yet, consider
spending some time working with us to make Tor better!

Thanks,
--Roger

</description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2008-03-25T19:13:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/18">
    <title>Tor 0.1.2.19 is released</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/18</link>
    <description>Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
exit policy a little bit more conservative so it's safer to run an exit
relay on a home system, and fixes a variety of smaller issues.

https://www.torproject.org/download.html

Changes in version 0.1.2.19 - 2008-01-17
  o Security fixes:
    - Exit policies now reject connections that are addressed to a
      relay's public (external) IP address too, unless
      ExitPolicyRejectPrivate is turned off. We do this because too
      many relays are running nearby to services that trust them based
      on network address.

  o Major bugfixes:
    - When the clock jumps forward a lot, do not allow the bandwidth
      buckets to become negative. Fixes bug 544.
    - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
      on every successful resolve. Reported by Mike Perry.
    - Purge old entries from the "rephist" database and the hidden
      service descriptor database even when DirPort is zero.
    - Stop thinking that</description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2008-01-19T18:20:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/17">
    <title>Tor 0.1.2.18 is released</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/17</link>
    <description>Tor 0.1.2.18 fixes many problems including crash bugs, problems with
hidden service introduction that were causing huge delays, and a big
bug that was causing some servers to disappear from the network status
lists for a few hours each day.

We also modified the default Privoxy config files in the bundles to
avoid some security problems, so make sure to leave "install Privoxy"
checked when you upgrade.

Bundle users should upgrade. People using Privoxy in other
contexts should make sure to follow the configuration advice at
https://www.torproject.org/docs/tor-doc-unix#privoxy

The Tor 0.1.1.x branch is now officially obsolete and unsupported.

https://www.torproject.org/download.html

Changes in version 0.1.2.18 - 2007-10-28
  o Major bugfixes (crashes):
    - If a connection is shut down abruptly because of something that
      happened inside connection_flushed_some(), do not call
      connection_finished_flushing(). Should fix bug 451:
      "connection_stop_writing: Assertion conn-&gt;write_event failed"
 </description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2007-10-31T13:32:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/16">
    <title>Tor security advisory: cross-protocol http form attack</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/16</link>
    <description>
Here are the further details that we promised:

In a nutshell, a malicious website or Tor exit node can give the Tor
user a page that includes a POST element directed to Tor's control port
(localhost:9051). Tor binds its control port only to localhost to avoid
letting untrusted people send it commands, but the attacker skips past
this protection by making the browser do the connection. And the user
doesn't even have to click on anything if she's got javascript enabled.

This particular attack worked because Tor's control protocol gave an
error message on unrecognized commands but didn't hang up. So all the
http headers from the POST were unrecognized commands, and eventually
we got to the payload -- which contains recognized commands -- and it
went bad from there.

Jochen Topf wrote a fine paper describing this attack in 2001:
http://www.remote.org/jochen/sec/hfpa/index.html
Thanks to Kyle Williams and Martin Peck who independently rediscovered
the attack in the context of Tor.

The 0.1.2.16 and 0.2.0.4-alp</description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2007-09-01T18:31:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/15">
    <title>Tor 0.1.2.17 is released</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/15</link>
    <description>Tor 0.1.2.17 features a new Vidalia version in the Windows and OS X
bundles. Vidalia 0.0.14 makes authentication required for the ControlPort
in the default configuration, which addresses important security risks.
Everybody who uses Vidalia (or another controller) should upgrade.

In addition, this Tor update fixes major load balancing problems with
path selection, which should speed things up a lot once many people
have upgraded.

https://tor.eff.org/download.html

Changes in version 0.1.2.17 - 2007-08-30
  o Major bugfixes (security):
    - We removed support for the old (v0) control protocol. It has been
      deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
      become more of a headache than it's worth.

  o Major bugfixes (load balancing):
    - When choosing nodes for non-guard positions, weight guards
      proportionally less, since they already have enough load. Patch
      from Mike Perry.
    - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
      will allow fast T</description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2007-08-31T05:50:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/14">
    <title>Tor 0.1.2.16 is released</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/14</link>
    <description>Tor 0.1.2.16 fixes a critical security vulnerability that allows a
remote attacker in certain situations to rewrite the user's torrc
configuration file. This can completely compromise anonymity of users
in most configurations, including those running the Vidalia bundles,
TorK, etc. Or worse.

Users who do not have ControlPort enabled are secure; if you are not
sure, you should upgrade and you should probably overwrite your torrc
file with the default when you upgrade. More details will be posted over
the next few days.

https://tor.eff.org/download.html

We have Vidalia bundles for OS X Tiger on the website now. The recommended
workaround for Windows users is either to wait until we have a Vidalia
bundle ready, or do separate installs of the Win32 "expert" package from
https://tor.eff.org/download-windows
and the Windows Vidalia-only package from
http://vidalia-project.net/download.php

Changes in version 0.1.2.16 - 2007-08-01
  o Major security fixes:
    - Close immediately after missing authentication on </description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2007-08-02T22:19:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/13">
    <title>Tor 0.1.2.15 is released</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/13</link>
    <description>Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
problems, fixes compilation on BSD, and fixes a variety of other
bugs. Everybody should upgrade.

https://tor.eff.org/download.html

Changes in version 0.1.2.15 - 2007-07-17
  o Major bugfixes (compilation):
    - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.

  o Major bugfixes (crashes):
    - Try even harder not to dereference the first character after
      an mmap(). Reported by lodger.
    - Fix a crash bug in directory authorities when we re-number the
      routerlist while inserting a new router.
    - When the cached-routers file is an even multiple of the page size,
      don't run off the end and crash. (Fixes bug 455; based on idea
      from croup.)
    - Fix eventdns.c behavior on Solaris: It is critical to include
      orconfig.h _before_ sys/types.h, so that we can get the expected
      definition of _FILE_OFFSET_BITS.

  o Major bugfixes (security):
    - Fix a possible buffer overrun when using BSD natd support. Bug
     </description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2007-07-23T10:08:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/12">
    <title>Tor 0.1.2.14 is released</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/12</link>
    <description>Tor 0.1.2.14 changes the addresses of two directory authorities (this
change especially affects those who serve or use hidden services),
and fixes several other crash- and security-related bugs.

We'll put out 0.1.1.27 in the next week or so for people who absolutely
can't upgrade -- but really, please upgrade to 0.1.2.14 if you can. Those
still running 0.1.0.x should now consider it obsolete and unsupported.

https://tor.eff.org/download.html

Changes in version 0.1.2.14 - 2007-05-25
  o Directory authority changes:
    - Two directory authorities (moria1 and moria2) just moved to new
      IP addresses. This change will particularly affect those who serve
      or use hidden services.

  o Major bugfixes (crashes):
    - If a directory server runs out of space in the connection table
      as it's processing a begin_dir request, it will free the exit stream
      but leave it attached to the circuit, leading to unpredictable
      behavior. (Reported by seeess, fixes bug 425.)
    - Fix a bug in dirserv_re</description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2007-05-25T21:13:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/11">
    <title>Tor 0.1.2.13 is released</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/11</link>
    <description>Tor 0.1.2.13, the first stable release of the 0.1.2.x branch, is
finally ready.

This release features some major anonymity fixes, such as safer path
selection; better client performance; faster bootstrapping, better address
detection, and better DNS support for servers; write limiting as well
as read limiting to make servers easier to run; and a huge pile of other
features and bug fixes. The bundles also ship with Vidalia 0.0.11.

https://tor.eff.org/download.html

Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
of the Freenode IRC network, remembering his patience and vision for
free speech on the Internet.

Changes in version 0.1.2.13 - 2007-04-24
  o Major features, client performance:
    - Weight directory requests by advertised bandwidth. Now we can
      let servers enable write limiting but still allow most clients to
      succeed at their directory requests. (We still ignore weights when
      choosing a directory authority; I hope this is a feature.)
    - Stop overloading e</description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2007-04-25T17:03:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/10">
    <title>Work on Tor this summer, get paid by Google</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/10</link>
    <description>Hi folks,

We (EFF and Tor working together) have been accepted into Google's
Summer of Code 2007. This means they'll fund several students to work
with us this summer on projects related to Tor. International students
are welcome too.

The deadline for students submitting applications is _MARCH 24_.

I've put up a page with more details here:
http://wiki.noreply.org/noreply/TheOnionRouter/SummerOfCode
and there's a big list of potential projects here:
http://tor.eff.org/volunteer.html.en#Coding

Please let us know if you're interested, and spread the word. The
more applications we get, the more likely Google is to give us good
students. So if you haven't filled up your summer plans yet, consider
spending some time working with us to make Tor better!

Thanks,
--Roger

</description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2007-03-16T07:31:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/9">
    <title>Tor 0.1.1.26 fixes HttpProxyAuthenticator privacy flaw</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/9</link>
    <description>Tor 0.1.1.26 fixes a serious privacy bug for people who use the
HttpProxyAuthenticator config option: Tor would send your proxy auth
directly to the directory server when you're tunnelling directory
requests through Tor. Specifically, this happens when publishing or
accessing hidden services, or when you have set FascistFirewall or
ReachableAddresses and you're accessing a directory server that's not
reachable directly.

The OS X stable bundles now also feature a new Vidalia version (0.0.9)
and a new Privoxy version (3.0.6).

http://tor.eff.org/download.html

If you use HttpProxyAuthenticator, we recommend you switch to 0.1.1.26
or stop using it for now. The upcoming 0.1.2.5-alpha (not yet finished)
will have this bugfix too. For people running 0.1.0.x who absolutely
cannot upgrade, here's your patch:
http://archives.seul.org/or/cvs/Dec-2006/msg00098.html

Changes in version 0.1.1.26 - 2006-12-14
  o Security bugfixes:
    - Stop sending the HttpProxyAuthenticator string to directory
      servers when direc</description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2006-12-17T07:37:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/8">
    <title>Tor 0.1.1.25 is released</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/8</link>
    <description>Tor 0.1.1.25 fixes yet more crashes and performance bugs, as well
as quieting some loud but harmless log warnings. If any of them are
bothering you, consider upgrading.

http://tor.eff.org/download.html

Changes in version 0.1.1.25 - 2006-11-04
  o Major bugfixes:
    - When a client asks us to resolve (rather than connect to)
      an address, and we have a cached answer, give them the cached
      answer. Previously, we would give them no answer at all.
    - We were building exactly the wrong circuits when we predict
      hidden service requirements, meaning Tor would have to build all
      its circuits on demand.
    - If none of our live entry guards have a high uptime, but we
      require a guard with a high uptime, try adding a new guard before
      we give up on the requirement. This patch should make long-lived
      connections more stable on average.
    - When testing reachability of our DirPort, don't launch new
      tests when there's already one in progress -- unreachable
      servers we</description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2006-11-09T07:27:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/7">
    <title>Tor 0.1.1.24 is released</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/7</link>
    <description>Tor 0.1.1.24 fixes some more crashes and performance bugs. If any
of them are bothering you, consider upgrading.

http://tor.eff.org/download.html

Changes in version 0.1.1.24 - 2006-09-29
  o Major bugfixes:
    - Allow really slow clients to not hang up five minutes into their
      directory downloads (suggested by Adam J. Richter).
    - Fix major performance regression from 0.1.0.x: instead of checking
      whether we have enough directory information every time we want to
      do something, only check when the directory information has changed.
      This should improve client CPU usage by 25-50%.
    - Don't crash if, after a server has been running for a while,
      it can't resolve its hostname.
    - When a client asks us to resolve (not connect to) an address,
      and we have a cached answer, give them the cached answer.
      Previously, we would give them no answer at all.

  o Minor bugfixes:
    - Allow Tor to start when RunAsDaemon is set but no logs are set.
    - Don't crash when the c</description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2006-10-08T03:54:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/6">
    <title>Tor security advisory: clients will route traffic</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/6</link>
    <description>The short version:
  Upgrade to 0.1.1.23.

Impact:
  A malicious entry node (the first Tor server in your path) can
  route traffic through your Tor client as though you're a server. It can
  only route traffic to other Tor servers though -- it can't induce any
  "exit" connections.

Versions affected:
  All versions of Tor in the 0.1.0.x series earlier than 0.1.0.18.
  All versions of Tor in the 0.1.1.x series earlier than 0.1.1.23.
  The experimental snapshot 0.1.2.1-alpha-cvs.

Solution:
  Upgrade to at least Tor 0.1.1.23. If you absolutely must stay with
  the 0.1.0.x series, I've put a patched tarball for the old 0.1.0.x
  series at:
  http://tor.eff.org/dist/tor-0.1.0.18.tar.gz
  http://tor.eff.org/dist/tor-0.1.0.18.tar.gz.asc

More details:

There is a bug in older versions of Tor that allows a hostile Tor server
to crash your Tor process, or route traffic through your client to the
Tor network as though it were a server. To exploit this bug, an attacker
needs to be or compromise the first Tor server </description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2006-08-29T09:29:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/5">
    <title>Tor 0.1.1.23 is released -- you should upgrade</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/5</link>
    <description>Tor 0.1.1.23 fixes more bugs in server reachability testing, a few more
crash bugs, and an important client-side bug.

Both clients and servers are strongly encouraged to upgrade.

http://tor.eff.org/download.html

Changes in version 0.1.1.23 - 2006-07-30
  o Major bugfixes:
    - Fast Tor servers, especially exit nodes, were triggering asserts
      due to a bug in handling the list of pending DNS resolves. Some
      bugs still remain here; we're hunting them.
    - Entry guards could crash clients by sending unexpected input.
    - More fixes on reachability testing: if you find yourself reachable,
      then don't ever make any client requests (so you stop predicting
      circuits), then hup or have your clock jump, then later your IP
      changes, you won't think circuits are working, so you won't try to
      test reachability, so you won't publish.

  o Minor bugfixes:
    - Avoid a crash if the controller does a resetconf firewallports
      and then a setconf fascistfirewall=1.
    - Avoid an inte</description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2006-08-04T01:47:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/4">
    <title>Tor 0.1.1.22 is released</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/4</link>
    <description>Tor 0.1.1.22 fixes reachability testing for servers, as well as partial
directory downloads. Servers should upgrade; clients who have flaky
or slow net connections will also benefit. We also bundle with the new
Vidalia version: 0.0.7.

http://tor.eff.org/download.html

Changes in version 0.1.1.22 - 2006-07-05
  o Major bugfixes:
    - Fix a big bug that was causing servers to not find themselves
      reachable if they changed IP addresses. Since only 0.1.1.22+
      servers can do reachability testing correctly, now we automatically
      make sure to test via one of these.
    - Fix to allow clients and mirrors to learn directory info from
      descriptor downloads that get cut off partway through.
    - Directory authorities had a bug in deciding if a newly published
      descriptor was novel enough to make everybody want a copy -- a few
      servers seem to be publishing new descriptors many times a minute.
  o Minor bugfixes:
    - Fix a rare bug that was causing some servers to complain about
      </description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2006-07-08T06:15:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/3">
    <title>Tor 0.1.1.21 is released</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/3</link>
    <description>Tor 0.1.1.21 fixes minor stability and protocol correctness problems,
mainly for Tor servers. We've also upgraded the Windows bundle with
Vidalia 0.0.5, and we're linking to a new OS X bundle with Vidalia 0.0.5
(finally a better interface for Mac users!). Lastly, we've added support
for SUSE-style RPM packages.

We're still tracking down some reported bugs in Tor server reachability
testing.

http://tor.eff.org/download.html

Changes in version 0.1.1.21 - 2006-06-10
  o Crash and assert fixes from 0.1.1.20:
    - Fix a rare crash on Tor servers that have enabled hibernation.
    - Fix a seg fault on startup for Tor networks that use only one
      directory authority.
    - Fix an assert from a race condition that occurs on Tor servers
      while exiting, where various threads are trying to log that they're
      exiting, and delete the logs, at the same time.
    - Make our unit tests pass again on certain obscure platforms.

  o Other fixes:
    - Add support for building SUSE RPM packages.
    - Speed up</description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2006-06-12T06:31:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.onion-routing.announce/2">
    <title>Tor 0.1.1.20 is released</title>
    <link>http://permalink.gmane.org/gmane.network.onion-routing.announce/2</link>
    <description>Tor 0.1.1.20, the first stable release of the 0.1.1.x branch, is
finally ready.

This release features some major security fixes, including entry guards
to protect the beginning of the circuit, exit enclaves to protect the
end, and better firewall support; a new directory protocol that improves
bandwidth use and keeps clients more up to date; two new directory
authorities; a new ascii-based controller protocol that lets people
easily write applications to interact with Tor; and many scalability
and performance improvements.

http://tor.eff.org/download.html

Changes in version 0.1.1.20 - 2006-05-23
  o Crash and assert fixes from 0.1.0.17:
    - Fix assert bug in close_logs() on exit: when we close and delete
      logs, remove them all from the global "logfiles" list.
    - Fix an assert error when we're out of space in the connection_list
      and we try to post a hidden service descriptor (reported by Peter
      Palfrader).
    - Fix a rare assert error when we've tried all intro points for
      a hidd</description>
    <dc:creator>Roger Dingledine</dc:creator>
    <dc:date>2006-05-24T12:19:20</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.network.onion-routing.announce">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.network.onion-routing.announce</link>
  </textinput>
</rdf:RDF>
