[tahoe-dev] [pycryptopp] #3: serialize ecdsa keys without the fluff

[pycryptopp]

#3: serialize ecdsa keys without the fluff
-----------------------------+----------------------------------------------
     Reporter:  zooko        |      Owner:  zooko   
         Type:  enhancement  |     Status:  reopened
     Priority:  major        |    Version:  0.4.0   
   Resolution:               |   Keywords:          
Launchpad_bug:               |  
-----------------------------+----------------------------------------------

Comment(by zooko):

 Here's a patch from my sandbox that does this as well as #2 (deterministic
 generation of private key from small seed).  There are a few problems with
 this patch:

 1.  There's something terribly wrong with the memory management, so that
 it segfaults.  I'm pretty sure that this has to do with my attempt to
 embed a C++ object (defined by a Crypto++ class) directly into a Python
 object (a struct that starts with the Python object header fields).  The
 motivation for this is improved efficiency and (ha!) safer memory
 management.  I intend to separate out this attempt from the rest of the
 patch and try to make it work without that feature.

 2.  It builds its own deterministic key generation RNG using Tiger.
 Recently on the cryptopp mailing list Wei Dai explained that a stream
 cipher such as AES-CTR can be used as an RNG, although I'm afraid it might
 work only in the newest, not-yet-released version of Crypto++:
 http://groups.google.com/group/cryptopp-
 users/browse_thread/thread/9e02130e55988500#

-- 
Ticket URL: <http://allmydata.org/trac/pycryptopp/ticket/3#comment:9>
pycryptopp <http://allmydata.org/trac/pycryptopp>
Python bindings for the Crypto++ library