On Tue, 31 Mar 2009 10:58:19 +1100 Andrej Falout <[email protected]> wrote:
> And how is that accounting thing going? (re: data privacy on allmydata.com) The latest progress is a half-finished design that I posted to tahoe-dev a few weeks ago, and the associated ticket #666: http://allmydata.org/pipermail/tahoe-dev/2009-March/001471.html http://allmydata.org/trac/tahoe/ticket/666 Comments are most welcome! The next step will be to have a discussion with Zooko about the scheme, since we didn't manage to get the chance to talk about it in person at PyCon last week. One idea he mentioned in particular was wanting to make the "account id" values accept arbitrary-length integers rather than limiting them to something like 64 bits. This would make it easier to use, say, DSA pubkeys as identifiers in the future. The only drawback would be requiring the backend storage format to accomodate arbitrary-length identifiers, but since the current proposal already requires it to tolerate arbitrary-length sequences of fixed-length identifiers, it might not be a significant marginal cost. I can't make too much progress on the actual code until pycryptopp#3 (ECDSA) is done and a new release of pycryptopp is out. I can do some prep work, but I can't really run tests or commit anything until we've got an ECDSA serialization format that we can stick with. http://allmydata.org/trac/pycryptopp/ticket/3 cheers, -Brian _______________________________________________ tahoe-dev mailing list [email protected] http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
