git.schokokeks.org
Repositories
Help
Report an Issue
tor-webwml.git
Code
Commits
Branches
Tags
Suche
Strukturansicht:
1215974df
Branches
Tags
bridges
docs-debian
jobs
master
press-clips
tor-webwml.git
projects
en
google.wml
Update the projects.
Andrew Lewman
commited
1215974df
at 2008-06-03 05:37:15
google.wml
Blame
History
Raw
## translation metadata # Revision: $Revision: 14486 $ # Translation-Priority: 3-low #include "head.wmi" TITLE="Google Project: Automatic Upgrade of Tor" <div class="main-column"> <!-- PUT CONTENT AFTER THIS TAG --> <h2>Google Project: Automatic Upgrade of Tor</h2> <hr /> <p> </p> <p> This project is generously funded by <a href="http://www.google.com">Google</a>. </p> <a id="Timetable"></a> <h2><a class="anchor" href="#Timetable">Timetable</a></h2> <table width="100%" border="0" cellspacing="0" cellpadding="3"> <!-- <thead> <tr bgcolor="#e5e5e5"> <th>Deliverable</th> <th>Due Date</th> </tr> </thead> --> <tr bgcolor="#e5e5e5"> <td> <b>Milestone 1:</b> Vidalia recognizes when Tor needs to upgrade, and learns the most suitable new version and where to find it.<br /> <small><em>Looking at the majority-signed network status consensus to decide when to update and to what version (Tor already lists what versions are considered safe, in each network status document)</em></small> </td> <td> November 15, 2008 </td> </tr> <tr> <td> <b>Milestone 2:</b>Vidalia can fetch a new version of Tor from the Tor website and check its signature.<br /> <small><em>Update either via Tor or via the directory mirror update protocol (proposal 127) when possible, for additional privacy. Check package signatures to ensure package validity.</em></small> </td> <td> November 15, 2008 </td> </tr> <tr bgcolor="#e5e5e5"> <td> <b>Milestone 3:</b> Vidalia has an interface for notifying the user about upgrades and helping them upgrade. <br /> <small><em>Give the user an interface for these updates, including letting her opt to migrate from one major Tor version to the next. </em></small> </td> <td> November 15, 2008 </td> </tr> </table> <br /> <!-- Do we want a people section? If so, would it make sense to write what these people will be doing? And---what exactly are these people going to do? :) <a id="People"></a> <h2><a class="anchor" href="#People">People</a></h2> <ul> <li><a href="<page people>#Core">Jacob Appelbaum</a></li> <li><a href="<page people>#Core">Matt Edman</a></li> </ul> --> </ul> </div><!-- #main --> #include <foot.wmi>