<a href="https://torbutton.torproject.org/dev/design/#FirefoxBugs">Here</a> is some information on this bug and other firefox privacy issues<br><br><div class="gmail_quote">On Sat, Apr 19, 2008 at 9:33 PM, Gregory Maxwell <<a href="mailto:gmaxwell@gmail.com">gmaxwell@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Sun, Apr 20, 2008 at 12:05 AM, Mike Perry <<a href="mailto:mikeperry@fscked.org">mikeperry@fscked.org</a>> wrote:<br>
> Thus spake .FUF (<a href="mailto:fuf@itdefence.ru">fuf@itdefence.ru</a>):<br>
</div><div class="Ih2E3d">> Incidentally, this was filed as Firefox Bug<br>
> <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=405652" target="_blank">https://bugzilla.mozilla.org/show_bug.cgi?id=405652</a>. They have a fix<br>
> in the 3.0 branch. I requested backport into FF2.0.<br>
<br>
</div>It looks like the change just makes it send the current time. While<br>
that should be an improvement, It's not at all clear to me that the<br>
privacy issues of this are fixed.<br>
<br>
Many many users do not have clocks which are accurate enough that<br>
second level quantization hides their skew. I've successfully used<br>
remote client time to identify trouble making users on IRC (though on<br>
IRC I had the benefit of the returned time being local time rather<br>
than GMT).<br>
<br>
If the world didn't end with the client sending uptime .. could<br>
perhaps it send some other value?<br>
</blockquote></div><br>