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
106
107
108
109
110
111
|
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 <etotheipi@gmail.com>) id 1UIlL5-0004VX-Js
for bitcoin-development@lists.sourceforge.net;
Thu, 21 Mar 2013 19:39:51 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.178 as permitted sender)
client-ip=209.85.214.178; envelope-from=etotheipi@gmail.com;
helo=mail-ob0-f178.google.com;
Received: from mail-ob0-f178.google.com ([209.85.214.178])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UIlL4-0006fs-Pn
for bitcoin-development@lists.sourceforge.net;
Thu, 21 Mar 2013 19:39:51 +0000
Received: by mail-ob0-f178.google.com with SMTP id wd20so3297885obb.9
for <bitcoin-development@lists.sourceforge.net>;
Thu, 21 Mar 2013 12:39:45 -0700 (PDT)
X-Received: by 10.60.20.225 with SMTP id q1mr7588739oee.31.1363894785439;
Thu, 21 Mar 2013 12:39:45 -0700 (PDT)
Received: from [192.168.1.85] (c-76-111-96-126.hsd1.md.comcast.net.
[76.111.96.126])
by mx.google.com with ESMTPS id 4sm8534419obj.7.2013.03.21.12.39.44
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Thu, 21 Mar 2013 12:39:44 -0700 (PDT)
Message-ID: <514B61EB.8060201@gmail.com>
Date: Thu, 21 Mar 2013 15:39:23 -0400
From: Alan Reiner <etotheipi@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/alternative;
boundary="------------040502030101060507040905"
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(etotheipi[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1UIlL4-0006fs-Pn
Subject: [Bitcoin-development] New webpage: Offline Backups
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
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: Thu, 21 Mar 2013 19:39:51 -0000
This is a multi-part message in MIME format.
--------------040502030101060507040905
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
I noticed the new webpage is up on bitcoin.org. I still have mixed
feelings about it, but I noticed there is a "You need to know!" section
that suggests offline backups.
As long as you are featuring Armory and Electrum on the "wallets" page,
you should be including them in that blurb as options for offline
storage. It's kind of silly to say "/You must do this! But we have no
recommendations for how. At all. Good luck/!" At least have a
dedicated page or (not-ideally, forum post) describing the various
options and leads for them to follow for actually doing it.
-Alan
--------------040502030101060507040905
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I noticed the new webpage is up on bitcoin.org. I still have mixed
feelings about it, but I noticed there is a "You need to know!"
section that suggests offline backups.<br>
<br>
As long as you are featuring Armory and Electrum on the "wallets"
page, you should be including them in that blurb as options for
offline storage. It's kind of silly to say "<i>You must do this!
But we have no recommendations for how. At all. Good luck</i>!"
At least have a dedicated page or (not-ideally, forum post)
describing the various options and leads for them to follow for
actually doing it. <br>
<br>
-Alan<br>
</body>
</html>
--------------040502030101060507040905--
|
