BTLE: do not log CSRK and MAC


The Connection Signature Resolving Key (CSRK) is used to sign data
in a connection. Because of that, leaking that key might result in
unwanted writes from untrusted devices.
CSRK can be assigned to a device by a manufacturer, and thus
exposing it to the logs is not safe.

The message authentication code (MAC) is calculated using CSRK and
an increasing sign counter. I'm not sure if there's any practical
problem in exposing MAC (e.g, if it's possible to find CSRK based
on the values), but better be safe and not print it either.

Pick-to: 6.11 6.8 6.5
Change-Id: Id6e8887df96f5bf18f31fc90ccecc00f976f1ee8
Reviewed-by: Juha Vuolle <juha.vuolle@qt.io>
commit596c22619cdbbe03c903754fc9bb4e26b3e22087
parent5a34b2f123f26683c029063ee66022bd5b299021
authorIvan Solovev <ivan.solovev@qt.io>
committerIvan Solovev <ivan.solovev@qt.io>
commit timeMon, 20 Apr 2026 16:05:01 +0000