Opened at 2021-08-18T15:14:58Z
Closed at 2021-09-07T18:08:43Z
#3774 closed defect (fixed)
Specify how the lease renew secret is derived to the GBS specification document
| Reported by: | exarkun | Owned by: | exarkun |
|---|---|---|---|
| Priority: | normal | Milestone: | HTTP Storage Protocol |
| Component: | unknown | Version: | n/a |
| Keywords: | Cc: | ||
| Launchpad Bug: |
Description
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.
Change History (2)
comment:1 Changed at 2021-08-18T15:55:09Z by itamarst
comment:2 Changed at 2021-09-07T18:08:43Z by GitHub <noreply@…>
- Resolution set to fixed
- Status changed from new to closed
In 5d75706/trunk:
Note: See
TracTickets for help on using
tickets.
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.