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
|
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 <gmaxwell@gmail.com>) id 1Qdrek-0006wZ-QW
for bitcoin-development@lists.sourceforge.net;
Mon, 04 Jul 2011 22:30:18 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.47 as permitted sender)
client-ip=209.85.216.47; envelope-from=gmaxwell@gmail.com;
helo=mail-qw0-f47.google.com;
Received: from mail-qw0-f47.google.com ([209.85.216.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Qdrej-0000FK-VW
for bitcoin-development@lists.sourceforge.net;
Mon, 04 Jul 2011 22:30:18 +0000
Received: by qwh5 with SMTP id 5so3489775qwh.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 04 Jul 2011 15:30:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.241.205 with SMTP id lf13mr848340qcb.292.1309818612460;
Mon, 04 Jul 2011 15:30:12 -0700 (PDT)
Received: by 10.229.83.196 with HTTP; Mon, 4 Jul 2011 15:30:12 -0700 (PDT)
In-Reply-To: <5196CA67-B84A-4413-BE6D-504811EAA954@jrbobdobbs.org>
References: <1309801974.3423.80.camel@Desktop666>
<CABsx9T31ZuQHKwcNnb9-NpaCA6c43PXVZ+Tc+GZ=2Wkz08enHw@mail.gmail.com>
<5196CA67-B84A-4413-BE6D-504811EAA954@jrbobdobbs.org>
Date: Mon, 4 Jul 2011 18:30:12 -0400
Message-ID: <CAAS2fgSNdnT+7qvBRnqMTG3Pnciw+U81GhgaTD9=-7bdpPyiFQ@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Douglas Huff <dhuff@jrbobdobbs.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.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
(gmaxwell[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-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: 1Qdrej-0000FK-VW
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Encrypted Wallet Backward Compatibility
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: Mon, 04 Jul 2011 22:30:18 -0000
On Mon, Jul 4, 2011 at 5:18 PM, Douglas Huff <dhuff@jrbobdobbs.org> wrote:
>
> On Jul 4, 2011, at 1:23 PM, Gavin Andresen wrote:
>> RE: breaking backup scripts: =C2=A0if they use the backupwallet =C2=A0RP=
C
>> command, then they will Just Work.
>
> I'd go a step further and say that, since import/export is planned to get=
merged at about the same time, intentionally breaking unsafe/badly designe=
d backup mechanisms is actually desirable.
Silently breaking them, not so much.
Or do you think people are going to notice that they've started
backing up a zero byte file?
|
