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 ) 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 ; 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: References: <20130507121641.GA11770@netbook.cypherspace.org> Date: Tue, 7 May 2013 15:14:08 +0200 Message-ID: From: Wladimir To: Gavin Andresen 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 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 13:14:16 -0000 --001a11c37536ae916c04dc209700 Content-Type: text/plain; charset=UTF-8 On Tue, May 7, 2013 at 2:28 PM, Gavin Andresen 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 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

On Tue, May 7, 2013 at 2:28 PM, Gavin Andresen <<= a href=3D"mailto:gavinandresen@gmail.com" target=3D"_blank">gavinandresen@g= mail.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 Ba= ck <adam@cypherspace.org> wrote:
Hi

Three minor security/other issues:

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=

2. a button to import a private key (and option to transfer it to another =C2=A0 =C2=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
=C2=A0 =C2=A0address), rather than having to spend the entire wallet onto a= new
=C2=A0 =C2=A0address, just to get BTC off a specific address. =C2=A0Doing i= t that way has
=C2=A0 =C2=A0problems: creates more network traffic/bigger packets, higher = fees (if
=C2=A0 =C2=A0any transactions are young/low confirmation), and generally da= mages
=C2=A0 =C2=A0privacy as all your funds end up linked.

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

Importing private keys into the wallet will not be adde= d as a user-friendly option, as it is dangerous and potentially confusing.<= 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.

Wladimir
=C2=A0

--001a11c37536ae916c04dc209700--