From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UZh0J-0000P0-FZ for bitcoin-development@lists.sourceforge.net; Tue, 07 May 2013 12:28:23 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.45 as permitted sender) client-ip=74.125.82.45; envelope-from=gavinandresen@gmail.com; helo=mail-wg0-f45.google.com; Received: from mail-wg0-f45.google.com ([74.125.82.45]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UZh0H-0001eE-HJ for bitcoin-development@lists.sourceforge.net; Tue, 07 May 2013 12:28:23 +0000 Received: by mail-wg0-f45.google.com with SMTP id l18so557425wgh.24 for ; Tue, 07 May 2013 05:28:15 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.188.141 with SMTP id ga13mr14558802wic.9.1367929695255; Tue, 07 May 2013 05:28:15 -0700 (PDT) Received: by 10.194.76.106 with HTTP; Tue, 7 May 2013 05:28:15 -0700 (PDT) In-Reply-To: <20130507121641.GA11770@netbook.cypherspace.org> References: <20130507121641.GA11770@netbook.cypherspace.org> Date: Tue, 7 May 2013 08:28:15 -0400 Message-ID: From: Gavin Andresen To: Adam Back Content-Type: multipart/alternative; boundary=001a11c37f5a90452a04dc1ff329 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 (gavinandresen[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: 1UZh0H-0001eE-HJ Cc: Bitcoin-Dev 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 May 2013 12:28:23 -0000 --001a11c37f5a90452a04dc1ff329 Content-Type: text/plain; charset=ISO-8859-1 "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 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. > -- -- Gavin Andresen --001a11c37f5a90452a04dc1ff329 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable "sweep private key" is the missing functionality.

<= div>I agree, it would be nice to have.


On Tue, May 7, 2013 at 8:16 AM, Adam Back <adam@cypherspace.org<= /a>> wrote:
Hi

Three minor security/other issues:

1. please a way to unlock the wallet without displaying wallet password in<= br> =A0 =A0console screen (console unlock wallet, to import priv key); or

2. a button to import a private key (and option to transfer it to another =A0 =A0key - if you are not the sole controller the private key)

3. a UX way to transfer BTC off a specific adress (eg choose from
=A0 =A0address), rather than having to spend the entire wallet onto a new =A0 =A0address, just to get BTC off a specific address. =A0Doing it that wa= y has
=A0 =A0problems: creates more network traffic/bigger packets, higher fees (= if
=A0 =A0any transactions are young/low confirmation), and generally damages<= br> =A0 =A0privacy as all your funds end up linked.
-- --
Gavin Andresen
--001a11c37f5a90452a04dc1ff329--