tor-webwml.git

@@ -112,7 +112,7 @@ meetings around the world.</li>

       </tr>

       <tr class="alt">

-        <td><a href="#project-tails">TAILS</a></td>

+        <td><a href="#project-tails">Tails</a></td>

         <td>Usability</td>

         <td>Sys Admin</td>

         <td>Heavy</td>

@@ -656,11 +656,11 @@ meetings around the world.</li>

     Skill Level: <i>Medium to High</i>

     <br>

     Likely Mentors: <i>intrigeri, anonym</i>

-    <p>Several major upcoming TAILS features need to gather user input at

+    <p>Several major upcoming Tails features need to gather user input at

     startup time: bridges support, persistence, MAC address anonymization,

     etc.</p>

     <p>Existing boot menus lack the graphical widgets and generally

-    user-friendliness needed. Hence it was decided to implement TAILS startup

+    user-friendliness needed. Hence it was decided to implement Tails startup

     menu in GDM3: GDM3's default login/password prompt needs to be replaced

     with a custom GTK+ application hereby named tails-greeter that allows the

     user to provide any input necessary.</p>

@@ -1046,7 +1046,7 @@ meetings around the world.</li>

     coordinates, author's name and so on. Anyone who wants to anonymously

     publish a file can thus far too easily de-anonymize herself.</p>

     <p>A set of tools allowing users to easily inspect and clean up meta-data in files

-    would benefit Tor users, and would e.g. be shipped in TAILS.</p>

+    would benefit Tor users, and would e.g. be shipped in Tails.</p>

     <p>A graphical user interface is a must, but library and command-line

     interfaces are most welcome so that future work can add support for

     cleaning published files to various publishing tools, such as desktop

@@ -1072,15 +1072,15 @@ meetings around the world.</li>

     <br>

     Likely Mentors: <i>intrigeri, anonym</i>

     <p>Data persistence is a somewhat tricky topic in a Live system context,

-    especially one such as TAILS, which is explicitly designed to avoid

+    especially one such as Tails, which is explicitly designed to avoid

     leaving any trace of its use.</p>

     <p>Some real-life use cases, however, require some kind of data

-    persistence. To start with, TAILS should (carefully) support persistence of

+    persistence. To start with, Tails should (carefully) support persistence of

     application-specific configurations (e.g. GnuPG keyring) and of a user

-    arbitrary data store. Note that persistence in TAILS will always be opt-in

+    arbitrary data store. Note that persistence in Tails will always be opt-in

     and require encrypted storage.</p>

     <p>The backend work consists of improving Debian Live's existing

-    persistence features to make them suit the specific context of TAILS. A trust

+    persistence features to make them suit the specific context of Tails. A trust

     relationship is already established with upstream who is happy to merge our

     changes. The codebase is not that small and much refactoring is needed, so

     this really is a programming project rather than a fire'n'forget shell

@@ -52,7 +52,7 @@ use by any Android application to route Internet traffic through

 Orbot/Tor.</p>

 </td>

 <td>

-<div class="name"><a href="https://amnesia.boum.org/">TAILS</a></div>

+<div class="name"><a href="https://amnesia.boum.org/">Tails</a></div>

 <p>The (Amnesic) Incognito Live System is a live CD/USB distribution

 preconfigured so that everything is safely routed through Tor and leaves no

 trace on the local system.</p>