Skip to content

Usage Guide statement about memory usage could be more accurate #4070

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

Open
maddeleine opened this issue Jun 21, 2023 · 0 comments
Open

Usage Guide statement about memory usage could be more accurate #4070

maddeleine opened this issue Jun 21, 2023 · 0 comments

Comments

@maddeleine
Copy link
Contributor

Security issue notifications

If you discover a potential security issue in s2n we ask that you notify
AWS Security via our vulnerability reporting page. Please do not create a public github issue.

Problem:

The Usage Guide states that the s2n_connection struct is 4KB. That is technically correct; it's what you'll get if you do sizeof(s2n_connection), but it's not really that useful. It doesn't take into consideration the pointers on the connection which may point to alloced memory. So the total memory used for the connection is larger than 4KB. We've had several PRs open to try to pin down how much memory s2n uses per connection but they haven't really answered the question completely and also haven't been prioritized.

Solution:

Ideally we would be able to give users an accurate picture of how much memory will be used per TLS connection. I don't know if this would be a doc or a test, maybe both, but we should have a better answer when people ask this question.

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

2 participants