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
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
|
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 <laanwj@gmail.com>) id 1UZhii-0002YW-0G
for bitcoin-development@lists.sourceforge.net;
Tue, 07 May 2013 13:14:16 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.50 as permitted sender)
client-ip=209.85.214.50; envelope-from=laanwj@gmail.com;
helo=mail-bk0-f50.google.com;
Received: from mail-bk0-f50.google.com ([209.85.214.50])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UZhih-0006F7-3i
for bitcoin-development@lists.sourceforge.net;
Tue, 07 May 2013 13:14:15 +0000
Received: by mail-bk0-f50.google.com with SMTP id ik5so282290bkc.9
for <bitcoin-development@lists.sourceforge.net>;
Tue, 07 May 2013 06:14:08 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.204.57.142 with SMTP id c14mr584705bkh.7.1367932448693; Tue,
07 May 2013 06:14:08 -0700 (PDT)
Received: by 10.204.37.203 with HTTP; Tue, 7 May 2013 06:14:08 -0700 (PDT)
In-Reply-To: <CABsx9T10Gdzt_7RQK-Jv9fc6GEesj8nmxkGy=f_5j-Np09958Q@mail.gmail.com>
References: <20130507121641.GA11770@netbook.cypherspace.org>
<CABsx9T10Gdzt_7RQK-Jv9fc6GEesj8nmxkGy=f_5j-Np09958Q@mail.gmail.com>
Date: Tue, 7 May 2013 15:14:08 +0200
Message-ID: <CA+s+GJBbRwueBvaXcYMgM0b_LeChbDcBA0HQHQP9CvjnXzXhLg@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c37536ae916c04dc209700
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
(laanwj[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: 1UZhih-0006F7-3i
Cc: Bitcoin-Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] minor bitcoin-qt gripes moving BTC off
specific key
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, 07 May 2013 13:14:16 -0000
--001a11c37536ae916c04dc209700
Content-Type: text/plain; charset=UTF-8
On Tue, May 7, 2013 at 2:28 PM, Gavin Andresen <gavinandresen@gmail.com>wrote:
> "sweep private key" is the missing functionality.
>
> I agree, it would be nice to have.
>
>
> On Tue, May 7, 2013 at 8:16 AM, Adam Back <adam@cypherspace.org> wrote:
>
>> Hi
>>
>> Three minor security/other issues:
>>
>> 1. please a way to unlock the wallet without displaying wallet password in
>> console screen (console unlock wallet, to import priv key); or
>>
>> 2. a button to import a private key (and option to transfer it to another
>> key - if you are not the sole controller the private key)
>>
>> 3. a UX way to transfer BTC off a specific adress (eg choose from
>> address), rather than having to spend the entire wallet onto a new
>> address, just to get BTC off a specific address. Doing it that way has
>> problems: creates more network traffic/bigger packets, higher fees (if
>> any transactions are young/low confirmation), and generally damages
>> privacy as all your funds end up linked.
>>
>
Yes, sweep (send all the coins from this addresses to me) should certainly
be added. Maybe even a way to do it periodically, though but that would
require remembering the key.
Importing private keys into the wallet will not be added as a user-friendly
option, as it is dangerous and potentially confusing.
As for (1), I think a better solution would to add a list of commands whose
arguments are censored in the console screen and command line history. At
least `importprivkey`, `walletpassphrase`, `walletpassphrasechange` should
likely be in that list.
Wladimir
--001a11c37536ae916c04dc209700
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Tue, May 7, 2013 at 2:28 PM, Gavin Andresen <span dir=3D"ltr"><<=
a href=3D"mailto:gavinandresen@gmail.com" target=3D"_blank">gavinandresen@g=
mail.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">"sweep private key" is the missing functionality=
.<div>
<br></div><div>I agree, it would be nice to have.<br><div><div class=3D"im"=
><br><br><div class=3D"gmail_quote">On Tue, May 7, 2013 at 8:16 AM, Adam Ba=
ck <span dir=3D"ltr"><<a href=3D"mailto:adam@cypherspace.org" target=3D"=
_blank">adam@cypherspace.org</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">Hi<br>
<br>
Three minor security/other issues:<br>
<br>
1. please a way to unlock the wallet without displaying wallet password in<=
br>
=C2=A0 =C2=A0console screen (console unlock wallet, to import priv key); or=
<br>
<br>
2. a button to import a private key (and option to transfer it to another<b=
r>
=C2=A0 =C2=A0key - if you are not the sole controller the private key)<br>
<br>
3. a UX way to transfer BTC off a specific adress (eg choose from<br>
=C2=A0 =C2=A0address), rather than having to spend the entire wallet onto a=
new<br>
=C2=A0 =C2=A0address, just to get BTC off a specific address. =C2=A0Doing i=
t that way has<br>
=C2=A0 =C2=A0problems: creates more network traffic/bigger packets, higher =
fees (if<br>
=C2=A0 =C2=A0any transactions are young/low confirmation), and generally da=
mages<br>
=C2=A0 =C2=A0privacy as all your funds end up linked.<br></blockquote></div=
></div></div></div></blockquote><div><br></div><div>Yes, sweep (send all th=
e coins from this addresses to me) should certainly be added. Maybe even a =
way to do it periodically, though but that would require remembering the ke=
y.=C2=A0</div>
<div><br></div><div>Importing private keys into the wallet will not be adde=
d as a user-friendly option, as it is dangerous and potentially confusing.<=
div><br></div><div>As for (1), I think a better solution would to add a lis=
t of commands whose arguments are censored in the console screen and comman=
d line history. At least `importprivkey`, `walletpassphrase`, `walletpassph=
rasechange` should likely be in that list.<br>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Wladimir<br=
></div></div></div><div>=C2=A0</div><div><br></div></div></div></div></div>
--001a11c37536ae916c04dc209700--
|
