-
Notifications
You must be signed in to change notification settings - Fork 963
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
fix: don't broadcast public keys if the user is licensed #5190
Conversation
c61bdc8
to
49e63b8
Compare
49e63b8
to
3ba430d
Compare
Do we need this, with the is_licensed change I pushed earlier? |
Please excuse my ignorance, but I'm curious to learn why this is necessary. I understand ham has to operate unencrypted, so the licensed node can't send anything encrypted, but why prevent another non-licensed node from sending something encrypted. Must a licensed node also not receive anything encrypted? |
Not sure your change will have an effect if they already have keys generated. |
yes. public keys are still being sent in the NodeInfo broadcasts when |
Last time I checked, I came to the conclusion that it was a problem, yes. Of course I can't currently find that source. |
Got it. Yeah, looks good then. |
I tried to find the legislative answer to amateur radio and encryption and only went down a rabbit hole. In Australia atleast from https://www.acma.gov.au/amateur-radio-operating-procedures I found the following. But receiving signals as an amateur would mean the other party could only be another amateur and thus only unencrypted anyway. This not allowing reception of unencrypted would just be additional checks and balances. Except Encryption/scrambling Re-transmission |
Co-authored-by: Ben Meadors <[email protected]> Co-authored-by: Jonathan Bennett <[email protected]>
prevents NodeInfo broadcasts with public keys when the user is licensed.