28 Comments

Commenting has been turned off for this post
Steve Stroh N8GNJ's avatar

Commenting for this issue is now moved to the Zero Retries email list:

mailto:zeroretries@groups.io?subject=%23zr0226

Send email to zeroretries@groups.io with Subject: #zr0226

Expand full comment
Justin AB3E's avatar

Regarding encryption, I've come to believe this is an area of Part 97 that's actually quite permissive and progressive. It merely prohibits encoding messages *for the purpose of obscuring their meaning*. For once, the FCC doesn't actually prohibit (or allow) any particular technology, they actually regulate the intent.

To me, this means if I encrypt some messages and then publish the keys in a conspicuous, public location, my purpose is clearly not to obscure the meaning of the messages. This helps when the desire is to reuse Internet technologies that have encryption "baked in".

However, I have yet to hear of a legitimate situation where hams really want private comms not covered by exceptions in Part 97. What they most often want is actually authentication: to prove that something came from them and no one else, be that telecommand of a device or similar. This is also easily done and doesn't contravene Part 97 in my opinion. A cryptographic signature appended to the end of a message does not obscure meaning if the message is unencrypted. Amazingly, ARRL (perhaps by accident) already developed everything we need to do this as part of LOTW:

https://github.com/Mihara/lotw-trust

They could easily publish the root certs and everyone's public keys. Then, you could sign anything with your private key and it would be verifiable. It really just needs someone with the time/funding to tie it all together. Perhaps a fertile area for a grant...

Expand full comment
26 more comments...

No posts

Ready for more?