-
Notifications
You must be signed in to change notification settings - Fork 2.1k
nanocoap_sock: don't include token in empty ACK response #19366
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
Conversation
65436de
to
84827a4
Compare
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.
Please update the PR description before starting bors and replace "ACK response" with "empty ACK". "ACK response" would generally be understood as an ACK with a piggybacked response payload, which would need the token.
And empty ACK however MUST NOT have a token; this fixes a severe standard violation. Thx for spotting it
84827a4
to
d6e05da
Compare
bors merge |
19366: nanocoap_sock: don't include token in empty ACK response r=benpicco a=benpicco 19367: cord: bump reference from draft to rfc r=benpicco a=bergzand ### Contribution description The draft is an RFC, this bumps the "see also" in the docs to the rfc. ### Testing procedure Check that the correct RFC is linked in the docs. ### Issues/PRs references None Co-authored-by: Benjamin Valentin <benjamin.valentin@ml-pa.com> Co-authored-by: Koen Zandberg <koen@bergzand.net>
bors cancel |
Canceled. |
bors merge |
Already running a review |
Build succeeded: |
Contribution description
CoAP doesn't expect a Token in an empty ACK, but
coap_build_hdr()
will copy it over if we give it a token length.This is bad as here we only provide space for the CoAP header
ack
.coap_build_hdr()
will copy the token intosnip
where it causes all kinds of mayhem.Testing procedure
Issues/PRs references