interfaces: loosen a few max-size constraints which would limit us to a mere 1.09...
authorZooko O'Whielacronx <zooko@zooko.com>
Thu, 9 Oct 2008 19:13:57 +0000 (12:13 -0700)
committerZooko O'Whielacronx <zooko@zooko.com>
Thu, 9 Oct 2008 19:13:57 +0000 (12:13 -0700)
commit86e22b8addf1743864f3362ebb022a295c99d9cd
tree8b86c341336ddecf85b3d8d9a150501f9a37030a
parent93725a69353919b70ab1ed7a1dee8a99200d2f60
interfaces: loosen a few max-size constraints which would limit us to a mere 1.09 TB maximum file size

These constraints were originally intended to protect against attacks on the
storage server protocol layer which exhaust memory in the peer.  However,
defending against that sort of DoS is hard -- probably it isn't completely
achieved -- and it costs development time to think about it, and it sometimes
imposes limits on legitimate users which we don't necessarily want to impose.
So, for now we forget about limiting the amount of RAM that a foolscap peer can
cause you to start using.
src/allmydata/interfaces.py