Skip to content
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

[Feature Request]: Only allow empty keys for nodes that are set as a licensed user #5700

Open
garthvh opened this issue Dec 30, 2024 · 6 comments
Assignees
Labels
enhancement New feature or request

Comments

@garthvh
Copy link
Member

garthvh commented Dec 30, 2024

Platform

Cross-Platform

Description

Right now we allow users who are not licensed users to set empty keys for channels when they are not in licensed user mode, we should restrict empty keys to only licensed users so that Hams do not have to be concerned with potentially rebroadcasting messages sent from unlicensed users.

@garthvh garthvh added the enhancement New feature or request label Dec 30, 2024
@mepholic
Copy link

I think this is suggesting that non-HAM licensed nodes should not be allowed to use blank keys, or be able to send completely unencrypted traffic. It seems like this is being proposed as a "solution" for HAMs who are worried about digipeating traffic originating from nodes run by unlicensed operators.

I do not think that usage of encryption should be used as a heuristic to decide whether or not the traffic originated from a HAM operator or not, and in addition to this, nothing stops someone from lying about their licensing status. If the purpose of this feature request is to allow a HAM operator to selectively rebroadcast traffic from other HAM operators only, another field should probably be added to the packets to indicate station license status, and then an option should be added to the Rebroadcast Mode dropdown for "only packets from licensed stations", or something like that.

@mepholic
Copy link

I had some additional musings in Discord, which I'll include here:

is anyone here familiar with the technical aspects of the LoTW PKI? would it be possible to sign meshtastic frames with your callsign cert and have others be able to verify the signature?

if that is possible, one disadvantage of it would be that it would put ham verification authority for meshtastic users pretty much solely in the hands of the ARRL, but on the flip side, their direct mail authorization and the technical aspects of the PKI would allow folks to be fairly certain that signed packets are from actual hams, and in addition to that, many hams already have LoTW certs

@mepholic
Copy link

mepholic commented Dec 31, 2024

I've given this some more thought, and I realized that requiring encryption on unlicensed traffic means that Meshtastic would be outright illegal to use to jurisdictions that ban encryption, unless users in those jurisdictions turn on licensed operator mode, which in turn just enables even more foot guns. Is this really a good solution? 🤔

I generally think that being explicit in protocol design is a whole lot clearer and more flexible in the long term than being implicit.

Making the implicit assumption that all unencrypted traffic is and always will be licensed traffic, and all encrypted traffic is and always will be unlicensed traffic is a vague and seemingly arbitrary decision from a protocol design standpoint. It creates limitations on what is possible with the protocol in the future once implemented, and is not nearly as flexible as just adding a flag to packets that indicate whether the originating node is licensed or not.

@dm5tt
Copy link

dm5tt commented Dec 31, 2024

Isn't there an option to still use some kind of cryptographic signing in Meshtastic without encryption enabled? Encryption ham radio is forbidden globally - signing not. This still would solve a lot of real world problems.

@thebentern
Copy link
Contributor

thebentern commented Jan 1, 2025

I've given this some more thought, and I realized that requiring encryption on unlicensed traffic means that Meshtastic would be outright illegal to use to jurisdictions that ban encryption, unless users in those jurisdictions turn on licensed operator mode, which in turn just enables even more foot guns. Is this really a good solution? 🤔

Areas that do not allow any encryption may be an even smaller audience of meshtastic usage than licensed mode users. I have not seen any examples of folks contending with it. I suspect most individuals subject to those restrictions just pick a lora region (illegally) and hang out on the defaults or don't use meshtastic at all.

@SpudGunMan
Copy link

SpudGunMan commented Jan 4, 2025

It's also very easy to exploit this keyless nature

Crazy idea 🥔what about some base key where its key=Licensed:Callsign with a very reversible hash which is the encryption but it's not

There needs to be a way to route these packets effectively over all networks to make this enjoyable and help in its emergency use.

And not be exploitable why wouldn't everyone use nokey if the ham infrastructure is built robust in an area, or to bypass duty cycle limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants