Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bluematt.me
	designates 208.79.240.5 as permitted sender)
	client-ip=208.79.240.5; envelope-from=bitcoin-list@bluematt.me;
	helo=smtpauth.rollernet.us; 
From: Matt Corallo <bitcoin-list@bluematt.me>
To: bitcoin-development@lists.sourceforge.net
In-Reply-To: <41C9602E-0234-4357-9B75-E0A4DA65B117@jrbobdobbs.org>
References: <BANLkTin=_y_GGFO0JT9Z8jdmGwGEm7Yrvw@mail.gmail.com>
	<41C9602E-0234-4357-9B75-E0A4DA65B117@jrbobdobbs.org>
Content-Type: multipart/signed; micalg="pgp-sha1";
	protocol="application/pgp-signature";
	boundary="=-S0v8fpkBWRHfN+MCnK0V"
Date: Tue, 28 Jun 2011 21:50:28 +0200
Message-ID: <1309290628.3689.9.camel@Desktop666>
Mime-Version: 1.0
Subject: Re: [Bitcoin-development] satoshi client v0.4 priorities
Precedence: list


--=-S0v8fpkBWRHfN+MCnK0V
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I believe he meant rebase onto wallet encryption.

On Tue, 2011-06-28 at 13:39 -0500, Doug Huff wrote:
> sipa already rebased his showwallet tree. It's missing the segfault fix (=
or was yesterday) but said fix merges cleanly. I'm not entirely sure it's r=
eady for pulling but it is in a functional state.
>=20
> On Jun 28, 2011, at 12:48 PM, Jeff Garzik wrote:
>=20
> > (copying part of a conversation from IRC)
> >=20
> > IMO, wallet crypto and wallet import/export are the two "must have"
> > features for v0.4.  wallet crypto rationale is obvious.  sipa's wallet
> > import/export might need a rebase, but it seems important for further
> > wallet security, such as printing out and storing a private key in a
> > bank's safety deposit box.
> >=20
> > autotools and other stuff can wait, if they hold up the release of
> > wallet crypto.
> >=20
> > --=20
> > Jeff Garzik
> > exMULTI, Inc.
> > jgarzik@exmulti.com
> >=20
> > -----------------------------------------------------------------------=
-------
> > All of the data generated in your IT infrastructure is seriously valuab=
le.
> > Why? It contains a definitive record of application performance, securi=
ty=20
> > threats, fraudulent activity, and more. Splunk takes this data and make=
s=20
> > sense of it. IT sense. And common sense.
> > http://p.sf.net/sfu/splunk-d2d-c2
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>=20
> -------------------------------------------------------------------------=
-----
> All of the data generated in your IT infrastructure is seriously valuable=
.
> Why? It contains a definitive record of application performance, security=
=20
> threats, fraudulent activity, and more. Splunk takes this data and makes=
=20
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________ Bitcoin-development maili=
ng list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge=
.net/lists/listinfo/bitcoin-development


--=-S0v8fpkBWRHfN+MCnK0V
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAABAgAGBQJOCjB4AAoJEBrh01BD4I5UxaoP/jITR25ZVIjFXc+4XY8ZZOxk
EZ+zFP+OPT4cRmrYkGgdQ1hrVUaCuq5NDNoCKrgcLLjhbRqKku2Q9j0X1Yfa/6Zn
pPK1L5+PvPFDXPwMFb6HSPJDFRaG42wYgpKY/5GNyo1RDrYnQQwPiKctPcAG+Wmv
sGTuB7X8oS6/ZDfQN9lxd9BUGyVfDmSg4bM5FnDOLUbs6bBTVa/gQ+hP3BR9ZfdA
VOyf3KFyXoLOVmE7RAsxA4UEyRWWZxtJExa/eFoz/VAQaMxZvA/8T9scOVhKwMsL
a6B1ZAxUx8HPcWYKomBmBDDt4o6QUjWnHyvpRoW5QjkYpf3f5OtGaEUfqSi30FWo
qKJYpfWwY2GSG49KDP7dUSDqJyLS7M1xNKCimn0MKezw8+ZLiQjkis4dOE+rQmKC
QIA/fYNTBuqTERkvfTdcdLf7V9UiJmK5FLfoW/ME259vrzX8o7sYb3f9nkY2Z1eY
MqQT1NxvRtFfxlh+4KcdPxRKX89eD6CXr6xAMfnx/4bHwaMEEw2fTHr63oJ7JhMK
MkCKHHeu7OQImkSU9CODQoRcd0ep4SLAgH5EmFAA+7hgBXBGPgi6hw8fIeloNY4a
wixXiDYEDEQPbTt5EFMyorN0BB5hbp1A0ahVxCHGhPDwEMc98Gnrb3MPI/9a7T2/
bqfP5Bi6s6d2MZVbygfV
=XAbG
-----END PGP SIGNATURE-----

--=-S0v8fpkBWRHfN+MCnK0V--