[guardian-dev] WebRTC

[Tim Prepscius]

There is something that could be done with this which might be interesting.

So I believe it possible for me to build a plugin for
chrome/firefox/maybe-safari which "intercepts" the google search page.
 When I type in a search for the google page it could do a "micro tor"
and talk to a different client B.

That client B would take the request, expunge cookies and make the
request to google, re-transmitting the final results to the
originating client.

It could sort of be a "enforced" no tracking.


I wonder if this would be possible.  It would be nice if I could
guarantee google cannot track me by cookie or ip address.


There would still need to be a central server for the initial look up
of potential "client B" but it would be far less bandwidth than doing
total proxy-ing and (possibly) wouldn't be illegal, since it could be
set up generically not just to target one big-brother-company.

This method could be used for any site which has a "request
information for Q, get response R"

???

-tim


On 7/31/13, Daniel Pocock <daniel at pocock.com.au> wrote:
> On 31/07/13 16:29, Timur Mehrvarz wrote:
>> On 07/30/2013 04:17 PM, Nathan of Guardian wrote:
>>> While the idea of peer-to-peer always seems great initially, if you are
>>> unable to route that through Tor, or bounce it off a middle mix server
>>> of some sort to mask end-points, I hesitate from adopting that as a tool
>>> for activists and journalists, say, who need to protect their networks
>>> and sources.
>> Actually, WebRTC traffic does *not have* to travel peer-to-peer. It can
>> also be pushed through proxies. Probably even through TOR. (Does TOR
>> route UDP?)
>
>
> The bigger question: do you want to risk an arbitrary ICE client such as
> a browser discovering all the local addresses and sending them to the
> peer?  It defeats the purpose of TOR
>
> For ICE to find the optimal connectivity path, it implicitly has to
> share topology information between the two endpoints.
> _______________________________________________
> Guardian-dev mailing list
>
> Post: Guardian-dev at lists.mayfirst.org
> List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev
>
> To Unsubscribe
>         Send email to:  Guardian-dev-unsubscribe at lists.mayfirst.org
>         Or visit:
> https://lists.mayfirst.org/mailman/options/guardian-dev/timprepscius%40gmail.com
>
> You are subscribed as: timprepscius at gmail.com
>