Delivery-Date: Fri, 29 May 2015 17:57:20 -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 BEDE81E12FF;
	Fri, 29 May 2015 17:57:18 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id DA5FA34B8B;
	Fri, 29 May 2015 21:57:13 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 3A89934B89
 for <tor-talk@lists.torproject.org>; Fri, 29 May 2015 21:57:10 +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 rsPKwkKflEpH for <tor-talk@lists.torproject.org>;
 Fri, 29 May 2015 21:57:10 +0000 (UTC)
Received: from nm16.bullet.mail.bf1.yahoo.com (nm16.bullet.mail.bf1.yahoo.com
 [98.139.212.175])
 (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 0F3AD3213E
 for <tor-talk@lists.torproject.org>; Fri, 29 May 2015 21:57:09 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048;
 t=1432936626; bh=mIpYjrf6sZ8OK8ij1I8NpT6rQtXkfDnYlZ/CCFu8rfc=;
 h=Date:From:To:Subject:References:In-Reply-To:From:Subject;
 b=PA/gS7qxnJNA3glmmuG2arZrcMpgiMLnDYBpm85jTKpAdNHjslzP0FnsxKioNCbR8Q+ysy6N6kWziFZS6ZHA4iCkCyNRo4xiuuu/NRytxcmrd7cv/AyNX2Go/hBQ+QNTot/BcRghT3hwhTHgRCI+y/cosfjT9jEKQlN/Mad/AqPQHLklrc6Kbs9/SxyZZhQxKtNYbr6394LJWC5Vo+eud435h9Mzn4aBAb/1Fl49mq9vQ69vnGmuHcW5a87uVtqg17xI1AtYDmPs3SZR9PaWu5RyjtbZE2ExGZXWoBPL+1ScVm2zCAjR587J6Qli9ayM2paOz/OL0Gw5AVCE/o8R0g==
Received: from [98.139.170.178] by nm16.bullet.mail.bf1.yahoo.com with NNFMP;
 29 May 2015 21:57:06 -0000
Received: from [98.139.213.10] by tm21.bullet.mail.bf1.yahoo.com with NNFMP;
 29 May 2015 21:57:06 -0000
Received: from [127.0.0.1] by smtp110.mail.bf1.yahoo.com with NNFMP;
 29 May 2015 21:57:06 -0000
X-Yahoo-Newman-Id: 680629.65946.bm@smtp110.mail.bf1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: iFgRcOgVM1nBKMH4F0pF.Ik5EQvB3uK8jfZysOzdNuznkyc
 ZH0HgYFlJnZaDNiDnmh579mORkI28ZbNTcMZ.9_hEDf8HsybpYpKAaLEY9Nb
 qpGjxgnudHE0_mp985ZuONnrQ..8ectRcN1hN1sQrZUwvUNtG_4C0xF8rCcM
 CYFrlDDrbqHAHLgP.SFLkobkvgTlLLVKYbymrC.O7pNZm2WY5rvol6qokRlK
 cTZ9hqMWJhmmk7bFJCoPI5dBkzAMzHfzQjYuIjCcg.bEKTkZq1k4_KdoFWDu
 gRjnCj2HT0fyxyLjjKSjzIagE4K7.kpwIDLmo_WCgT_78kg33E2ezwW_zmYF
 e4SYCAWVJt4j4VbTX3G6RxQTOu0wswHbVPi05pH2HfLBreVPVaG6L2rDHqVC
 y8IhC_FEWFQc_KMkGHgQifPzlxklxn_cJGzdiGfV1ZQukhWzcz4.J.Cn1E4X
 5NC.yVefFpYjJxiAGJuFDsQI.ri4ComuNKJzOq.jiq7zPHje38xewan0Kf6D
 6h4.mKmDzZFuR_NeppvD6MuL3xN2A
X-Yahoo-SMTP: 2naF56eswBDuYDy9JW2WHf3pncV9
Message-ID: <5568E0B0.3020105@yahoo.com>
Date: Fri, 29 May 2015 17:57:04 -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>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
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 5/28/2015 7:34 PM, Jonathan Wilkes wrote:
 >> 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?

 >I would have had to do a lot more troubleshooting before I went and
 >complained about a bug. I was just testing it out between a couple of
 >VMs to understand how it works and feels, because I am working with
 >secure mail protocols and want to understand the existing ones. It
 >worked fine with both of them up simultaneously.

It's hard to say anything more without details.  Except that offline 
delivery
within the two-day buffer is a core feature described in the white-paper
and included in the implementation since the first release.

 >This is pretty similar to receiving a Usenet feed in the old days, and
 >downloading all the messages so as to receive a few encrypted ones. That
 >makes for the best recipient privacy, at the cost of bandwidth. From
 >what I can tell, Bitmessage basically automates that process.

No, not "Bitmessage", but "the specific use-case for a feature that I
happen to understand and mentioned on this list."

 > If it
 >moved beyond the Darknet Markets crowd, success would kill it or at
 >least require compromising the broadcast-everything rule.

I'll just ask you straight up-- are you talking about broadcast-everything
systems in general, or are you giving an assessment of Bitmessage's 
design and
implementation based on (at least) a thorough reading of the 5 page 
whitepaper?

(Confidential to cryptography list lurkers: IMO we have plenty of Ben 
Lauries
at this point, and could use a lot more Hal Finneys. :)

-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

