Skip to content

Conversation

@sgunes-wirepas
Copy link
Contributor

Adds support for network_keys and management_keys fields under SinkNewConfig, as well as the SINK_KEY_MANAGEMENT_V1 feature flag.

Add new functions for write only config fields(similar to read only
fields) and move key parameters there.
Using a nested dictionary under new_config parameter doesn't follow the
existing convention (such as the app_config and earlier key related
entries), but it should make it easier to maintain the new_config
dictionary in the long run if we have a structure which is more similar
to the SinkNewConfig structure in protobuf.
@sgunes-wirepas sgunes-wirepas marked this pull request as ready for review August 19, 2025 13:42
"app_config_seq": 300,
"app_config_data": bytes.fromhex("90807060"),
"channel_map": 120,
"cipher_key": bytes.fromhex("102030"),

Choose a reason for hiding this comment

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

There is some zero padding in the gw for the keys?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, the gateway would just return an error if the key size is incorrect. This library doesn't do any checks as long as the protobuf messages are valid. It helps with testing, we can generate "bad" messages using this library.



def parse_config_keys(message_obj, dic):
def parse_config_wo(message_obj, dic):

Choose a reason for hiding this comment

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

Or wo_fields?

@sgunes-wirepas sgunes-wirepas merged commit 2dfacac into main Aug 21, 2025
5 checks passed
@sgunes-wirepas sgunes-wirepas deleted the feature/sink-key-management branch August 21, 2025 13:15
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