-
Notifications
You must be signed in to change notification settings - Fork 82
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
Mandatory parts of TLS 1.3 #174
Merged
Changes from 1 commit
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
351c62a
psk support in tls.py script on server side
tomato42 7ce663c
simple PSK integration test
tomato42 d9e855b
session obj TLS 1.3 exporter and resumption data
tomato42 6c28b6b
save the time when ticket was received
tomato42 7b44f57
keep reference to tickets in session
tomato42 31400ea
handshake helpers for client resumption
tomato42 1ee4c1b
TLS1.3 resumption support in client
tomato42 2e9f66b
resumption test in tls.py script
tomato42 e059118
handshake settings for server side support of session tickets
tomato42 daf8f52
session ticket payload
tomato42 fe471d6
add support for sending TLS 1.3 tickets in server
tomato42 2507236
restoring session from session ticket
tomato42 6296421
ticket support in tls.py server
tomato42 578f38f
clean up handshakesettings
tomato42 9a53913
don't try to negotiate TLS 1.3 with client_version
tomato42 5bbf1b3
handle FALLBACK_SCSV for TLS 1.3 too
tomato42 12aaaa1
draft-25: include record layer into AEAD additional data
tomato42 dc07b02
draft-26: update version number
tomato42 58a705e
verify TLS 1.3 record header
tomato42 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
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
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 understand that this is probably easier to recreate the record layer header, but wouldn't it be more future-proof to carry it over from the actual data received?
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.
this has the side-effect of enforcing them to those values, and I want to be strict on receiving
(on sending side I'm setting them to configured values as I want to be able to test this in other implementations)
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.
But on the receiving side you then do not authenticate what was sent over the wire. I do not know whether there is any theoretical attack possible this way though. The enforcing to the expected values should be done explicitly I think.
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.
fixed: 58a705e