tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

3) # Translation-Priority: 3-low

4) 

5) #include "head.wmi" TITLE="Tor: News" CHARSET="UTF-8"

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

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

13) <div class="underline"></div>

14) 
15) <ul>

16) <li>19 January 2010:  Tor 0.2.1.22 released as stable.  Fixes a critical
17) privacy problem in bridge directory authorities.  This stable update
18) also rotates two of the seven v3 directory authority keys and

19) locations.  Read the <a
20) href="http://archives.seul.org/or/announce/Jan-2010/msg00000.html">announcement</a>
21) for the full list of fixes.</li>

22) <li>21 December 2009: Tor 0.2.1.21 released as stable.  Fixes issues with OpenSSL and helps exit relays.  Read the <a href="http://archives.seul.org/or/announce/Dec-2009/msg00000.html">announcement</a> for the full list of fixes. </li>

23) <li>10 October 2009:  Tor 0.2.1.20 released as stable.  Read the <a href="https://blog.torproject.org/blog/tor-02120-released">announcement</a> for the updates and changes.</li>

24) <li>28 July 2009: Tor 0.2.1.19 released as stable.  Read the <a

25) href="http://archives.seul.org/or/announce/Aug-2009/msg00000.html">announcement</a>
26) for the updates and changes.</li>

27) <li>25 June 2009: Tor 0.2.0.35 released as stable.  Read the <a
28) href="http://archives.seul.org/or/announce/Jun-2009/msg00000.html">announcement</a> for the updates and changes.</li>

29) <li>12 March 2009:  Tor launches performance roadmap and campaign.  Read the <a href="<page press/2009-03-12-performance-roadmap-press-release>">Press Release</a> for more information.</li>

30) <li>09 February 2009:  Tor 0.2.0.34 released as stable.  Read the <a
31) href="http://archives.seul.org/or/announce/Feb-2009/msg00000.html">announcement</a>
32) for the updates and changes.  This release fixes a security issue.</li>

33) <li>21 January 2009: Tor 0.2.0.33 released as stable.  Read the <a
34) href="http://archives.seul.org/or/announce/Jan-2009/msg00000.html">announcement</a>
35) for the updates and changes.</li>

36) <li>19 December 2008: Tor releases 3-year development roadmap.  Read the

37) <a href="<page press/2008-12-19-roadmap-press-release>">Press Release</a>
38) for more information.</li>

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

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

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

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

50) <li>25 May 2008: Tor receives two awards from the <a
51) href="http://nlnet.nl/">NLnet Foundation</a>.  The first is to improve the performance
52) of hidden services.  The second is to make Tor work better for low bandwidth
53) clients.  The NLnet <a
54) href="http://nlnet.nl/news/2008/20080514-awards.html">awards page</a>
55) has more details about the two projects.</li>
56) 
57) <li>13 May 2008: <a href="http://archives.seul.org/or/talk/May-2008/msg00048.html">Tor 0.2.0.26-rc</a>
58) replaces several V3 directory authority keys affected by a recent <a
59) href="http://lists.debian.org/debian-security-announce/2008/msg00152.html">Debian
60) OpenSSL bug</a>.  <strong>This is a security-critical release.</strong>
61) Everybody running any version in the 0.2.0.x series should upgrade, whether
62) they are running Debian or not.  Also, all servers running any version of Tor
63) whose keys were generated by Debian, Ubuntu, or any derived distribution may
64) have to replace their identity keys.  See our
65) <a href="http://archives.seul.org/or/announce/May-2008/msg00000.html">security
66) advisory</a> or the <a
67) href="https://blog.torproject.org/blog/debian-openssl-flaw%3A-what-does-it-mean-tor-clients%3F">blog
68) follow-up</a> for full details.  As always, you can find Tor 0.2.0.26-rc on
69) the <a href="https://www.torproject.org/download#Dev">downloads page</a>.</li>

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

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

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

78) contributions to the project.</li>

79) 
80) <li>Feb 2008: Tor is happy to announce the <a
81) href="https://blog.torproject.org">official Tor blog</a>.</li>
82) 
83) <li>Jan 2008: <a href="<page download>">Tor 0.1.2.19</a> (the latest
84) stable release) fixes a huge memory leak on exit relays, makes the
85) default exit policy a little bit more conservative so it's safer to run an exit
86) relay on a home system, and fixes a variety of smaller issues. Please
87) upgrade.  Full <a
88) href="http://archives.seul.org/or/announce/Jan-2008/msg00000.html">release
89) notes</a> are available.</li>
90) 
91) <li>Oct 2007: <a href="<page download>">Tor 0.1.2.18</a> (the new stable
92) release) fixes many problems including crash bugs, problems with hidden
93) service introduction that were causing huge delays, and a big bug that
94) was causing some servers to disappear from the network status lists for
95) a few hours each day. We also modified the default Privoxy config files
96) in the bundles to avoid some security problems, so make sure to leave
97) "install Privoxy" checked when you upgrade. See the <a
98) href="http://archives.seul.org/or/announce/Oct-2007/msg00000.html">release
99) announcement</a> for more information.</li>
100) 
101) <li>Oct 2007: As many of you know, The Tor Project became an <a
102) href="<page people>">independent and official nonprofit</a> this past
103) February. We did this so we could accept grants from groups who
104) only donate to NGOs, and so our donors could deduct qualifying
105) <a href="<page donate>">donations</a> made to us.
106) <br />
107) We'd like to extend our profound thanks to the <a
108) href="https://www.eff.org/">Electronic Frontier Foundation</a> for their
109) past support, fiscal sponsorship, and help in hosting some of our web
110) pages, and for their continued mentorship of and counsel to our
111) fledgling nonprofit organization.</li>
112) 
113) <li>Sep 2007: If you have received email claiming to be Tor, it wasn't
114) from us. The <a href="<page download>">official Tor bundles</a> can be <a

115) href="<page verifying-signatures>">verified as authentic</a>.</li>

116) 
117) <li>Aug 2007: <strong>Please update your Tor software!</strong>  The
118) latest versions (stable: 0.1.2.17; development: 0.2.0.6-alpha)
119) patch a significant security vulnerability.  See the <a
120) href="http://archives.seul.org/or/announce/Aug-2007/msg00000.html">release
121) announcement</a> for more information.</li>
122) 
123) <li>Feb 2007: The Tor Project and UColo/Boulder <a
124) href="http://blogs.law.harvard.edu/anonymous/2007/02/26/the-rumors-of-our-demise/">respond</a>
125) to a recent blogstorm regarding a paper documenting a possible attack
126) strategy against Tor.</li>
127) 
128) <li>Jan 2007: The Tor network has grown to hundreds of thousands of
129) users. The developers can't do all the new features, bug fixes, and
130) documentation. <a href="<page volunteer>">We need your help!</a></li>
131) 
132) <li><b>We are actively looking for new sponsors and funding.</b>
133) If your organization has an interest in keeping the Tor network usable
134) and fast, please <a href="<page contact>">contact us</a>. Sponsors of Tor
135) also get personal attention, better support, publicity (if they want it),

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