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

Added Record fragmentation handling #46

Merged
merged 5 commits into from
Jul 27, 2015
Merged

Added Record fragmentation handling #46

merged 5 commits into from
Jul 27, 2015

Conversation

alexmgr
Copy link
Collaborator

@alexmgr alexmgr commented Jul 23, 2015

  • Records above 2^16 - 1 raise a TLSFragmentationError. It's up to the user to fragment on the RFC 2^14 boundary
  • Provided helper functions to assist with fragmentation

@buildhive
Copy link

tintin » scapy-ssl_tls #156 SUCCESS
This pull request looks good
(what's this?)

@buildhive
Copy link

tintin » scapy-ssl_tls #160 SUCCESS
This pull request looks good
(what's this?)

- Override Packet fragment() in TLSRecord(). Allows fragmenting
packet on defined offsets
- TLSFragmentationError is now raised when a record requires
  fragmentation
- TLSRecords can be fragmented to any size
- Added unittests
- This reverts commit a1e0b8a.
- I gave this somemore thought, and I don't think that TLSSocket
  should take the decision about the fragmentation boundary. Should
  be up to the user, allows more flexibility
alexmgr added a commit that referenced this pull request Jul 27, 2015
Added Record fragmentation handling
@alexmgr alexmgr merged commit 63ba9bd into master Jul 27, 2015
@buildhive
Copy link

tintin » scapy-ssl_tls #167 SUCCESS
This pull request looks good
(what's this?)

@alexmgr alexmgr deleted the fragmentation branch July 27, 2015 19:40
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.

None yet

2 participants