-
Notifications
You must be signed in to change notification settings - Fork 2.1k
gcoap_dtls: Selecting transport at run time is not possible #16674
Copy link
Copy link
Closed
Labels
Area: securityArea: Security-related libraries and subsystemsArea: Security-related libraries and subsystemsProcess: API changeIntegration Process: PR contains or issue proposes an API change. Should be handled with care.Integration Process: PR contains or issue proposes an API change. Should be handled with care.Type: bugThe issue reports a bug / The PR fixes a bug (including spelling errors)The issue reports a bug / The PR fixes a bug (including spelling errors)
Metadata
Metadata
Assignees
Labels
Area: securityArea: Security-related libraries and subsystemsArea: Security-related libraries and subsystemsProcess: API changeIntegration Process: PR contains or issue proposes an API change. Should be handled with care.Integration Process: PR contains or issue proposes an API change. Should be handled with care.Type: bugThe issue reports a bug / The PR fixes a bug (including spelling errors)The issue reports a bug / The PR fixes a bug (including spelling errors)
Description
Say I have a user interface where a URL is provided:
coap://example.org/sensororcoaps://example.org/sensor. Currently, whengcoap_dtlsis compiled ingcoap_req_send()does not provide me any capability to honor that URL input. It just selects DTLS (so always assumescoaps://, as far as I can tell).Steps to reproduce the issue
Try to send an unencryptet CoAP request using
gcoap_req_send()withgcoap_dtlscompiled in.Expected results
The CoAP request is unencrypted and sent over a UDP sock.
Actual results
The CoAP request is always encrypted and sent over a DTLS sock.
Versions
Any RIOT version after 23a8659.