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

Tolerate s2n_init() being called before aws_io_library_init() #508

Merged
merged 10 commits into from
Aug 12, 2022

Conversation

graebm
Copy link
Contributor

@graebm graebm commented Aug 12, 2022

ISSUE:
A customer reported a failure when aws-c-io called s2n_init(). The customer's code was already using S2N-TLS, and they were already calling s2n_init() themselves. They were pulling in aws-c-io via a deep dependency chain and weren't even aware that anything else in their application was using S2N-TLS.

In the past, the failing call to s2n_init() wasn't being checked, we did start checking for success in this PR #461

DESCRIPTION OF CHANGES
If S2N-TLS has already been initialized, then aws-c-io does not call s2n_init() or s2n_cleanup()

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@graebm graebm merged commit 4e462a0 into main Aug 12, 2022
@graebm graebm deleted the s2n-external-init branch August 12, 2022 21:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants