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.

Sign up for GitHub

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

Jump to bottom

Add configurable crypto operation maximum data size #117

Open
wmiaw opened this issue Jul 14, 2016 · 2 comments
Open

Add configurable crypto operation maximum data size #117

wmiaw opened this issue Jul 14, 2016 · 2 comments
Assignees
@wmiaw
Labels
enhancement

Comments

@wmiaw
Copy link
Contributor

wmiaw commented Jul 14, 2016 •
edited
Loading

Allow MSL configurations to specify a maximum size for data processed by a crypto operation, to ensure compatibility with all participating entities. Perhaps this belongs in MessageCapabilities. Application data can be split across MSL payload chunks to satisfy this limit, but errors would need to be thrown for data in tokens and headers.

The default size should be set to 100KiB.
@wmiaw wmiaw self-assigned this Jul 14, 2016
@coffeetocode
Copy link

I believe this is closed based on a status report I saw from SecEng; can you confirm?

@wmiaw
Copy link
Contributor Author

wmiaw commented Dec 12, 2018

It was not implemented in MSL Core. It has been implemented on the Netflix servers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wmiaw wmiaw

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wmiaw @coffeetocode