[Feature Request]: DM the Owner - Contact Info (NodeID) for mandatory-rebroadcast roles #8410
korbinianbauer
started this conversation in
Ideas
Replies: 1 comment 3 replies
-
|
Option A) I have a specific node that is not my day to day node, that I use for remote admin of my infrastructure nodes, it's not online all the time, only when I need to use it to either make changes or while I am deploying a new infrastructure node to confirm remote admin is working etc - so you would be messaging thin air (or it would be forwarding a DM to thin air) Option B) This is not going to work for a variety of reasons - one being you are taking a choice away from infrastructure node owners, they may not want others to know which infrastructure node's belong to them. As an "optional" entry - yes, not as a forced requirement. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Platform
Cross-Platform
Description
Tl;dr:
ROUTERs and Co. should offer to DM the owner.Mandatory-rebroadcast roles, especially
ROUTER, but alsoROUTER_LATEandCLIENT_BASEcan cause trouble for other users. (E.g. #8367)Usually, these nodes are not connected to a phone, so you cannot easily reach the owner/maintainer by DM. Trying to reach them via public channels or other platforms (Reddit, Telegram, HAM clubs) is hit and miss at best. Not everyone reads or uses these.
However, these roles are often connected to another of the owner's personal nodes anyway for remote administration.
This feature request is about:
Option A: Allow DMs to be sent to mandatory-rebroadcast roles. These DMs would be automatically forwarded to the last-used remote administration node.
Option B: Have infrastructure nodes (Routers, etc.) broadcast the NodeID of their last-used remote administration node as part of their NodeInfo. The client app could then offer a button to DM that NodeID directly.
Synergic proposals:
If [Feature Request]: Make mandatory-rebroadcast roles only possible to enable via remote admin #8347 is implemented, every mandatory-broadcast role has to have a remote-admin key, with this feature it would also automatically have a contact node configured.
If [Feature Request]: Apply an expiry time on router roles, so that they fall-back to router_late if not actively maintained. #8378 is implemented and falls back to Client if not maintained, the contact nodeID would even be guaranteed to be up-to-date
Limitations
-> this feature will not guarantee you can reach the owner, just provide an on-platform, default way to do it, and increase your chances of success.
Security concerns:
Privacy concerns:
IMO none, here's why:
Without this feature:
ADMIN_APP packets are sent via the primary channel, which is the decryptable-by-everyone public channel by default. Example: https://malla.meshtastic.es/packet/16186810
The
fromandtofields specifically however are alway unencrypted. The payload (specific settings) is encrypted with the channel's PSK.Therefore, the NodeID used to remotely administer another node is already public information, no matter what.
Currently, this information is only revealed when the maintainer performs a remote administration action.
If an infrastructure owner wishes to keep the specific settings private, they currently have to use a custom primary channel for remote administration, but the
fromandtofields stay unencrypted.With this feature:
This feature would make the administrator's NodeID more readily available—which is the intended purpose—but it does not expose any new, previously protected information.
Bandwidth concerns:
Beta Was this translation helpful? Give feedback.
All reactions