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; 
Message-ID: <4E4C0F93.7000309@gmail.com>
Date: Wed, 17 Aug 2011 11:59:31 -0700
From: Sam Revitch <sam.revitch@gmail.com>
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>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Bitcoin-development] Password-protected private key export
	format and version bytes
Precedence: list

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