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

tls handshake: when peer closes the connection, server also closes it #72

Merged
merged 1 commit into from
Oct 17, 2022

Conversation

TheLortex
Copy link
Contributor

No description provided.

@hannesm
Copy link
Contributor

hannesm commented Oct 13, 2022

I think this is fine, since the tls_mirage code isn't consistent in read_react that whenever an error occues, close is called on the underlying flow.

@dinosaure dinosaure force-pushed the close-on-handshake-fail branch from 9dd6344 to cd92ae4 Compare October 13, 2022 14:02
@dinosaure
Copy link
Owner

Thanks, do you confirm that it solves the memory issue on mirage.io?

@dinosaure
Copy link
Owner

Let's say that it's ok 👍.

@dinosaure dinosaure merged commit 24c7cf3 into dinosaure:master Oct 17, 2022
@TheLortex
Copy link
Contributor Author

Yes it fixes the issue. But looking at the metrics, there's still a connection leak that is not solved

dinosaure added a commit to dinosaure/opam-repository that referenced this pull request Oct 19, 2022
CHANGES:

- Fix a file-descriptor leak when we fail on the TLS handshake (dinosaure/paf-le-chien#72, @TheLortex, @dinosaure, @hannesm)
- Add `reneg` function into `Paf_mirage.Make.TLS` (dinosaure/paf-le-chien#73, @dinosaure)
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