seaboard18
06-20-2006, 07:28 AM
It is really interesting though that this has happened and I have yet to read a post from someone who claims to know the what and why of this. Many forums and no one knows or suggests that they know.
The closest I've seen is that Chuck is getting ready for Rev109, but who knows?
I would hope that subs were the reason why! However, that would not explain why Bev is up. I think I read BEV was up, is this correct? Bev was there testing ground for the cmd 07 in the first place. Keys have not changed on either system. 5-07-06 and 5-26-06.
It appears that they are planning to start using EMM $F3 prior to CMD07. This means that a CMD04 will have to be decrypted immediately prior to a CMD07 for proper video authorization. In other words, they will be speeding up the datastream. If you can't decrypt a CMD04 in less then 2 seconds - game over. mili
I would think that the provider could simulate the cmd 04 easy enough or test the cmd 04 on there testing channels on either system while remaining secure, using only the cmd 07 for subs on both systems.
What is possible is that the provider has lost 102 cams in the subbed population in the past few weeks or days due to the original cmd 07 speed change. There is a limit as to how fast commands can be processed using the 102 cryptoprocessor. Engineers that design micro chips to function within a certain tolerance which includes speed and heat, along with many more tolerances. If tolerance is exceeded for a long period of time, these devices will fail. Some of the original 102 cards were in use back in the N1 days. N2 revisions to these cards could be part of the providers problem because they were not ever replaced by the provider.
The provider was forced into securing the stream by the CRTC and the FCC. The engineers that work for these organizations said in theory it would work to secure the stream. However those engineers did not design this cam.
The concept of what I wrote above is possible, if this is not the case then expect the cmd 07 to return including the cmd 04 as Mili proposed in his post above. This should serve as a quick explanation only and don't bank on it as the reason unless Rom 10 continues to work for a long period of time. What I described is a system failure of a cam, which is possible. Thanks for reading my post. :D
Seaboard
The closest I've seen is that Chuck is getting ready for Rev109, but who knows?
I would hope that subs were the reason why! However, that would not explain why Bev is up. I think I read BEV was up, is this correct? Bev was there testing ground for the cmd 07 in the first place. Keys have not changed on either system. 5-07-06 and 5-26-06.
It appears that they are planning to start using EMM $F3 prior to CMD07. This means that a CMD04 will have to be decrypted immediately prior to a CMD07 for proper video authorization. In other words, they will be speeding up the datastream. If you can't decrypt a CMD04 in less then 2 seconds - game over. mili
I would think that the provider could simulate the cmd 04 easy enough or test the cmd 04 on there testing channels on either system while remaining secure, using only the cmd 07 for subs on both systems.
What is possible is that the provider has lost 102 cams in the subbed population in the past few weeks or days due to the original cmd 07 speed change. There is a limit as to how fast commands can be processed using the 102 cryptoprocessor. Engineers that design micro chips to function within a certain tolerance which includes speed and heat, along with many more tolerances. If tolerance is exceeded for a long period of time, these devices will fail. Some of the original 102 cards were in use back in the N1 days. N2 revisions to these cards could be part of the providers problem because they were not ever replaced by the provider.
The provider was forced into securing the stream by the CRTC and the FCC. The engineers that work for these organizations said in theory it would work to secure the stream. However those engineers did not design this cam.
The concept of what I wrote above is possible, if this is not the case then expect the cmd 07 to return including the cmd 04 as Mili proposed in his post above. This should serve as a quick explanation only and don't bank on it as the reason unless Rom 10 continues to work for a long period of time. What I described is a system failure of a cam, which is possible. Thanks for reading my post. :D
Seaboard