I installed DSD fast lane paid version. I am still learning to use this but am able to pickup analog and P25 channels so far. It claims to display the encryption key on a encrypted freq. I have tried this on 2 DMR encrypted freq but i am not seeing the key. I have the even log menu set for "encrypted voice call following - full following". I attached a screen shot of what i am receiveing. Any suggestion to get the key to display?
DSD fast lane encryption key
- Thread starter lkas
- Start date
I don't believe DMR broadcasts the key (which is NOT the actual encryption key, just the key ID number), I've only seen it on P25 myself.
Where did you see this claim? I'm intrigued
CanesFan95
Analog already is interoperable.
That's not the actual encryption key. No system is going to just divulge that for the world to see. What it's showing is the Key ID which just the numbering used to program keys into a radio (a radio can have more than 1 encryption key loaded into it). For example, encryption key #1, encryption key #2, etc., but not the actual key itself.
The encrypted voice call following is only telling DSD+ if you want to stop on encrypted TGs but does not actually decode 'em cause you don't have/know the key. If you opt to tell DSD+ to stop on encrypted TGs, you will not actually hear anything, or maybe an initial blip of encrypted noise until DSD+ mutes the audio altogether.
The encrypted voice call following is only telling DSD+ if you want to stop on encrypted TGs but does not actually decode 'em cause you don't have/know the key. If you opt to tell DSD+ to stop on encrypted TGs, you will not actually hear anything, or maybe an initial blip of encrypted noise until DSD+ mutes the audio altogether.
It doesn't display the key, it displays the key number. So if I have a multikey radio, I may have 5 keys for 5 channels or systems.
The program shows the "alias" of the key for lack of a better term. Nothing to do with monitoring the encrypted conversation.
The program shows the "alias" of the key for lack of a better term. Nothing to do with monitoring the encrypted conversation.
Wouldn't be any reason to encrypt if the key was easily available. You just missed the word ID after key, it is the encryption Key ID only.
As has been stated already, it displays the KeyID, not the actual key data. Key data is never broadcast over the air, as that would defeat the entire purpose of encryption if it were that easy to capture the actual key data.
As for DSD+ showing the KeyID, you're only going to see that broadcast over the traffic channels, not over the control channel. You need to allow DSD+ to tune to encrypted transmissions in order to see the KeyID.
As for DSD+ showing the KeyID, you're only going to see that broadcast over the traffic channels, not over the control channel. You need to allow DSD+ to tune to encrypted transmissions in order to see the KeyID.
Lastly, there are no key IDs for DMR Basic Privacy.
learn something knew everyday
Out of all of those replies, you are the only one who answered correctly. Everyone else was talking about RC4 or higher encryption, and they (for the most part) were correct about KeyIDs.
like i said.... learn something new every day
slicerwizard
Member
DMR encrypted comms transmit KID values. (BP is not encryption; it's just pizzpoor scrambling)
Similar threads
