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.

Sign up for GitHub

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

Jump to bottom

Encryption Support? #200

Open
majmongoose opened this issue Jan 25, 2022 · 3 comments
Open

Encryption Support? #200

majmongoose opened this issue Jan 25, 2022 · 3 comments
Assignees
@hmatuschek
Labels
enhancement New feature or request

Comments

@majmongoose
Copy link

My radio (DMR 6x2) finds dual use on ham bands and commercial radio bands in the US, where we are permitted to use encryption on commercial. Is there any plans to implement AES encryption programming? It is supported in the official CPS.
@hmatuschek
Copy link
Owner

Yes, it is planned but as it is not HAM radio related, it has a somewhat low priority.

@hmatuschek hmatuschek added the enhancement New feature or request label Jan 28, 2022
hmatuschek added a commit that referenced this issue Feb 13, 2022
@hmatuschek
Imlemented EncryptionExtension to represent encryption keys. Addresses …
bf3befb 
…#200.
hmatuschek added a commit that referenced this issue Feb 16, 2022
@hmatuschek
Added CommercialChannelExtension. Implements the reference to an encr…
755a6aa 
…yption key for channels. Addresses #200.
hmatuschek added a commit that referenced this issue Feb 16, 2022
@hmatuschek
Implemented editing of ConfigObjectReferences. Addresses #200.
ba17e61
@hmatuschek
Copy link
Owner

hmatuschek commented Feb 16, 2022 •
edited

Ok I use this issue as an excuse to finalize the implementation of the device specific settings. That is, encryption will be implemented as an extension in the encryption branch. Things needed:

  • Implement EncryptionExtension (holds the keys)
  • Implement CommercialChannelExtension (holds the reference to a key for each channel)
  • Document extensions in manual
  • Implement handling of ConfigObjectLists in ExtensionWrapper
  • Implement handling of ConfigObjectReference in ExtensionWrapper
  • Implement encoding/decoding of encryption in Radioddity Codeplugs
  • Implement encoding/decoding of encryption in TyT Codeplugs
  • Implement encoding/decoding of encryption in AnyTone Codeplugs

@hmatuschek hmatuschek self-assigned this Feb 16, 2022
hmatuschek added a commit that referenced this issue Feb 20, 2022
@hmatuschek
Added ConfigObjectSelectionDialog. Addresses #200.
9253144
hmatuschek added a commit that referenced this issue Feb 21, 2022
@hmatuschek
Fixed list editing in extensions. Addresses #200.
0e47971
hmatuschek added a commit that referenced this issue Feb 21, 2022
@hmatuschek
Fixed ExtensionWrapper signals. Addresses #200.
f4290dd
hmatuschek added a commit that referenced this issue Feb 23, 2022
@hmatuschek
Implemented encoding/decoding of encryption keys for Radioddity devic…
80f2721 
…es. Addresses #200.
@audriusb
Copy link

audriusb commented Dec 9, 2023

i like that it's there, but i can only see 128 bit support. both Anytone 878 and TYT 390 support AES256 now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hmatuschek hmatuschek

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hmatuschek @majmongoose @audriusb