Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible alternatives for SizeLimit::Bounded() in decode_from and encode_into #32

Open
eresch opened this issue Sep 4, 2015 · 1 comment

Comments

@eresch
Copy link
Contributor

eresch commented Sep 4, 2015

No description provided.

@Cranc
Copy link

Cranc commented Sep 9, 2015

we do not use SizeLimit::Bounded() and never used it in storage ....

if you want us to use it read below.

in behalf of storage group:
decode_from and encode_into are only used in table and are not accessible from outside and are only used to save and load table information so unless it is possible to push unlimited columns in a table (which is quite unlikely) it is impossible for encode_into or decode_from to be targeted by some kind of DDOS - which BTW is the only reason to use Bounded() size-limit so i don't see a reason to remove SizeLimit::Infinite

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants