[tahoe-lafs-trac-stream] [tahoe-lafs] #1567: S3 backend: restore s3.max_space option

[tahoe-lafs]

#1567: S3 backend: restore s3.max_space option
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:
  davidsarah             |     Status:  closed
         Type:  defect   |  Milestone:  soon
     Priority:  normal   |    Version:  1.9.0b1
    Component:  code-    |   Keywords:  s3-backend security storage
  storage                |  max_space lae
   Resolution:  wontfix  |
Launchpad Bug:           |
-------------------------+-------------------------------------------------
Changes (by davidsarah):

 * status:  new => closed
 * resolution:   => wontfix


Old description:

> The {{{s3.max_space}}} option, which limits the space used by a storage
> server using an S3 backend, was removed in [5482/ticket999-S3-backend]
> because it wasn't completely implemented. The intention of this option is
> to protect the user from being charged for excessive space usage, perhaps
> due to a rogue file copy that is copying more than expected, or someone
> gaining access to the introducer FURL and maliciously uploading a large
> amount of data.
>
> The attached patch adds back the partial implementation.

New description:

 The {{{s3.max_space}}} option, which limits the space used by a storage
 server using an S3 backend, was removed in [5482/ticket999-S3-backend]
 because it wasn't completely implemented. The intention of this option is
 to protect the user from being charged for excessive space usage, perhaps
 due to a rogue file copy that is copying more than expected, or someone
 gaining access to the introducer FURL and maliciously uploading a large
 amount of data.

 The attached patch adds back the partial implementation.

--

Comment:

 This should probably be implemented generically using the leasedb, rather
 than with any S3- or cloud-backend-specific code. Strictly speaking that
 could have a different result because there may be objects in the S3
 bucket that do not correspond to shares in the leasedb (and need not even
 look like share objects), but that doesn't seem like it is our problem.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1567#comment:2>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage