#3876 closed defect (fixed)

Generate upload secret per bucket

Reported by: itamarst Owned by: GitHub <noreply@…>
Priority: normal Milestone: HTTP Storage Protocol
Component: unknown Version: n/a
Keywords: Cc:
Launchpad Bug:

Description (last modified by itamarst)

Right now the IStorageClient HTTP emulator has a single upload secret per server. This is not too bad, but can leak information for people using Tor/I2P because the server can correlate uploads.

This was caused by the HTTP server validating the upload secret across all in-progress uploads (==buckets). If two clients ever used a different upload secret for different shares of the same storage index, they couldn't do parallel uploads. This seems wrong, shares are independent.

So the HTTP API should be changed so that upload secrets are not checked at bucket creation time. It should be fine to have different upload secrets for different shares of the same storage index.

Change History (2)

comment:1 Changed at 2022-03-07T14:30:50Z by itamarst

  • Description modified (diff)
  • Type changed from enhancement to defect

comment:2 Changed at 2022-03-08T15:10:53Z by GitHub <noreply@…>

  • Owner set to GitHub <noreply@…>
  • Resolution set to fixed
  • Status changed from new to closed

In 5be7cbc/trunk:

Merge pull request #1182 from tahoe-lafs/3876-per-bucket-upload-secret

Allow per-bucket upload secret

Fixes ticket:3876

Note: See TracTickets for help on using tickets.