Web nodes provide ambient upload authority

[toby.murray]

Under the current webapi, nodes offer ambient upload authority to any host that can send them web requests. There are deployment scenarios for Tahoe in which this behaviour is undesirable.

A means to disable this behaviour would be useful. In particular, being able to turn this behaviour off via a setting in tahoe.cfg could be good.

Discussion surrounding this issue can be found in the thread starting here: ​http://allmydata.org/pipermail/tahoe-dev/2009-January/001015.html

[toby.murray]

A patch to add 'web.ambient_upload_authority' as a paramater to tahoe.cfg

[toby.murray]

A test case for this configuration parameter with one test for each of its two boolean states

[zooko]

Thanks! I'm looking at your patch.

[zooko]

fixed by 66f83c7356a79978. I have some more questions about this topic which I'll post to the mailing list.

[francois]

The patch has been reverted by Zooko.

[davidsarah]

See #1215 (add CORS support), which is blocked by at least this issue.

[davidsarah]

See also #1455, about UI redressing attacks on the ambiently accessible pages.

[davidsarah]

In LAE's Tahoe-LAFS-on-S3 service (and possibly other cases when we have accounting), a customer who made a public gateway accessible would have to pay for storage of any files uploaded via that gateway, which puts a real cramp on sharing.