Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Ignore (possibly malformed) options after EOL #281

Merged

Conversation

ecatmur
Copy link
Contributor

@ecatmur ecatmur commented Feb 1, 2018

It is invalid for options (other than EOL) to occur after EOL. However,
most network stacks will stop processing options at EOL, meaning that
any further options will be ignored, including if they make the options
field malformed. We should likewise stop processing at EOL as otherwise
we will reject packets that most network stacks accept.

Similarly, when writing out options use EOL as end padding, instead of
NOP.

Test.

mfontanini and others added 3 commits December 3, 2017 16:04
It is invalid for options (other than EOL) to occur after EOL. However,
most network stacks will stop processing options at EOL, meaning that
any further options will be ignored, including if they make the options
field malformed. We should likewise stop processing at EOL as otherwise
we will reject packets that most network stacks accept.

Similarly, when writing out options use EOL as end padding, instead of
NOP.

Test.
@mfontanini mfontanini changed the base branch from master to develop February 1, 2018 16:59
@mfontanini mfontanini merged commit 971fdf7 into mfontanini:develop Feb 3, 2018
@mfontanini
Copy link
Owner

This makes sense. Thanks!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants