[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3763: Potential issues with `PUT /v1/lease/:storage_index` in GBS protocol

[Tahoe-LAFS]

#3763: Potential issues with `PUT /v1/lease/:storage_index` in GBS protocol
--------------------------+-----------------------------------
     Reporter:  itamarst  |      Owner:  exarkun
         Type:  task      |     Status:  new
     Priority:  normal    |  Milestone:  HTTP Storage Protocol
    Component:  unknown   |    Version:  n/a
   Resolution:            |   Keywords:
Launchpad Bug:            |
--------------------------+-----------------------------------

Comment (by itamarst):

 Replying to [comment:4 exarkun]:

 > I *feel* like the overlap between `add_lease` and `renew_lease` is a
 mistake.  It would be convenient if the `renew_lease` functionality were
 *100%* encompassed by that overlap (because then `renew_lease` could be
 deleted) but there is the annoying `cancel_secret`...

 Well, but the cancellation secret isn't actually used by anything. So for
 implementation purposes we can just ignore it for now, have a single API
 call, and worry about cancellation later?

 On the other hand, for audit purposes having a cancellation secret spec in
 place would be useful, seems like a thing where you really want to get the
 security right...

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