Delivery-Date: Thu, 28 May 2015 22:35:15 -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=-2.5 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FORGED_YAHOO_RCVD,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,
	T_RP_MATCHES_RCVD 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 0DCB71E1422;
	Thu, 28 May 2015 22:35:14 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 4C90135450;
	Fri, 29 May 2015 02:35:08 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 60A813544E
 for <tor-talk@lists.torproject.org>; Fri, 29 May 2015 02:35:05 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
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 PvTZujFUdHBN for <tor-talk@lists.torproject.org>;
 Fri, 29 May 2015 02:35:05 +0000 (UTC)
Received: from nm24-vm0.bullet.mail.bf1.yahoo.com
 (nm24-vm0.bullet.mail.bf1.yahoo.com [98.139.213.161])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 418B63544C
 for <tor-talk@lists.torproject.org>; Fri, 29 May 2015 02:35:05 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048;
 t=1432866902; bh=gdal4LF+aVcr35JAzroivquVEh9vdewwoR0L/APYSI8=;
 h=Date:From:To:Subject:References:In-Reply-To:From:Subject;
 b=XstoInGmvzQ87ub8aYC5Xtatalc0JLw69SrgvfjJbdCBOzlL0cZfDfqV1DTZca+rNkPXIDukOk9FgfL0t+O3L/xX8qLFWQ9vMiKHJ0UNyR80aAee4xKc0WLfYFJ1QHNmfN5dZw1hzhqkOvxGJbM1xsmK2sux+RXdctHMU3jzbtzd2/cTwB4LCT70rh2Q2Y9ibVcnTX7rAWta5BOTTQjPPuZfxrDEhI6KmfzpJpPWFT1NoV7XmBvLDNdTLk9LF5tSwscrwpYmDGWXD8quQtW4ttFe5Es0PbXdejuXvYgwO/a3KTpbvYpNYhn2Fht3AN1EGb7YGix/Yrb+AQxKH9eiEg==
Received: from [66.196.81.170] by nm24.bullet.mail.bf1.yahoo.com with NNFMP;
 29 May 2015 02:35:02 -0000
Received: from [98.139.211.194] by tm16.bullet.mail.bf1.yahoo.com with NNFMP;
 29 May 2015 02:35:02 -0000
Received: from [127.0.0.1] by smtp203.mail.bf1.yahoo.com with NNFMP;
 29 May 2015 02:35:02 -0000
X-Yahoo-Newman-Id: 580220.71844.bm@smtp203.mail.bf1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: ifUmRPYVM1nTrUDqEsxRdSy.4hdpSfYbsPthqERHKNisYac
 sgjvRgRAV7BKu8vzKG9DGy1o1wJ77HajJwfH8Ii1UJ0fDkoeF769iRTrnEhn
 pFUn79sJAS.DDf9JRC8xnecCuOhwrSYwO_aVzyyz89GESi3W.dtOubRpqSlO
 4tNX9ps.VtLYA12QirBfCbgtiqoR.NRnPFBFow.EXOT06mkbvxjdHfHd3D0U
 oykirJ9qgAkO9Ws6ymS9ws6AX.YhfruPVUnZN6.g.nlHfv3BRhM3Q1pi3yJ9
 eHmKdraPk5q_WZgChIlSD9rt4e2gtwZhGaRhu.f0TRhCoEDXhhM_zSFy9k7d
 8u61w_vDrIPdhE2Aqm3YqspPtDjjRfG29aXIpYt4LSG1ZO.hj4euaJwtKIr2
 zqQfJDsOM67QvMflBzMJE2gHaiaz0HbPxlV_5qaFcpDwMEEbAWjk2XMfn7QN
 LKYfK6PZ5pEMTCTfaycOR1_qe4VPUAPbmVZP4hxUwSL1VGZIrd6a81Xwb8HI
 LYJxbS5zqUbXRCRqszmXw2n5BVNEn
X-Yahoo-SMTP: 2naF56eswBDuYDy9JW2WHf3pncV9
Message-ID: <5567D04D.6040908@yahoo.com>
Date: Thu, 28 May 2015 22:34:53 -0400
From: Jonathan Wilkes <jancsika@yahoo.com>
User-Agent: Mozilla/5.0 (X11; Linux i686;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <CAD2Ti2-qdymrnM-nHqP2sVBYP=notY6sW54dQ1to-KTbkTEY4A@mail.gmail.com>
 <555E2BFC.6000709@rawbw.com> <20150526233633.GA1790@lo.psyced.org>
 <5565198C.2000701@yahoo.com> <55651A22.4020501@confidantmail.org>
In-Reply-To: <55651A22.4020501@confidantmail.org>
Subject: Re: [tor-talk] Mailpile SMTorP [ref: nexgen P2P email]
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: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On 05/26/2015 09:13 PM, Mike Ingle wrote:
> I tried out Bitmessage and it did not seem to deliver without the 
> sender and recipient online. It's supposed to, it just didn't. Waiting 
> for key exchange.

Any response from the devs/forum when you reported the bug?

> It's also a bandwidth pig due to its broadcast nature.

For those unfamiliar with Bitmessage, it is designed so that everyone 
receives everything.
Within a two-day buffer, at least according to the white paper.

Why does it broadcast in this manner?  Imagine that you wish to read 
blog entries
of your 10 favorite bloggers, but you're afraid because 2 of the 
bloggers may be
considered dangerous by your favorite state-sponsored spy agency.

Let's suppose you can choose one of the following methods to read these 
blogs:
a) read the blogs as web pages, accessing them through Tor
b) read the blogs by subscribing to Bitmessage mailing lists

If you choose Tor and the spy agency has a _full_ view of the network 
traffic, then they
can violate your reading privacy.  They could-- for example-- record you 
as a reader
of the 2 "dangerous" blogs, distinct from users who, say, only read the 
8 "harmless"
blogs.

If you choose to read from Bitmessage mailing list posts and the spy 
agency has
a _full_ view of the network traffic, they cannot violate your reading 
privacy wrt the
2 "dangerous" blogs. They can link you to "suspicious activity" due to using
Bitmessage.  But through traffic analysis alone they cannot separate 
your reading habits
from people who use Bitmessage to only read the 8 "harmless" blogs. To 
them it
just looks like everyone is downloading the same data.  And because 
reading a Bitmessage
mailing list doesn't require _any_ special request back to the network, 
there's no way to tell
from traffic analysis which lists someone happens to be reading.

Bitmessage certainly has its share of issues, but I'm unaware of any 
other extant piece of
software that has a feature like that.

-Jonathan

>>
>> What about Bitmessage?
>>
>> -Jonathan
>>
>>
>

-- 
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

