On Sun, Feb 08, 2015 at 02:01:40AM -0500, Roger Dingledine wrote:
> In the distant past, we had a ".noconnect" special extension in Tor:
> https://gitweb.torproject.org/torspec.git/tree/address-spec.txt#n58
> and the idea was that you would connect to Tor's control port, induce a
> request for foo.
On Sat, Feb 07, 2015 at 01:59:05PM +0100, Fabio Pietrosanti (naif) - lists
wrote:
> we're introducing client-side checking if a user it's on Tor or not on
> the GlobaLeaks Javascript client.
>
> So, the TorButton approach is to load
> https://check.torproject.org/?TorButton=true .
Note that the T
On 7 February 2015 at 06:59, Fabio Pietrosanti (naif) - lists
wrote:
> There's a right way to detect if a user it's on Tor, from a Browser,
> without loading an external network resource?
Is the javascript client loaded from a remote website? If so, what
about embedding the user's remote IP and
I don't think you can reliably tell without information from the
network; indeed, to the extent that you can tell *at all* without
information from the network, I would expect that to be considered a
bug.
The tactic that occurs to me is, have the investigative media
website's server stick a marker
Hi all,
we're introducing client-side checking if a user it's on Tor or not on
the GlobaLeaks Javascript client.
As far as i understood since some time ago, the right way to do it was
to detect a TBB user with some fingerprinting technique, however those
are going to disappear/being avoided/fixed
