tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

3) 

4) #include "head.wmi" TITLE="Tor: News"

5) 
6) <div class="main-column">
7) 
8) <!-- PUT CONTENT AFTER THIS TAG -->
9) 
10) <a id="News"></a>

11) <h2><a class="anchor" href="#News">Tor: News</a></h2>

12) <hr />
13) 
14) <ul>

15) <li>05 December 2008: Tor 0.2.0.32 released as stable.  Read the <a
16) href="http://archives.seul.org/or/announce/Dec-2008/msg00000.html">announcement</a>
17) for the updates and changes.</li>

18) <li>08 September 2008:  Tor 0.2.0.31 released as stable. Read the <a
19) href="http://archives.seul.org/or/announce/Sep-2008/msg00000.html">announcement</a>
20) for the updates and changes.</li>

21) <li>25 August 2008: Tor 0.2.0.30 released as stable.  Read the

22) <a
23) href="http://archives.seul.org/or/announce/Aug-2008/msg00000.html">announcement</a> or <a
24) href="https://blog.torproject.org/blog/tor-0.2.0.30-released-stable">blog
25) post</a> for the numerous updates and changes.</li>

26) <li>25 May 2008: Tor receives two awards from the <a
27) href="http://nlnet.nl/">NLnet Foundation</a>.  The first is to improve the performance
28) of hidden services.  The second is to make Tor work better for low bandwidth
29) clients.  The NLnet <a
30) href="http://nlnet.nl/news/2008/20080514-awards.html">awards page</a>
31) has more details about the two projects.</li>
32) 
33) <li>13 May 2008: <a href="http://archives.seul.org/or/talk/May-2008/msg00048.html">Tor 0.2.0.26-rc</a>
34) replaces several V3 directory authority keys affected by a recent <a
35) href="http://lists.debian.org/debian-security-announce/2008/msg00152.html">Debian
36) OpenSSL bug</a>.  <strong>This is a security-critical release.</strong>
37) Everybody running any version in the 0.2.0.x series should upgrade, whether
38) they are running Debian or not.  Also, all servers running any version of Tor
39) whose keys were generated by Debian, Ubuntu, or any derived distribution may
40) have to replace their identity keys.  See our
41) <a href="http://archives.seul.org/or/announce/May-2008/msg00000.html">security
42) advisory</a> or the <a
43) href="https://blog.torproject.org/blog/debian-openssl-flaw%3A-what-does-it-mean-tor-clients%3F">blog
44) follow-up</a> for full details.  As always, you can find Tor 0.2.0.26-rc on
45) the <a href="https://www.torproject.org/download#Dev">downloads page</a>.</li>

46) <li>Mar 2008: <a
47) href="https://blog.torproject.org/blog/tor-project-google-summer-code-2008!">Tor
48) Project is in Google Summer of Code 2008!</a></li>
49) 

50) <li>Feb 2008: The <a href="https://www.torproject.org/people#Board">Board
51) of Directors</a> welcomes <a
52) href="https://blog.torproject.org/blog/isaac-mao-elected-one-our-new-directors">Isaac

53) Mao</a> to the board.  We thank Rebecca McKinnon for her support and

54) contributions to the project.
55) 
56) <li>Feb 2008: Tor is happy to announce the <a
57) href="https://blog.torproject.org">official Tor blog</a>.</li>
58) 
59) <li>Jan 2008: <a href="<page download>">Tor 0.1.2.19</a> (the latest
60) stable release) fixes a huge memory leak on exit relays, makes the
61) default exit policy a little bit more conservative so it's safer to run an exit
62) relay on a home system, and fixes a variety of smaller issues. Please
63) upgrade.  Full <a
64) href="http://archives.seul.org/or/announce/Jan-2008/msg00000.html">release
65) notes</a> are available.</li>
66) 
67) <li>Oct 2007: <a href="<page download>">Tor 0.1.2.18</a> (the new stable
68) release) fixes many problems including crash bugs, problems with hidden
69) service introduction that were causing huge delays, and a big bug that
70) was causing some servers to disappear from the network status lists for
71) a few hours each day. We also modified the default Privoxy config files
72) in the bundles to avoid some security problems, so make sure to leave
73) "install Privoxy" checked when you upgrade. See the <a
74) href="http://archives.seul.org/or/announce/Oct-2007/msg00000.html">release
75) announcement</a> for more information.</li>
76) 
77) <li>Oct 2007: As many of you know, The Tor Project became an <a
78) href="<page people>">independent and official nonprofit</a> this past
79) February. We did this so we could accept grants from groups who
80) only donate to NGOs, and so our donors could deduct qualifying
81) <a href="<page donate>">donations</a> made to us.
82) <br />
83) We'd like to extend our profound thanks to the <a
84) href="https://www.eff.org/">Electronic Frontier Foundation</a> for their
85) past support, fiscal sponsorship, and help in hosting some of our web
86) pages, and for their continued mentorship of and counsel to our
87) fledgling nonprofit organization.</li>
88) 
89) <li>Sep 2007: If you have received email claiming to be Tor, it wasn't
90) from us. The <a href="<page download>">official Tor bundles</a> can be <a
91) href="http://wiki.noreply.org/noreply/TheOnionRouter/VerifyingSignatures">verified
92) as authentic</a>.</li>
93) 
94) <li>Aug 2007: <strong>Please update your Tor software!</strong>  The
95) latest versions (stable: 0.1.2.17; development: 0.2.0.6-alpha)
96) patch a significant security vulnerability.  See the <a
97) href="http://archives.seul.org/or/announce/Aug-2007/msg00000.html">release
98) announcement</a> for more information.</li>
99) 
100) <li>Feb 2007: The Tor Project and UColo/Boulder <a
101) href="http://blogs.law.harvard.edu/anonymous/2007/02/26/the-rumors-of-our-demise/">respond</a>
102) to a recent blogstorm regarding a paper documenting a possible attack
103) strategy against Tor.</li>
104) 
105) <li>Jan 2007: The Tor network has grown to hundreds of thousands of
106) users. The developers can't do all the new features, bug fixes, and
107) documentation. <a href="<page volunteer>">We need your help!</a></li>
108) 
109) <li><b>We are actively looking for new sponsors and funding.</b>
110) If your organization has an interest in keeping the Tor network usable
111) and fast, please <a href="<page contact>">contact us</a>. Sponsors of Tor
112) also get personal attention, better support, publicity (if they want it),

113) and get to influence the direction of our research and development.