[tahoe-dev] [tahoe-lafs] #466: extendable Introducer protocol: dictionary-based, signed announcements

[tahoe-lafs]

#466: extendable Introducer protocol: dictionary-based, signed announcements
------------------------------+---------------------------------------------
     Reporter:  warner        |       Owner:  nejucomo                                                                                
         Type:  enhancement   |      Status:  new                                                                                     
     Priority:  major         |   Milestone:  undecided                                                                               
    Component:  code-network  |     Version:  1.1.0                                                                                   
   Resolution:                |    Keywords:  introduction forward-compatibility performance accounting ecdsa pycryptopp review-needed
Launchpad Bug:                |  
------------------------------+---------------------------------------------
Changes (by nejucomo):

  * owner:  => nejucomo


Comment:

 I've begun a review of this ticket.  Some initial questions from the first
 design comment follow.  I may answer some of these by reading the patch
 and the trunk version.

 Q1. Why does the design specify EC-DSA-192?  What are the requirements
 which drive this algorithm selection?

 Zooko suggested on IRC that the primary goal is small public keys.


 Q2. Why is the pubkey-identifier optional?  What use case does this
 facilitate?


 Q3. If the identifier is absent, verification is checked against all "root
 certs".  How are these managed?

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/466#comment:14>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage