Specify how the lease renew secret is derived to the GBS specification document #3774

Closed
opened 2021-08-18 15:14:58 +00:00 by exarkun · 2 comments

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.

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.
exarkun added the
unknown
normal
defect
n/a
labels 2021-08-18 15:14:58 +00:00
exarkun added this to the HTTP Storage Protocol milestone 2021-08-18 15:14:58 +00:00
exarkun self-assigned this 2021-08-18 15:14:58 +00:00

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.

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.
GitHub <noreply@github.com> commented 2021-09-07 18:08:43 +00:00
Owner

In 5d75706/trunk:

Merge pull request #1118 from LeastAuthority/3774.lease-renewal-secret-construction-docs

write some words about lease renewal secrets

Fixes: ticket:3774
In [5d75706/trunk](/tahoe-lafs/trac-2024-07-25/commit/5d757069800b52c6a089c66758f152925d51c6d6): ``` Merge pull request #1118 from LeastAuthority/3774.lease-renewal-secret-construction-docs write some words about lease renewal secrets Fixes: ticket:3774 ```
tahoe-lafs added the
fixed
label 2021-09-07 18:08:43 +00:00
GitHub <noreply@github.com> closed this issue 2021-09-07 18:08:43 +00:00
Sign in to join this conversation.
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#3774
No description provided.