<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello all! <br>
</p>
<p>After a year away from my Tor related research, I'm finally back
at it. As I've
introduced in the past [1] I wanted to build a Tor Browser
Friendliness scanner
that would scan the web and rate the Tor Browser friendliness of
web pages. Unfortunately time got away from me for personal
reasons, but I finally got the
chance to work on the scanner and I feel it's close to being ready
to run. <br>
</p>
<p>To re-introduce the concept: the scanner checks a web page for
evidence of some
activity that would likely cause the site to not render or run
properly on the
Tor Browser. This includes the tests listed below, which are
motivated by
the Tor Browser Design Document [2] and our own experiences
analyzing what broke
on the Tor Browser during analysis of some randomly selected
websites. <br>
</p>
<p><u><b>Tests</b></u><br>
</p>
<p>1. Checks to see if the site supports HTTPS. If not, there's a
problem. <br>
2. Checks to see if the site serves JavaScript over HTTP. If not,
there could be
a problem on the Safer setting of the Tor Browser Security Slider,
<br>
3. Checks to see if there is auto-played media or hidden media.
This could cause
issues on the Safer setting of the Tor Browser Security Slider. <br>
4. Checks to see if there is any evidence of usage of the
following JavaScript
libraries/functionalities. These were taken from the draft of the
Tor Browser
Design Document. <br>
01. asm <br>
02. battery status <br>
03. game pad <br>
04. graphite <br>
05. media devices <br>
06. navigator online <br>
07. sensor <br>
08. network connection <br>
09. touch <br>
10. web audio <br>
11. webgl <br>
12. webrtc <br>
13. web speech <br>
14. HTML canvas <br>
5. Checks to see if the page contains JAR files or Flash files. <br>
6. Checks to see if the page contains chrome:// or <a class="moz-txt-link-freetext" href="resource://">resource://</a>
links.</p>
<p>Given this information, I have a few questions. <br>
</p>
<p>1. What other tests should I add, if any? <br>
2. Is there any other feedback on this idea that you'd like to
provide?</p>
<p>Please keep in mind that I intend on releasing the source code
soon. At the moment it's in an "academic code" state, and I want
to clean it up before release.<br>
</p>
<p>Thanks,</p>
<p>Kevin
</p>
<p>References:</p>
<p>[1]
<a class="moz-txt-link-freetext" href="https://lists.torproject.org/pipermail/tor-dev/2019-March/013731.html">https://lists.torproject.org/pipermail/tor-dev/2019-March/013731.html</a></p>
<p>[2] <a class="moz-txt-link-freetext" href="https://2019.www.torproject.org/projects/torbrowser/design/">https://2019.www.torproject.org/projects/torbrowser/design/</a><br>
</p>
<p></p>
</body>
</html>