this post was submitted on 28 May 2026
18 points (78.1% liked)

Meshtastic

2375 readers
1 users here now

A community to discuss Meshtastic (https://meshtastic.org/docs/introduction)

Other mesh communities:

MeshCore: !Meshcore@feddit.org Reticulum: !Reticulum@mander.xyz

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] vk6flab@lemmy.radio 3 points 2 weeks ago (1 children)

That's not strictly true.

AFAIK, Satellite command and control is permitted to be encrypted.

I'm also pretty sure that the encryption clauses are USA only. I don't recall seeing anything in the Australian regulations about it.

[–] Brummbaer@pawb.social 0 points 2 weeks ago (1 children)

I think it's worldwide - amateur radio transmission has to be unencrypted.

I also found this excerpt from

https://www.acma.gov.au/amateur-radio-operating-procedures

Transmissions from an amateur station must not be encrypted or scrambled, except for signals used to control a satellite, signals used to control a remote amateur station or by stations participating in emergency services operations or exercises.

[–] vk6flab@lemmy.radio 3 points 2 weeks ago (1 children)

While I take your point, I'd like to observe that you're not quoting from the actual legislation which doesn't talk about encryption, instead it describes the notion of "obscuring the meaning of the signal". (13.2.d.iv)

See: https://www.legislation.gov.au/F2023L01648/asmade/text

Before you tell me that this is describing encryption, consider Morse code, which requires you to know that a "dit-dah" means the letter "A". This is like having a code to represent something else, just like the word "Alpha" means the letter "A" and "QTH" means your operating location.

In other words, if there's a common understanding of the meaning, it's not obscured, but it can still be encrypted.

I realise that this is a fine line, but the word encryption doesn't require that nobody knows.

[–] Brummbaer@pawb.social 1 points 2 weeks ago (1 children)

I understand what you mean, but I'm not sure that is meant by obscuring the meaning of the signal.

Morse code is a way of sending unobscured information, everyone who listens in and knows how to interpret it can see what is transmitted - so the transmission is not obscured. SSTV is gibberish if you listen to it, but everyone can decode it into a picture if they use the public known way on how to do it. It's even worse when you think about what obscuring the meaning entails. You are not allowed to run a number station, because everything you send doesn't mean anything, since your number codes are obscuring the meaning of the message.

Also law is interpreted by the government and if the agency in charge says they see that as an interdiction of cryptography the only way to challenge that would be in court since they would just fine you or take away your license for encrypting anyway.

[–] vk6flab@lemmy.radio 1 points 2 weeks ago (1 children)

I think we're agreeing that the notion of encryption is subject to interpretation and you are absolutely right in pointing out that the regulator gets to decide what it means unless challenged in court.

I like the SSTV example because it's not obvious how to decode it, requiring tools to do so. The same is true for ft8 and Olivia for example.

I don't exactly know where the line is and based on my experience with this, I think that it was written like that on purpose.

[–] Brummbaer@pawb.social 1 points 2 weeks ago

I'm totally with you on that, but I think the encryption ban also was/is also actively supported by the bigger ham radio organisations. There is some open communications culture, which is fine, but it shouldn't hinder people to encrypt their traffic if they want to.