Delivery-Date: Mon, 23 Jun 2014 03:56:42 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 0F2601E0AA9
	for <archiver@seul.org>; Mon, 23 Jun 2014 03:56:39 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 541A92FD27;
	Mon, 23 Jun 2014 07:56:35 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id F07DE2FB2B
 for <tor-talk@lists.torproject.org>; Mon, 23 Jun 2014 07:48:25 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id wr8BGKhQvvxS for <tor-talk@lists.torproject.org>;
 Mon, 23 Jun 2014 07:48:25 +0000 (UTC)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com
 [IPv6:2a00:1450:400c:c05::22a])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id A531B2FB25
 for <tor-talk@lists.torproject.org>; Mon, 23 Jun 2014 07:48:25 +0000 (UTC)
Received: by mail-wi0-f170.google.com with SMTP id cc10so3673729wib.3
 for <tor-talk@lists.torproject.org>; Mon, 23 Jun 2014 00:48:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=message-id:date:from:user-agent:mime-version:to:subject:references
 :in-reply-to:content-type:content-transfer-encoding;
 bh=6PQ8lDzp91FPJj0DDnxq5gkyF2DbYFyLF2rfvl8+aqU=;
 b=UT5mWXUBsEUxUhvjoQl6tQRLAExy0/4yZ3hAXjl8vbKubu4bRlHegzMQVzHgcwUw9d
 jSTiNkdOAL7UqlZbr1J4HIc2Z0VxRTtB6P50D5ChpQyCvFO3q0AlFumCNFBWyalb9BiZ
 JjCwLi9mgvqokiYLNJG1sEPRNyXrfepi4spF/C2p5s+cCt5NS1yOHItVeK0+Bbr5psHL
 z/AVSyPAqHOC5SmpY7HaZ8gJlfVuHDaFCLQioY/4qdMTG8Zyn5DeSCPhau5NmZJPrWgJ
 WFr7JIvUZxyUsIKuFufRYraF7r0FbbE9Pmr2DSpie7wIzlAb3O8lYctv5+kaTudFlX3j
 aMDQ==
X-Received: by 10.180.218.4 with SMTP id pc4mr23617619wic.21.1403509702254;
 Mon, 23 Jun 2014 00:48:22 -0700 (PDT)
Received: from [192.168.1.11] (ANice-652-1-127-121.w83-201.abo.wanadoo.fr.
 [83.201.150.121])
 by mx.google.com with ESMTPSA id i4sm1560963wib.21.2014.06.23.00.48.20
 for <tor-talk@lists.torproject.org>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Mon, 23 Jun 2014 00:48:21 -0700 (PDT)
Message-ID: <53A7DBCC.1070800@gmail.com>
Date: Mon, 23 Jun 2014 09:48:28 +0200
From: Aymeric Vitte <vitteaymeric@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <CAKW6+3TQMF0w47v7nGKxoz0Ld1w14H9r62Ta5pTcvU5YA_mdTw@mail.gmail.com>
 <5382EBE3.2000505@gmail.com> <538DDBD0.9040400@privatdemail.net>
 <538F2458.4000206@gmail.com> <53A714CB.2040802@privatdemail.net>
In-Reply-To: <53A714CB.2040802@privatdemail.net>
Subject: Re: [tor-talk] how to stream videos using Tor
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

There are two reasons right now why Peersm can not work with the Tor =

Browser, and the two reasons are linked: minimum release of FF should be =

26, indexedDB storage must be activated (and working correctly). FF =

version for Tor Browser is 24 and indexedDB is deactivated in the Tor =

Browser.

We are going to modify a few things so it works with the Tor Browser =

(partially, you won't still be able to store data but you will be able =

to stream when Mozilla has implemented [1] and the Tor Browser has the =

corresponding FF version, so unfortunately not tomorrow despite of the =

fact tha Mozilla is actively working on it)

Anyway, it's not advised to use the Tor Browser for Peersm app since the =

Tor protocol is inside the browser and the threat model is completely =

different from the Tor Browser since Peersm app is fecthing data, not =

browsing.

Using Peersm with the Tor Browser will make that the Peersm Tor protocol =

websocket connections are proxied to Tor instead of reaching directly a =

Tor/Peersm bridge, so performances will be uselessly impacted.

The only "risk" not using the Tor Browser is that we know your IP =

address when you load the code, that's one of the reasons why there will =

be a standalone version of Peersm (see [2] but it's not finished, no =

technical difficulties, just a lack of time, another one being that for =

technical reasons we can not use https to load the code, see [3] to know =

why).

Now, if you feel more comfortable, you can proxy the latest versions of =

FF or Chrome to Tor as explained in [4]


[1] https://bugzilla.mozilla.org/show_bug.cgi?id=3D778617
[2] https://github.com/Ayms/node-Tor/tree/master/min
[3 https://bugzilla.mozilla.org/show_bug.cgi?id=3D917829
[4] http://www.peersm.com/?use-en

Le 22/06/2014 19:39, nobody a =E9crit :
> It is still not possible to use this app with the newest TBB. I think it
> is because TBB uses FF 24.6.0
>
> Aymeric Vitte:
>> Le 03/06/2014 16:29, nobody a =E9crit :
>>> The website doesn't work for me. Javascript is completely enabled but I
>>> can't insert any links or clicking on stream/download/upload.
>> These are demo buttons and input for links on the web site, only "click
>> here to use it" button works and redirect you to the app, maybe we
>> should change/clarify this.
>>
>>> Also http://peersm.com/peersm is complete blank.
>> Yes, thanks to advise, there was an unfortunate (and forgotten) end of
>> May deadline for some old testing purposes, it's corrected.
>>
>>> I use the TBB 3.6.1-Linux
>>>
>>>
>>> Aymeric Vitte:
>>>> You can use Peersm http://www.peersm.com (see the streaming demo video
>>>> http://www.youtube.com/watch?v=3DYVaE8UZzDlA and the starter links
>>>> http://www.peersm.com/?links-en) to stream/download anonymously from
>>>> Peersm or bittorrent networks or the web.
>>>>
>>>> Even if not recommended for "normal" use you can use the TBB with Peer=
sm
>>>> (I don't know what's the current FF version of the official TBB, you
>>>> need FF>=3D26 for Peersm, if not see http://www.peersm.com/?use-en)
>>>>
>>>> Regards,
>>>>
>>>> Aymeric
>>>>
>>>> Le 26/05/2014 07:06, John Henry a =E9crit :
>>>>> I cannot stream videos using my Tor browser and I wondered if anyone
>>>>> could
>>>>> explain how that can be done.

-- =

Peersm : http://www.peersm.com
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms

-- =

tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

