How to Enter the decryption key for vertex Standard Enhanced Encryption

[taradeved]

help me!

dsd-neo -1 bbbbbbbbb It does not decrypt
help me!
It does not recognize the encryption type.
It would be good to add detection of the type of encoding used in the vertex because dsd-neo recognizes all vertex samples as Bp.

[arancormonk]

as far as i'm aware, Vertex “enhanced” encryption isn’t supported by upstream DSD‑FME... it's something we'll have to add since Vertex (they are part of Motorola fwiw ) obviously doesn't want to follow the same implementation, at least from what i can tell in the work already done by lwvmobile... and it's probably on purpose.

i can work on adding support, but to finish the keystream analysis I need aligned clear/encrypted pairs and known plaintext.

• What To Capture (exactly 4 items)
  • Voice (clear): one capture of a short voice transmission unencrypted.
  • Voice (encrypted): the exact same voice transmission, but encrypted.
  • Text (clear): one capture of a short text message unencrypted.
  • Text (encrypted): the exact same text message, but encrypted.
• Recording Guidelines (must follow exactly)
  • Same RF parameters for each pair: same frequency, Color Code, timeslot, talkgroup, and radio ID.
  • Same content:
    • Voice: use the same audio source, preferably a pre‑recorded test phrase played twice (once clear, once encrypted), not a human re‑speaking. Add 1–2 seconds of “quiet/open mic” before and after the phrase both times. Keep
      duration ~10–20 seconds.
    • Text: use the same exact message bytes (e.g., “00000000000000”) for both clear and encrypted sends.
  • Same keying: use the same key for all encrypted samples. If your software shows a key ID or algorithm name, note it.
  • Don’t trim or post‑process: provide raw captures as recorded.
• File Formats (either of these works; both is even better)
  • Preferred: DMR symbol capture .bin (OP25/FME-style dibit file) — one file per item.
  • Acceptable: 48 kHz mono WAV discriminator/baseband audio — one file per item.
• Helpful Metadata (include in your message back)
  • Key value used for encryption (as entered), and any key ID displayed on the radio.
  • Radio brand/model and programming options used for “enhanced” encryption.
  • Talkgroup ID, timeslot, Color Code, and whether this was simplex or via repeater.
  • For the text message: confirm the exact plaintext string and character encoding if non‑ASCII (spaces, punctuation, case, etc.).
  • Timestamps or ordering so I can pair clear↔encrypted samples correctly.
• Tips To Ensure Samples Are Truly “Identical”
  • Voice: use the same pre‑recorded WAV/MP3 played twice into the radio, with the same start/stop timing. Avoid live re‑speaking.
  • If your radio supports sending a stored voice memo or test prompt, use that for exact repeatability.
  • Keep transmissions back‑to‑back to minimize any system changes.
• Scope/Size
  • 10–20 seconds per voice capture is enough. One short text message per clear/encrypted is fine.
  • Please avoid compressing the files (ZIP is OK; no lossy audio re‑encoding).

[taradeved]

as far as i'm aware, Vertex “enhanced” encryption isn’t supported by upstream DSD‑FME... it's something we'll have to add since Vertex (they are part of Motorola fwiw ) obviously doesn't want to follow the same implementation, at least from what i can tell in the work already done by lwvmobile... and it's probably on purpose.

i can work on adding support, but to finish the keystream analysis I need aligned clear/encrypted pairs and known plaintext.

* What To Capture (**exactly 4 items**)
  
  * Voice (clear): one capture of a short voice transmission unencrypted.
  * Voice (encrypted): the exact same voice transmission, but encrypted.
  * Text (clear): one capture of a short text message unencrypted.
  * Text (encrypted): the exact same text message, but encrypted.

* Recording Guidelines (**must follow exactly**)
  
  * Same RF parameters for each pair: same frequency, Color Code, timeslot, talkgroup, and radio ID.
  * Same content:
    
    * Voice: use the same audio source, **preferably a pre‑recorded test phrase played twice** (once clear, once encrypted), not a human re‑speaking. Add 1–2 seconds of “quiet/open mic” before and after the phrase both times. Keep
      duration ~10–20 seconds.
    * Text: use the same exact message bytes (e.g., “00000000000000”) for both clear and encrypted sends.
  * Same keying: **use the same key for all encrypted samples**. If your software shows a key ID or algorithm name, note it.
  * Don’t trim or post‑process: provide raw captures as recorded.

* File Formats (either of these works; both is even better)
  
  * Preferred: DMR symbol capture .bin (OP25/FME-style dibit file) — one file per item.
  * Acceptable: 48 kHz mono WAV discriminator/baseband audio — one file per item.

* Helpful Metadata (include in your message back)
  
  * Key value used for encryption (as entered), and any key ID displayed on the radio.
  * Radio brand/model and programming options used for “enhanced” encryption.
  * Talkgroup ID, timeslot, Color Code, and whether this was simplex or via repeater.
  * For the text message: confirm the exact plaintext string and character encoding if non‑ASCII (spaces, punctuation, case, etc.).
  * Timestamps or ordering so I can pair clear↔encrypted samples correctly.

* Tips To Ensure Samples Are Truly “Identical”
  
  * Voice: **use the same pre‑recorded WAV/MP3 played twice into the radio, with the same start/stop timing. Avoid live re‑speaking**.
  * If your radio supports **sending a stored voice memo or test prompt, use that for exact repeatability**.
  * Keep transmissions back‑to‑back to minimize any system changes.

* Scope/Size
  
  * 10–20 seconds per voice capture is enough. One short text message per clear/encrypted is fine.
  * Please avoid compressing the files (ZIP is OK; no lossy audio re‑encoding).

I will work on this and then send it to you.

[taradeved]

This vertex sample https://drive.google.com/file/d/1FCZe9ryYLhcHcy-cE2sijLxNqnofZyCz/view?usp=sharing

[taradeved]

ths is uncrypted sample https://drive.google.com/file/d/1g-OC6ctXroOqeqNOmu7q89q-pFA8xy3e/view?usp=sharing

[taradeved]

this message "00000000000000" ,key encryption '1234567891'
https://limewire.com/d/Idin5#uIo2mMfAUd

[arancormonk]

thanks, do you also have the unencrypted text message as requested?

What To Capture (exactly 4 items)

Voice (clear): one capture of a short voice transmission unencrypted.
Voice (encrypted): the exact same voice transmission, but encrypted.
Text (clear): one capture of a short text message unencrypted.
Text (encrypted): the exact same text message, but encrypted.

[falkrist]

tested this flag "-1 Manually Enter RC4 or DES Key Value (DMR, P25, NXDN) (Hex Value)" for my old one Retevis P1 radio with RC4 (10 symbols) key (which successfully decoded with dsd-fme) - doesn't decrypt also. Probably need to open separate case, but saw descussion around "-1" flag and decided to reply :)

[arancormonk]

tested this flag "-1 Manually Enter RC4 or DES Key Value (DMR, P25, NXDN) (Hex Value)" for my old one Retevis P1 radio with RC4 (10 symbols) key (which successfully decoded with dsd-fme) - doesn't decrypt also. Probably need to open separate case, but saw descussion around "-1" flag and decided to reply :)

i made a separate issue: #35