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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <sam.revitch@gmail.com>) id 1Qru2y-00070u-5V
for bitcoin-development@lists.sourceforge.net;
Fri, 12 Aug 2011 15:53:20 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.47 as permitted sender)
client-ip=209.85.213.47; envelope-from=sam.revitch@gmail.com;
helo=mail-yw0-f47.google.com;
Received: from mail-yw0-f47.google.com ([209.85.213.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1Qru2x-0001ae-AB
for bitcoin-development@lists.sourceforge.net;
Fri, 12 Aug 2011 15:53:20 +0000
Received: by ywe9 with SMTP id 9so2551411ywe.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 12 Aug 2011 08:53:14 -0700 (PDT)
Received: by 10.42.133.69 with SMTP id g5mr1004400ict.112.1313164393826;
Fri, 12 Aug 2011 08:53:13 -0700 (PDT)
Received: from [172.16.0.16] (c-24-20-45-229.hsd1.or.comcast.net
[24.20.45.229])
by mx.google.com with ESMTPS id 3sm2389621ibm.61.2011.08.12.08.53.12
(version=SSLv3 cipher=OTHER); Fri, 12 Aug 2011 08:53:12 -0700 (PDT)
Message-ID: <4E454C66.4010706@gmail.com>
Date: Fri, 12 Aug 2011 08:53:10 -0700
From: Sam Revitch <sam.revitch@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
rv:1.9.2.17) Gecko/20110501 Lightning/1.0b3pre Thunderbird/3.1.10
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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
(sam.revitch[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
0.0 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service
X-Headers-End: 1Qru2x-0001ae-AB
Subject: [Bitcoin-development] Password-protected private key export format
and version bytes
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: Fri, 12 Aug 2011 15:53:20 -0000
Hi folks,
I've been working on a new private key export format that includes
simple password-protection. Details of the scheme are posted at:
https://bitcointalk.org/index.php?topic=36195.0
It is intended as an interchange format, not specifically integrated
with wallet encryption, and simple enough to be produced by the
vanitygen program. Importing to the official bitcoin client using a
method like the import/export patch would require the user to provide
the password of the private key, in addition to the wallet password if
the wallet is encrypted.
Comments on the format are welcomed!
As the proposed format is base-58, I would like to make a request to use
one of the data classes as proposed by Pieter Wuille about a month ago:
http://sourceforge.net/mailarchive/forum.php?thread_name=20110708092506.GA6641%40ulyssis.org&forum_name=bitcoin-development
If this doesn't fit with the general bitcoin development agenda, that's
OK too, but I would like to explore some possibility for a protected
export format for private keys.
Thanks,
-Sam Revitch
|
