[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
 Keywords:           |  Launchpad Bug:
---------------------+---------------------------------------
 It turns out the secret is derived in part using Foolscap.  If we actually
 want to remove the Foolscap dependency then we'll have to change the
 implementation of the code that derives it.  Before doing that, it would
 be nice to have some text that says exactly how we want it to be derived
 (and maybe that will be the same as the current implementation or maybe
 not - if not, maybe justify why this is okay, too).

 Also, the specification is better if it includes this information instead
 of leaving it as an implementation detail.

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