1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <drwho@virtadpt.net>) id 1V9LQe-00062R-RQ
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Aug 2013 20:42:56 +0000
X-ACL-Warn:
Received: from mail-vc0-f182.google.com ([209.85.220.182])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1V9LQb-0004pj-BY
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Aug 2013 20:42:56 +0000
Received: by mail-vc0-f182.google.com with SMTP id hf12so4394241vcb.13
for <bitcoin-development@lists.sourceforge.net>;
Tue, 13 Aug 2013 13:42:46 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=x-gm-message-state:message-id:date:from:reply-to:organization
:user-agent:mime-version:to:subject:references:in-reply-to:openpgp
:content-type:content-transfer-encoding;
bh=uxCZEIJY9gjrygEBEdFFpnPuO7G/BLs3BrLO5NYdQSw=;
b=Pcv8NyosWl+ClDtDVQ0Bcj8Em3E5gwSkP4ls4k15+TO3K5FiycpNy+BZ/A8HYrjy+O
Ky94HOanF32Xl1W1rKTFawH5Z65urTX8vy6tCft52xoZNLCY1Qm2NZ62Di4S+iUFHA03
bBofcPOTqrQ5iJgSDsfKTChuangGRl3XViAJtYpMbnZW3ASqnk4lD7mzLwgmIvor5ZP0
VBcl6Cjni1S8hlU7Boglm3Mj59Pitmx7kazDUFC4LohHofgbqUpIiyNtjukFJYD8RUhT
02ZiGZSrgpaTWO9QCHKHDr9rSZIrt1wZVxDBoDkMlnzIsuztRfW8Hdg6XSf0orO6jeN1
69SQ==
X-Gm-Message-State: ALoCoQmTsL2MTQ7AFz6NwLwrpeZ0ZJp7AakBSfd+6y5rHEAikG1UNbh1hMiIA5ZIKHQNxQCBbXpI
X-Received: by 10.58.208.130 with SMTP id me2mr5913178vec.13.1376424927989;
Tue, 13 Aug 2013 13:15:27 -0700 (PDT)
Received: from windbringer.virtadpt.net
(static-108-18-135-163.washdc.fios.verizon.net. [108.18.135.163])
by mx.google.com with ESMTPSA id m5sm24505432qaa.13.2013.08.13.13.15.27
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Tue, 13 Aug 2013 13:15:27 -0700 (PDT)
Message-ID: <520A93DE.8080409@virtadpt.net>
Date: Tue, 13 Aug 2013 16:15:26 -0400
From: The Doctor <drwho@virtadpt.net>
Organization: Virtual Adept Networks, Unlimited
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:17.0) Gecko/20130514 Thunderbird/17.0.6
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CAEvNM8=zeunvnGBNgjAgs-e9oiTONy1mYOLgA=5DEHK8VUizxw@mail.gmail.com>
In-Reply-To: <CAEvNM8=zeunvnGBNgjAgs-e9oiTONy1mYOLgA=5DEHK8VUizxw@mail.gmail.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=807B17C1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1V9LQb-0004pj-BY
Subject: Re: [Bitcoin-development] BitMail.sf.net - encrypted p2p email
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: drwho@virtadpt.net
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 20:42:57 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/09/2013 03:01 PM, Randolph D. wrote:
> anyone tested the secure encrypted p2p email:
> http://bitmail.sf.net
Not lately. It's pretty CPU and network intensive, which may or may
not be detrimental to your use case.
I keep meaning to read through these security analyses of Bitmessage
but I'm a little short on compute cycles at the moment:
https://bitmessage.org/forum/index.php?topic=1666.0
http://www.reddit.com/r/bitmessage/comments/1fwyx7/a_security_analysis_of_bitmessage/
- --
The Doctor [412/724/301/703] [ZS]
Developer, Project Byzantium: http://project-byzantium.org/
PGP: 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F DD89 3BD8 FF2B 807B 17C1
WWW: https://drwho.virtadpt.net/
If at first you don't succeed, call for an airstrike.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlIKk94ACgkQO9j/K4B7F8FMsgCgkuM56fI4hVT9H1ueZSFwl9Kk
qRoAoJkKZf4afKgVQKtDO6zRd/Auc/RV
=zwmX
-----END PGP SIGNATURE-----
|
