That makes sense, but I think I just saw the "key" fly by a few seconds ago, and with a keyspace of only 255 possibilities it is pretty trivial to get on the system. It just means that to attack the system it takes a little bit more money to purchase the correct radio and an hour to brute force the key by hand--it doesn't really change the situation, just the hardware required for the attack.
Besides, an someone could always wait for an authorized user to key up and overpower the input signal to the repeater.
I guess if you look at the number of ESK capable radios in the hands of people that would want to cause problems it does buy some protection for a short while. It would make sense that they would change it at the last minute before the DNC without any public announcement--pretty genius actually, seeing as it really is the only way to make it effective for preventing tampering is to use the element of surprise while people scramble to get new hardware. It makes you wonder if they had a credible threat of someone using interference to disrupt their response during the DNC.
I just got my new BC246T in May as a birthday present so I am really bumbed. It's now just about totally useless. Will be awhile before I can affor $500 for a new scanner.
Anyone know which states don't use ESK but the EADS. I'll try to sell it I guess.
I live in the heart of Denver and really can't get Aurora or Arvada very much.
If I'm reading the reply to SlamX correctly, the Uniden firmware update won't help any scanner to receive Denver except for the 396 and 996.
OK sorry to get anyone’s hopes up. I did see the update page and all the models listed. However, did not pay real close attention to this line......
No worries Chris, I got trumped up on that one also. I was thinking there was info recently released that I hadn't seen yet.OK sorry to get anyone’s hopes up. I did see the update page and all the models listed. However, did not pay real close attention to this line......
EDACS ESK Support: We’ll be adding ESK support to both the BCD396T and the BCD996T.
So, my error and I apologize.
I downloaded the firmware last night, and i actually went threw the 0-160#'s for Denver and soon i put in the 160 in it work, I think it was DGrove who said that 160 was for WheatRidge and put that one in right away and it work right off..Earlier this AM i just found on the Uniden forum by UPMan that 160 is a default setting for EDACS radios. Everything is working great on my end..I did..and 160 is correct for Denver also, and it does work (the firmware change allows trunktracking).
If they can get it to work on their analog scanners I cannot see why not. Sales of their analog trunking scanner line would definitely jump in ESK regions instead of sales going to the competition.