Drop 'Panopticlick' project idea
Damian Johnson

Damian Johnson commited on 2017-01-29 22:15:24
Zeige 1 geänderte Dateien mit 0 Einfügungen und 54 Löschungen.


Kinda confusing since they called it 'Fingerprint Central' instead but from
what I can tell this was Pierre Laperdrix's project last year.
... ...
@@ -896,60 +896,6 @@ the codebase that you want to work on.
896 896
     </p>
897 897
     </li>
898 898
 
899
-    <a id="panopticlick"></a>
900
-    <li>
901
-    <b>Panopticlick</b>
902
-    <br>
903
-    Likely Mentors: <i>Georg (GeKo)</i>, <i>G&uuml;nes Acar</i>, <i>Nicolas (boklm)</i>
904
-    <p>
905
-
906
-The <a href="https://panopticlick.eff.org">Panopticlick project by the EFF</a>
907
-revolutionized how people think about <a
908
-href="https://panopticlick.eff.org/static/browser-uniqueness.pdf">browser
909
-fingerprinting</a>, both by developing tests and metrics to measure browser
910
-fingerprintability, and by crowdsourcing the evaluation and contribution of
911
-individual browser features to overall fingerprintability.
912
-
913
-    </p>
914
-    <p>
915
-
916
-Unfortunately, the way Panopticlick is designed <a
917
-href="https://blog.torproject.org/blog/effs-panopticlick-and-torbutton">makes
918
-it difficult</a> to evaluate defenses to browser fingerprinting, especially
919
-for browsers with a relatively small userbase such as Tor Browser. This is
920
-because any approach we take to reduce fingerprinting automatically makes our
921
-users more distinct from the previous users who submitted their fingerprint
922
-data to the EFF. Indeed, it is also impossible to ever expect that users of
923
-one browser will ever be able to blend in with users of another browser
924
-(Chrome users will always be distinguishable from Firefox users for example,
925
-based on feature set alone).
926
-
927
-   </p>
928
-   <p>
929
-
930
-To address this, we would like to have <a
931
-href="https://trac.torproject.org/projects/tor/ticket/6119">our own
932
-fingerprint test suite</a> to evaluate the fingerprintability of each browser
933
-feature for users running a specific Tor Browser version. There are also <a
934
-href="https://trac.torproject.org/projects/tor/query?keywords=~tbb-fingerprinting">additional
935
-fingerprinting tests</a> we can add beyond those deployed by Panopticlick.
936
-   </p>
937
-   <p>
938
-
939
-For this project, the student would develop a website that users can
940
-voluntarily visit to test and record their Tor Browser fingerprint.  The user
941
-should get feedback on how she performed and the test results should be
942
-available in a machine readable format (e.g. JSON), broken down by Tor Browser
943
-version.  In a second step one could think about adding more sophisticated
944
-tests or supporting other browser vendors that might want to test the
945
-uniformity amongst their userbase as well. Of course, results from each
946
-browser would also need to be broken down by both browser implementation and
947
-version, so that results would only reflect the population of that specific
948
-implementation.
949
-
950
-    </p>
951
-    </li>
952
-
953 899
     <a id="stegotorus"></a>
954 900
     <li>
955 901
     <b>Make Stegotorus deployment ready</b>
956 902