-
-
Notifications
You must be signed in to change notification settings - Fork 348
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
Workaround OpenSSL 1.1.1 session-ticket issue #1171
Merged
oremanj
merged 5 commits into
python-trio:master
from
njsmith:workaround-openssl-session-ticket-bug
Aug 2, 2019
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
20d2de5
Workaround OpenSSL 1.1.1 session-ticket issue
njsmith b0acb2f
Parametrize SSL tests to check both TLS 1.2 and TLS 1.3
njsmith 655ee5c
Add newsfragment
njsmith 9758859
Quiet a false-positive from flake8
njsmith b681e32
Tolerate old openssl
njsmith File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
OpenSSL has a bug in its handling of TLS 1.3 session tickets that can | ||
cause deadlocks or data loss in some rare edge cases. These edge cases | ||
most frequently happen during tests. (OpenSSL bugs: `#7948 | ||
<https://github.com/openssl/openssl/issues/7948>`__, `#7967 | ||
<https://github.com/openssl/openssl/issues/7967>`__.) `trio.SSLStream` | ||
now works around this issue, so you don't have to worry about it. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can fix the flake8 issue by removing the unused client_ctx import
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not unused, it's making the fixture function visible to pytest...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry about that, I'm used to projects where pytest discovers the fixtures through conftest.py