Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QtlL8-0006kP-76 for bitcoin-development@lists.sourceforge.net; Wed, 17 Aug 2011 18:59:46 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.175 as permitted sender) client-ip=209.85.213.175; envelope-from=sam.revitch@gmail.com; helo=mail-yx0-f175.google.com; Received: from mail-yx0-f175.google.com ([209.85.213.175]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1QtlL7-0007HW-4c for bitcoin-development@lists.sourceforge.net; Wed, 17 Aug 2011 18:59:46 +0000 Received: by yxi19 with SMTP id 19so1231078yxi.34 for ; Wed, 17 Aug 2011 11:59:39 -0700 (PDT) Received: by 10.43.43.129 with SMTP id uc1mr1108842icb.72.1313607574849; Wed, 17 Aug 2011 11:59:34 -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 m21sm563843ibf.42.2011.08.17.11.59.32 (version=SSLv3 cipher=OTHER); Wed, 17 Aug 2011 11:59:33 -0700 (PDT) Message-ID: <4E4C0F93.7000309@gmail.com> Date: Wed, 17 Aug 2011 11:59:31 -0700 From: Sam Revitch 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 References: <4E454C66.4010706@gmail.com> In-Reply-To: <4E454C66.4010706@gmail.com> 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: 1QtlL7-0007HW-4c Subject: Re: [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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2011 18:59:46 -0000 Hello all, The description of the password-protected export format has been revised slightly, and now includes multiple algorithms and a parameter byte for selecting the encryption parameters. As before, the thread is here: https://bitcointalk.org/index.php?topic=36195.0 Unless there is an existing or other planned use for data class 32, or another specific objection, I would like to use it for password-protected private keys. Going by Sipa's description, this would mean that a password-protected private key for bitcoin is type 32, and for the testnet, type 79. Thanks, -Sam Revitch