Print

[2E0SVE]

Ok, so I know using encryption is not permitted with the license. 

1/ But is signing messages with a secret key (not encrypting it, generating a hash say a 128 MD5 hash) and signing that with a key secret key and publichedpubluc key allowed?  This would in no way obscure the content of the message which would remain in plain text but give a method of verifying the source and authenticity of a message. 

Comments please and

2/ And running the thought process further would actually encrypting the message but publishing the heys - both public and private - say on github be in compliance with the license(s).  This would in no way make the message secret as anyone competend could obtain the message with the use of the hey

[KA0HCP]

It's best to avoid any situation that requires thought about the matter. Don't mix any sort of encryption with AR messages.

[W9IQ]

Ok, so I know using encryption is not permitted with the license. 

1/ But is signing messages with a secret key (not encrypting it, generating a hash say a 128 MD5 hash) and signing that with a key secret key and publichedpubluc key allowed?  This would in no way obscure the content of the message which would remain in plain text but give a method of verifying the source and authenticity of a message.

I can only answer from a US regulatory perspective.

You are correct. Signing messages, signed MACs, etc. are acceptable uses of cryptographic techniques under FCC rules. These do not obscure the message by design nor intent.

2/ And running the thought process further would actually encrypting the message but publishing the heys - both public and private - say on github be in compliance with the license(s).  This would in no way make the message secret as anyone competend could obtain the message with the use of the hey

The FCC has been very clear that this is not permitted since the intent and effect is to obscure the message.

- Glenn W9IQ