Skip to content

Conversation

@rzr
Copy link
Collaborator

@rzr rzr commented Oct 20, 2025

It looks like majority of users are using client and server on same system, adding encryption brings more problems than convenience, specifically when tracing/debugging the flow, or when disconnection it adds complexity (the whole session should be renegotiated).

It looks like majority of users are using client and server on same
system, adding encryption brings more problems than convenience,
specifically when tracing/debugging the flow, or when disconnection
it adds complexity (the whole session should be renegotiated).

Signed-off-by: Philippe Coval <[email protected]>
@rzr
Copy link
Collaborator Author

rzr commented Oct 20, 2025

It will be mentioned in next change that update doc/RELEASE_NOTE.md to release ver7_18.05

@rzr
Copy link
Collaborator Author

rzr commented Oct 20, 2025

Actually i am not sure,
Let me mark it as draft

It is a breaking change according to doc/RELEASE_NOTE.md

5.1.2.3.1 Security Command Class

The Z/IP Gateway communicates securely with Z-Wave nodes that support the Z-Wave Security Command Class.
All security is terminated in the Z/IP Gateway and never leaves the Z-Wave network.
If a LAN Z/IP Client wishes to communicate with a secure ZWave node,
it needs to transmit the normal Z/IP Packet to the Z/IP Gateway
using the Z/IP Lan Security (DTLS) encapsulation mechanisms.

@rzr rzr marked this pull request as draft October 20, 2025 15:36
rzr added a commit that referenced this pull request Oct 20, 2025
Origin: #41
Signed-off-by: Philippe Coval <[email protected]>
@rzr rzr mentioned this pull request Oct 20, 2025
Copy link
Contributor

@silabs-JulienT silabs-JulienT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Too impactful from a maintenance perspective.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants