Skip to content

NSAPI - Don't send trailing garbage in DNS queries #4274

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

Merged
merged 1 commit into from
May 18, 2017

Conversation

kjbracey
Copy link
Contributor

@kjbracey kjbracey commented May 5, 2017

Observed during investigation of
#4246 - DNS queries sent
the entire buffer, not just the bit filled in.

Inefficient, especially for 6LoWPAN, and a security hole - the trailing
data could be previously-used heap.

Observed during investigation of
ARMmbed#4246 - DNS queries sent
the entire buffer, not just the bit filled in.

Inefficient, especially for 6LoWPAN, and a security hole - the trailing
data could be previously-used heap.
@kjbracey
Copy link
Contributor Author

kjbracey commented May 5, 2017

@mikaleppanen, @c1728p9, @geky

@mikaleppanen
Copy link

Looks good to me

@0xc0170
Copy link
Contributor

0xc0170 commented May 5, 2017

/morph test-nightly

@geky
Copy link
Contributor

geky commented May 5, 2017

Heh, we found this too yesterday looking at a similar issue. Seems like you beat us to the punch.

It seems some DNS servers also reject the query if the size of the packet does not match what's in the header. Should resolve #3926

@mbed-bot
Copy link

mbed-bot commented May 5, 2017

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test-nightly

Output

mbed Build Number: 157

Test failed!

@theotherjimmy
Copy link
Contributor

mbedgt: no matching platforms were found!

I don't think that's @kjbracey-arm's fault. @studavekar Any idea on what could have caused this?

@studavekar
Copy link
Contributor

MAX32625MBED device was not been listed by mbedls, Device was in bad state. mbedgt should detect and run the test now.

@studavekar
Copy link
Contributor

/morph test-nightly

@mbed-bot
Copy link

mbed-bot commented May 8, 2017

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test-nightly

Output

mbed Build Number: 167

Test failed!

@geky
Copy link
Contributor

geky commented May 8, 2017

The arch pro has been having issues in CI with the flash test. @bridadan is already on it, it may just be that the board's flash has been exhausted.

@bridadan
Copy link
Contributor

Quick update on the arch pro. @studavekar was able to reproduce it and the error is detailed in #4288. @0xc0170 mentions there that he thinks we should disable the flash capability for the arch pro until we can fix it, so I raised PR #4298. When that gets in hopefully this PR can move forward.

@0xc0170
Copy link
Contributor

0xc0170 commented May 11, 2017

/morph test-nightly

@mbed-bot
Copy link

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test-nightly

Output

mbed Build Number: 186

Test failed!

@0xc0170
Copy link
Contributor

0xc0170 commented May 12, 2017

restarting

/morph test-nightly

@mbed-bot
Copy link

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test-nightly

Output

mbed Build Number: 199

Test failed!

@0xc0170
Copy link
Contributor

0xc0170 commented May 15, 2017

/morph test-nightly

@mbed-bot
Copy link

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test-nightly

Output

mbed Build Number: 225

All builds and test passed!

@sg- sg- merged commit 8e8174a into ARMmbed:master May 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants