QtCoAP: document custom-transport security responsibilities


Qt CoAP documents implementing the QCoapConnection interface as a way
to provide an alternative transport. Such a transport replaces the
default DTLS-over-UDP protection, but the documentation does not state
that securing the exchange then becomes the integrator's responsibility.
A transport that provides no encryption, peer authentication, or message
framing silently leaves the traffic unprotected, and the loss is not
observable from the rest of the application.

Extend the Security section of the Qt CoAP Overview to state that a
custom transport must itself provide these properties

Fixes: QTBUG-149939
Pick-to: 6.12 6.11 6.8
Change-Id: I00a695e0f4cdc73db4bb45e9022cb43af9c5e36b
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
commit628d44a420820e6aaf0bd971cd548f5711491d9d
parent1b70ad662edce5f89f91c9a803936e8229f4e6da
authorMate Barany <mate.barany@qt.io>
committerMate Barany <mate.barany@qt.io>
commit timeTue, 8 Sep 2026 08:35:13 +0000