-
Notifications
You must be signed in to change notification settings - Fork 201
add PKI uplink and downlink options #550
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
… packet payloads
co-authored-by: edinnen
Short turbo preset
Optional properties
Update comments to match discord conversation
update api name
Adds public_key and private_key for PKI
Add client notification fromradio message
Addresses #4428
There's already an "encryption_enabled" setting in the MQTT config. Can't we follow that? |
We're treating PKI as a separate channel, so this setting follows the per-channel MQTT settings. I'm not sure how exactly that would map to encryption_enabled. |
"encryption_enabled" applies to all packets sent to the MQTT server, no matter which channel. I think we can just follow the same logic for PKI? |
I believe these new settings aren't for whether the uploaded packets are encrypted or not (with PKI they always are), it's for whether they're uplinked/downlinked to/from MQTT at all. Since the new PKI DMs use different keys, they're effectively "channel-less", so these options are the equivalent of the "uplink enabled" and "downlink enabled" that's on each channel, but for these new messages instead. |
(or to put it more simply, maybe: if we followed |
Summary of my points on Discord: currently we also don't have granular settings for uplinking/downlinking DMs and I believe this will be confusing because when you discover a node, you expect you can also DM it. |
Shelving this for now. |
Seems like we'll want the switches to control PKI uplink and downlink via MQTT