tor-webwml.git

@@ -317,6 +317,16 @@ meetings around the world.</li>

     and still under very active development.

     </p>

+    <p>

+    <b>Project Ideas:</b><br />

+    <i><a href="#tailsStartMenu">Custom GDM3 startup menu, aka.

+    tails-greeter</a></i><br />

+    <i><a href="#tailsMetadataAnonymizing">Meta-data anonymizing toolkit for

+    file publication</a></i><br />

+    <i><a href="#tailsDebianLive">Improve Debian Live support for

+    persistence</a></i>

+    </p>

+    

     <a id="project-torsocks"></a>

     <h3><a href="http://code.google.com/p/torsocks/">Torsocks</a> (<a

     href="https://gitweb.torproject.org/torsocks.git">code</a>, <a

@@ -604,6 +614,35 @@ meetings around the world.</li>

     TBB, please contact Erinn.</p>

     </li>

+    <a id="tailsStartMenu"></a>

+    <li>

+    <b>Custom GDM3 startup menu, aka. tails-greeter</b>

+    <br>

+    Priority: <i>High</i>

+    <br>

+    Effort Level: <i>Medium</i>

+    <br>

+    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

+    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

+    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>

+    <p>Anyone undertaking this project should be familiar with GNU/Linux and

+    application development; no other skill is required, apart of the ability

+    to quickly find practical answers in APIs and documentation for many

+    technologies she knows nothing about: this challenging coding project will

+    indeed involve getting familiar with some modern GNU/Linux Desktop

+    technologies such as D-Bus, GNOME and GConf. Python/GTK+ is probably the

+    best suited language for the task.</p>

+    <p>For more information see <a href="https://amnesia.boum.org/todo/boot_menu/">https://amnesia.boum.org/todo/boot_menu/</a></p>

+    </li>

+

     <!--

     <a id="trackNetworkStatus"></a>

     <li>

@@ -939,6 +978,67 @@ meetings around the world.</li>

     </p>

     </li>

 -->

+    

+    <a id="tailsMetadataAnonymizing"></a>

+    <li>

+    <b>Meta-data anonymizing toolkit for file publication</b>

+    <br>

+    Priority: <i>Medium</i>

+    <br>

+    Effort Level: <i>Low to Medium</i>

+    <br>

+    Skill Level: <i>Low to Medium</i>

+    <br>

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

+    <p>Tor helps greatly publishing files anonymously. However, much personal

+    information can be enclosed *inside* such published files meta-data: GPS

+    coordinates, authors 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 to easily inspect and cleanup meta-data in files

+    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

+    published files cleaning to various publishing tools, such as Desktop

+    social networking clients and Web content management systems.</p>

+    <p>This project mostly consists in writing glue between the many existing

+    tools and libraries that provide read/write access to files meta-data. An

+    extensible program design would probably be the best bet, so that support

+    for other kinds of files can easily be added later.</p>

+    <p>The meta-data cleaning toolkit would run at least on GNU/Linux;

+    additional Windows and/or Mac OS X support would be welcome. The tools used

+    would be up to the students. The detailed specification is ready and will

+    be published soon.</p>

+    

+    <a id="tailsDebianLive"></a>

+    <li>

+    <b>Improve Debian Live support for persistence</b>

+    <br>

+    Priority: <i>Medium</i>

+    <br>

+    Effort Level: <i>Medium</i>

+    <br>

+    Skill Level: <i>Low to Medium</i>

+    <br>

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

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

+    especially one explicitly designed to avoid leaving any trace of its use

+    such as TAILS.</p>

+    <p>Some real-life usecases however require to setup some kind of data

+    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

+    and require encrypted storage.</p>

+    <p>The backend part work consists in improving Debian Live existing

+    persistence features to make them suit the specific TAILS context. 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

+    script hack contest.</p>

+    <p>Anyone undertaking this project must be familiar with GNU/Linux, and

+    preferably with Debian. Being able to (quickly learn to) write clean and

+    safe programs in shell is also needed.</p>

+    <p>For more information see <a href="https://amnesia.boum.org/todo/persistence/">https://amnesia.boum.org/todo/persistence/</a></p>

+    

     <a id="torsocksForOSX"></a>

     <li>

     <b>Make torsocks/dsocks work on OS X</b>