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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <adam.back@gmail.com>) id 1UZgpB-0007uy-Hz
for bitcoin-development@lists.sourceforge.net;
Tue, 07 May 2013 12:16:53 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.83.43 as permitted sender)
client-ip=74.125.83.43; envelope-from=adam.back@gmail.com;
helo=mail-ee0-f43.google.com;
Received: from mail-ee0-f43.google.com ([74.125.83.43])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UZgp9-00011m-MC
for bitcoin-development@lists.sourceforge.net;
Tue, 07 May 2013 12:16:53 +0000
Received: by mail-ee0-f43.google.com with SMTP id b15so269959eek.30
for <bitcoin-development@lists.sourceforge.net>;
Tue, 07 May 2013 05:16:45 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=x-received:date:from:to:cc:subject:message-id:mime-version
:content-type:content-disposition:user-agent:x-hashcash:x-hashcash;
bh=jhSiKYve9FLH++Oc/y9FzP2aVD4D4oPzKuInG9G6qF8=;
b=HKJByHLWxwA3ehH5zPFMATioaTyjTXCHBoM9Yw6dyWjuApHHzpWye92FPJZX8eJrnb
dFc67bdVCWNQSlR+EBPqPbwDz/CXYXnGXJEXE+UFRskFrZXjm1NMTiFH/gfK16drjyXZ
2D84rrNBzoZwltbCxjkKn1AzVBSfTTojMeSpzg3cOAiODaXb6LBOv8gKLepirWYBI1pj
05FNGE04pmqeBD8D1Bu/IOgttQ+WMk6RtofgFdE6goNAhAQmmxNNedWiPihEYt6fHR35
r8UyTL+pvwjnx6317r6i4hMfDlFTk/sAw75HYs73WNIKaeIjh8m+d2+mNYQWV35sKDDy
wfBg==
X-Received: by 10.14.214.3 with SMTP id b3mr4875201eep.24.1367929005235;
Tue, 07 May 2013 05:16:45 -0700 (PDT)
Received: from netbook (c83-90.i07-21.onvol.net. [92.251.83.90])
by mx.google.com with ESMTPSA id
w52sm38981671eev.12.2013.05.07.05.16.43
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1.1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Tue, 07 May 2013 05:16:44 -0700 (PDT)
Received: by netbook (Postfix, from userid 1000)
id 736532E0619; Tue, 7 May 2013 14:16:42 +0200 (CEST)
Received: by flare (hashcash-sendmail, from uid 1000);
Tue, 7 May 2013 14:16:42 +0200
Date: Tue, 7 May 2013 14:16:41 +0200
From: Adam Back <adam@cypherspace.org>
To: Bitcoin-Dev <bitcoin-development@lists.sourceforge.net>
Message-ID: <20130507121641.GA11770@netbook.cypherspace.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Hashcash: 1:20:130507:bitcoin-development@lists.sourceforge.net::rj/RhAYtjUmEZ
JzG:000000000000000000001Rws
X-Hashcash: 1:20:130507:adam@cypherspace.org::JaBeXVMvhta3GX9/:00000000000000000
0000000000000000000000000EEX
X-Spam-Score: -1.5 (-)
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
(adam.back[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1UZgp9-00011m-MC
Subject: [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 12:16:53 -0000
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.
Stop reading here if thats clear.. below is how those scenarios happened
which I think are common enough.
So someone sent me a small BTC donation by emailing me the private key, as I
had no bitcoin address. So naturally I need to move the funds off the
private key, or they could spend it under me.
I had another small amount on a self-controlled private key in the wallet
via a reddit tip (.05BTC tip payed to self-controlled key became .0498BTC).
So I went through the debug->console unlock wallet (password in cleartext on
screen? yuck), then importpriv key, process and that worked, though not
particularly intuitive - could do with an "import key" button?
Then I wanted to take the .01 BTC off the private key and the FAQs etc seem
to suggest that the only way to do it is to spend our entire balance (from
all keys) onto a new address. Not exactly what I wanted, but I did it
anyway and the tx fee goes up from .0001 which I set it to to .0005 because
the transaction was young, to avoid network flooding. Even though
transaction I actually wanted to move (on the non self-controlled key had a
big heap of confirmations and so could've been .0001 tx fee).
Would be kind of handy to be able to select the key to empty without having
to empty the entire wallet into a new key... (Smaller transaction KB on the
network, less fees for the user, less confusing).
Maybe theres a way to do it, eg via the console again, but I didnt find it;
and it's surely common enough that it could do with being another button or
right click option. eg I could've setup another wallet instance but thats
rather indirect.
Adam
|
