OP25 Issues with ADP decoding

[Reconrider]

I have op25 boatbod setup
I have a valid ADP key to a single frequency system.

I enter the key, keyID and algo then load up op25 - no errors

Using the premade encryption_key.json file, I set everything up and put in like I see the others were.
With op25 loaded, the only correct is the keyid and some of the key. Why is the bytes with characters in it not seen correctly by op25?

rx.py
./rx.py  --args "rtl" --gains 'lna:36' -S 960000 -X -q 1 -v 11 -V -U --crypt-behavior 0 -k encryption1_keys.json -T conv.tsv 2> conv.log


{                          (changed numbers w/ another number and characters with another character)
    "0x0070":{ "algid": "0xaa", "key": [ "0x34", "0x09", "0xB4", "0x35", "0x7A" ]}
}

KeyID: 0070
Key: 3409B4357A

 

[mtindor]

I have op25 boatbod setup
I have a valid ADP key to a single frequency system.

I enter the key, keyID and algo then load up op25 - no errors

Using the premade encryption_key.json file, I set everything up and put in like I see the others were.
With op25 loaded, the only correct is the keyid and some of the key. Why is the bytes with characters in it not seen correctly by op25?

rx.py
./rx.py  --args "rtl" --gains 'lna:36' -S 960000 -X -q 1 -v 11 -V -U --crypt-behavior 0 -k encryption1_keys.json -T conv.tsv 2> conv.log


{                          (changed numbers w/ another number and characters with another character)
    "0x0070":{ "algid": "0xaa", "key": [ "0x34", "0x09", "0xB4", "0x35", "0x7A" ]}
}

KeyID: 0070
Key: 3409B4357A

Interesting issue. I've only ever had an all-numeral key to work with. And the example I think also was all numeral. Unsure why your key wouldn't work. After all, with the 0x prefix it's clearly expecting hex, and you clearly have valid hex bytes.

 

[hazrat8990]

Is it possible that it needs to be entered as decimal vs. HEX? Maybe try Decimal to Hexadecimal Converter

 

[Reconrider]

Interesting issue. I've only ever had an all-numeral key to work with. And the example I think also was all numeral. Unsure why your key wouldn't work. After all, with the 0x prefix it's clearly expecting hex, and you clearly have valid hex bytes.

That's my exact thought also. Here's what op25(boatbod) outputs the crypt_key as
"crypt_key", "keyid": 112, "algid": 170, "key": [52, 9, 180, 53, 122]})

 

[Reconrider]

Is it possible that it needs to be entered as decimal vs. HEX? Maybe try Decimal to Hexadecimal Converter

That's possible, except the 0xB4, 0x7A are technically already hex. A and B are not valid decimal characters. I check again on the website you giveth me as a second try though.
The decimal box drops the 'A' and 'B'

 

[hazrat8990]

Your key ID 112 is 70 when converted to HEX. When you convert 0070 HEX back to decimal, you get 112.

 

[Reconrider]

Your key ID 112 is 70 when converted to HEX. When you convert 0070 HEX back to decimal, you get 112.

You're not understanding.
The keyID is not my issue here since that is correct. my issue is the actual key is not being seen my OP25 correctly because of the A and B characters where I define it

The keyID is perfectly fine. It's the ADP key not working

 

[mtindor]

That's my exact thought also. Here's what op25(boatbod) outputs the crypt_key as
"crypt_key", "keyid": 112, "algid": 170, "key": [52, 9, 180, 53, 122]})

So it outputs it in decimal? But the decimal values all are exactly what you would expect based upon the hex you previously posted. Don’t you agree?

 

[hazrat8990]

You're not understanding.
The keyID is not my issue here since that is correct. my issue is the actual key is not being seen my OP25 correctly because of the A and B characters where I define it

The keyID is perfectly fine. It's the ADP key not working

I am understanding just fine, I was just pointing out the correlation of decimal vs. HEX in your previous posts. The values in the first quoted post are HEX, and the second is decimal. I just focused on the key ID itself, instead of the actual key.

KeyID: 0070
Key: 3409B4357A
[/code]

That's my exact thought also. Here's what op25(boatbod) outputs the crypt_key as
"crypt_key", "keyid": 112, "algid": 170, "key": [52, 9, 180, 53, 122]})

 

[Reconrider]

I am understanding just fine, I was just pointing out the correlation of decimal vs. HEX in your previous posts. The values in the first quoted post are HEX, and the second is decimal. I just focused on the key ID itself, instead of the actual key.

Ahh my bad, didn't realize that. So in OP that's my "code" I put in op25 to run.
The crypt_key is from op25 upon start up. That's what I'm given.
And yes, the keyid is actually 112 but in the json file I put it as 0070 because that's the hex so it works correctly.

 

[mtindor]

Ahh my bad, didn't realize that. So in OP that's my "code" I put in op25 to run.
The crypt_key is from op25 upon start up. That's what I'm given.
And yes, the keyid is actually 112 but in the json file I put it as 0070 because that's the hex so it works correctly.

Assuming you have the right key from where you got it, I believe you put it in 100% correct. And what it is outputting seems to be 100% correct, only in decimal instead of hex

 

[hazrat8990]

KeyID: 0070
Key: 3409B4357A

Maybe they need to be entered as:
KeyID: 112
Key: 223501104506

 

[mtindor]

KeyID: 0070
Key: 3409B4357A

Maybe they need to be entered as:
KeyID: 112
Key: 223501104506

I can tell you that I had a key that was all numerals. In my file, I put the ALG ID and the key ID in as hex and also put the actual key in as hex. If my key was 3131313131 i put it in as 0x31 across-the-board

So for me, it was all hex in the file. The key is 10 character, hex. Like I said, I believe you added it in correctly, everything in hex. And the values it spits out in decimal, match the hex values.

I can only guess that the key itself is incorrect. The fact that OP 25 spits out the information suggested it is reading the file. It’s been so long ago since I messed with it.

 

[Reconrider]

Assuming you have the right key from where you got it, I believe you put it in 100% correct. And what it is outputting seems to be 100% correct, only in decimal instead of hex

Key does work without a doubt. dsd fme confirms by decoding the audio in clear.

KeyID: 0070
Key: 3409B4357A

Maybe they need to be entered as:
KeyID: 112
Key: 223501104506

Can you explain how you got the decimal key please. Every time I am to enter it, it is removed.

I can tell you that I had a key that was all numerals. In my file, I put the ALG ID and the key ID in as hex and also put the actual key in as hex. If my key was 3131313131 i put it in as 0x31 across-the-board

So for me, it was all hex in the file. The key is 10 character, hex. Like I said, I believe you added it in correctly, everything in hex. And the values it spits out in decimal, match the hex values.

I can only guess that the key itself is incorrect. The fact that OP 25 spits out the information suggested it is reading the file. It’s been so long ago since I messed with it.

I tried it with the actual key and converting it to hex and adding it as a byte in the key.json file. for some reason it doesn't work correctly for me. Inoring that broadcasted info, listening to the garble come through proves the key is somehow incorrect also sadly

 

[mtindor]

Key does work without a doubt. dsd fme confirms by decoding the audio in clear.

Can you explain how you got the decimal key please. Every time I am to enter it, it is removed.

I tried it with the actual key and converting it to hex and adding it as a byte in the key.json file. for some reason it doesn't work correctly for me. Inoring that broadcasted info, listening to the garble come through proves the key is somehow incorrect also sadly

I should add that I don’t know if the key that I was given was in hex. I just know that in my case it was all numerals and I added it exactly like you added it, from left to right, with 0X31 0X31 etc.

I never paid attention to what OP 25 spit out, but I’m guessing it spit out everything and I’ll decimal like it did for you. Unfortunately, I don’t have that accessible to me right now to look and tell you for sure I think you follow the procedure based upon the instructions.

 

[mtindor]

Are you sure that you should have the value 0 for —crypt-behavior ? I can’t remember if that’s what I had or not.

 

[Reconrider]

I should add that I don’t know if the key that I was given was in hex. I just know that in my case it was all numerals and I added it exactly like you added it, from left to right, with 0X31 0X31 etc.

I never paid attention to what OP 25 spit out, but I’m guessing it spit out everything and I’ll decimal like it did for you. Unfortunately, I don’t have that accessible to me right now to look and tell you for sure I think you follow the procedure based upon the instructions.

I'm unsure of that same thing honestly. The key was given to me for testing. dsd-fme, unication g5 both work with no issues. But I really want op25 to work because it's a great program

Are you sure that you should have the value 0 for —crypt-behavior ? I can’t remember if that’s what I had or not.

I do have that in my rx.py command

./rx.py --args "rtl" --gains 'lna:36' -S 960000 -X -q 1 -v 11 -V -U --crypt-behavior 0 -k encryption1_keys.json -T conv.tsv 2> conv.log

 

[mtindor]

I know that —crypt-behavior=2 skips all encrypted stuff but i dont remember what 0 and 1 do. That is why I question if you are sure that zero is the correct value. Obviously you do not want 2.

 

[mtindor]

I wonder if it is simply because you don’t have the equal sign in there

—crypt-behavior=0

 

[Reconrider]

I know that —crypt-behavior=2 skips all encrypted stuff but i dont remember what 0 and 1 do. That is why I question if you are sure that zero is the correct value. Obviously you do not want 2.

--crypt-behavior=CRYPT_BEHAVIOR
encrypted traffic behavior: 0=allow, 1=silence, 2=skip

I wonder if it is simply because you don’t have the equal sign in there

—crypt-behavior=0

That's a possibility I would like to say I attempted and nothing came of it. But I'm willing to try it a second time to make sure