blob: 2aa419e7b255bca0eaa6426c51da66070bb46c7a (
plain)
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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <luke@dashjr.org>) id 1Qe7Xb-0008Vs-JK
for bitcoin-development@lists.sourceforge.net;
Tue, 05 Jul 2011 15:27:59 +0000
X-ACL-Warn:
Received: from zinan.dashjr.org ([173.242.112.54])
by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1Qe7XV-0007sV-RL for bitcoin-development@lists.sourceforge.net;
Tue, 05 Jul 2011 15:27:59 +0000
Received: from ishibashi.localnet (fl-67-77-87-72.dhcp.embarqhsd.net
[67.77.87.72]) (Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id F1EEBD708E8;
Tue, 5 Jul 2011 15:27:47 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Mon, 4 Jul 2011 14:20:07 -0400
User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.2; x86_64; ; )
References: <1309801974.3423.80.camel@Desktop666>
In-Reply-To: <1309801974.3423.80.camel@Desktop666>
X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583
X-PGP-Key-ID: 665FC11DD53E9583
X-PGP-Keyserver: x-hkp://subkeys.pgp.net
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201107041420.08995.luke@dashjr.org>
X-Spam-Score: 0.4 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
0.8 DATE_IN_PAST_12_24 Date: is 12 to 24 hours before Received: date
-0.4 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1Qe7XV-0007sV-RL
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: Tue, 05 Jul 2011 15:27:59 -0000
On Monday, July 04, 2011 1:52:53 PM Matt Corallo wrote:
> There were several suggestions of renaming wallet.dat for encrypted
> wallets. Obviously this has many advantages and disadvantages. It
> breaks backup scripts,
It shouldn't. Backup scripts should make a copy with the JSON-RPC call.
What about changing the format of wallet.dat to something that triggers an
error in the old clients? ie, maybe a dummy crafted-to-make-old-versions-
complain file that simply means "use ewallet.dat"?
|
