[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3774: Specify how the lease renew secret is derived to the GBS specification document

[Tahoe-LAFS]

#3774: Specify how the lease renew secret is derived to the GBS specification
document
-------------------------+-----------------------------------
     Reporter:  exarkun  |      Owner:  exarkun
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  HTTP Storage Protocol
    Component:  unknown  |    Version:  n/a
   Resolution:           |   Keywords:
Launchpad Bug:           |
-------------------------+-----------------------------------

Comment (by itamarst):

 Right now the renew secret is derived from a number of items that won't
 change, but also from the Foolscap server Tub ID (this is the "lease
 seed").

 We talked about for the HTTP protocol maybe using the hash of the TLS
 certificate, or something similar, for the lease seed.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3774#comment:1>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage