For those of you who have looked at the 032 auto updating
stuff coming out of Canada *****BEWARE*****.
I have analyzed and disassembled the code and have found
the following.
1.  There are no seed keys, encrypted or otherwise in the RAM
   loader.
2.  Instead, the DES derived unit key is precalculated from the
   seed keys, ID, and a **FIXED** key selector byte string.
3.  The derived unit key is injected into RAM by the loader chip
   and the run chip then uses this derived unit key for all
   future working key calculations.
So what's the problem you say?
Well, all GI has to do is change the key selector byte string,
and the derived unit key put into U20 by the loader chip is no
longer valid.  So what, you say!  Well, your run chip is now no
longer able to compute a valid working key and will not decode
audio until the box has U20 rewritten with the latest derived
unit key.
Shame on the developers of this software.  This problem happened
nearly two years ago.  Doesn't anyone ever learn?


You are viewing proxied material from infinitelyremote.com. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.