[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tor-talk
Subject:    Re: Tor 0.2.2.13-alpha is out
From:       "Kobe, Fan YANG" <kobeyoung81 () gmail ! com>
Date:       2010-04-29 10:27:16
Message-ID: n2me79035fb1004290327w80d37719i74c6f596a2461d73 () mail ! gmail ! com
[Download RAW message or body]

unsubscribe

On Thu, Apr 29, 2010 at 3:13 AM, Roger Dingledine <arma@mit.edu> wrote:

> Tor 0.2.2.13-alpha addresses the recent connection and memory overload
> problems we've been seeing on relays, especially relays with their DirPort
> open. If your relay has been crashing, or you turned it off because it
> used too many resources, give this release a try.
>
> https://www.torproject.org/download.html.en
>
> Changes in version 0.2.2.13-alpha - 2010-04-24
>  o Major bugfixes:
>    - Teach relays to defend themselves from connection overload. Relays
>      now close idle circuits early if it looks like they were intended
>      for directory fetches. Relays are also more aggressive about closing
>      TLS connections that have no circuits on them. Such circuits are
>      unlikely to be re-used, and tens of thousands of them were piling
>      up at the fast relays, causing the relays to run out of sockets
>      and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
>      their directory fetches over TLS).
>
>  o Minor features:
>    - Finally get rid of the deprecated and now harmful notion of "clique
>      mode", where directory authorities maintain TLS connections to
>      every other relay.
>    - Directory authorities now do an immediate reachability check as soon
>      as they hear about a new relay. This change should slightly reduce
>      the time between setting up a relay and getting listed as running
>      in the consensus. It should also improve the time between setting
>      up a bridge and seeing use by bridge users.
>    - Directory authorities no longer launch a TLS connection to every
>      relay as they startup. Now that we have 2k+ descriptors cached,
>      the resulting network hiccup is becoming a burden. Besides,
>      authorities already avoid voting about Running for the first half
>      hour of their uptime.
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iD8DBQFL2IjP61qJaiiYi/URAqi/AKCR8P/SHKmTfucFliYX0Pb21VwkKACgxTA2
> onjodL4byTlt8G+VO54f92A=
> =RVsB
> -----END PGP SIGNATURE-----
>
>


-- 
Kobe Young

[Attachment #3 (text/html)]

unsubscribe<br><br><div class="gmail_quote">On Thu, Apr 29, 2010 at 3:13 AM, Roger \
Dingledine <span dir="ltr">&lt;<a \
href="mailto:arma@mit.edu">arma@mit.edu</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex;">

Tor 0.2.2.13-alpha addresses the recent connection and memory overload<br>
problems we&#39;ve been seeing on relays, especially relays with their DirPort<br>
open. If your relay has been crashing, or you turned it off because it<br>
used too many resources, give this release a try.<br>
<br>
<a href="https://www.torproject.org/download.html.en" \
target="_blank">https://www.torproject.org/download.html.en</a><br> <br>
Changes in version 0.2.2.13-alpha - 2010-04-24<br>
   o Major bugfixes:<br>
      - Teach relays to defend themselves from connection overload. Relays<br>
         now close idle circuits early if it looks like they were intended<br>
         for directory fetches. Relays are also more aggressive about closing<br>
         TLS connections that have no circuits on them. Such circuits are<br>
         unlikely to be re-used, and tens of thousands of them were piling<br>
         up at the fast relays, causing the relays to run out of sockets<br>
         and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling<br>
         their directory fetches over TLS).<br>
<br>
   o Minor features:<br>
      - Finally get rid of the deprecated and now harmful notion of &quot;clique<br>
         mode&quot;, where directory authorities maintain TLS connections to<br>
         every other relay.<br>
      - Directory authorities now do an immediate reachability check as soon<br>
         as they hear about a new relay. This change should slightly reduce<br>
         the time between setting up a relay and getting listed as running<br>
         in the consensus. It should also improve the time between setting<br>
         up a bridge and seeing use by bridge users.<br>
      - Directory authorities no longer launch a TLS connection to every<br>
         relay as they startup. Now that we have 2k+ descriptors cached,<br>
         the resulting network hiccup is becoming a burden. Besides,<br>
         authorities already avoid voting about Running for the first half<br>
         hour of their uptime.<br>
<br>
<br>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.9 (GNU/Linux)<br>
<br>
iD8DBQFL2IjP61qJaiiYi/URAqi/AKCR8P/SHKmTfucFliYX0Pb21VwkKACgxTA2<br>
onjodL4byTlt8G+VO54f92A=<br>
=RVsB<br>
-----END PGP SIGNATURE-----<br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Kobe Young<br>


***********************************************************************
To unsubscribe, send an e-mail to majordomo@torproject.org with
unsubscribe or-talk    in the body. http://archives.seul.org/or/talk/

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic