arsh
12-20-2007, 06:17 AM
Here's how the new rev248 is working AT THIS TIME.
Friday or Saturday BEV sends down a new mecm40 or mecm60 algo to the cards. So far this has come down globally and everyone in the stream gets it as long as there is no blocker. However, this code is sitting on the CAM Encrypted . We cannot decrypt it until we get the new 0907 keyXX for that new mecmXX. Along comes Sunday morning and BEV sends down the 0907 keyXX for the new mecmXX. Again, at this point these have been sent globally, everyone gets these. The nfl tier which usually expires every wednesday is updated or replaced with a new one. These updates are only sent to the subs(in general ).
Now, right before game time they will „activate” the new mecmXX algo. First step in the ecm is the 9F checks the USW and see's if you've received the mecmXX update to the codespace(Each Encrypted mecm algo is 100h bytes long). If you haven't received it, it exits and you have black screen. If you have the correct USW, meaning you got the update, it says, cool, go get the 0907 keyXX and decrypt this @!#$ in the codespace and throw it up in ram at $0100 and execute it so you can get the correct control words and some video. Of course tier check, dt's, etc come into play too. That decrypted @!#$ is where they were running code using the timer registers to morph the control words. The trick to all the timers is if certain bits are set, the card ignores some of the next commands. All is fine on plastic because it really knows what to do when particular bits are set/cleared. However, an emulator may not know all the rules so it follows the orders of the code and sets and clears bits even though the card wouldn't because it's an „illegal” command. Again, the card knows the rules, it is inherent in it's manufacturing, emulators only know the rules they are programmed to know, hence atmega goes down, fta's and anything else that doesn't have the rules right.
BEV has been playing nice actually, they've only been implementing mecm40 or mecm60 during nfl and only on the nfl channels, the rest of the channels have no mecmXX post processing. What I'm suprised they haven't done yet is send down BOTH new mecm40/60 and turn on one for regular channels and the other for nfl. For example, mecm40 for regular and mecm60 for nfl. FTA and other go dark on ALL channels till new algo can be understood and implemented. During the couple of days it takes to „fix” the fta's they've turned off MECM60 since nfl channels go dark anyway at the end of the day and write a new one, then about the time the fta's have released a fix to get the normal channels back up, they've already sent down a new mecm60 algo and just „activate” that promptly to kill the fta release while they start sending down a new mecm40. They can toggle between algo's at will too. Are you starting to see the cycle?
Now, to further add, this is just the beginning of what rev248 can do. Sure sounds like misery for the fta's, no? But wait, there's more. How about those 10-12 „new” map calls sitting down at the bottom of the new rev that are unused so far? Well, as you can see, any plastic „autoroll” option is going to have to allow codespace changes so the new Encrypted algo's can be written. All these map calls load and move map registers. They could be nice and just load the map registers to build keys, so if they load a map register with data from your blocker code, well, you just lost video. However, why would they be so nice?
__________________
Friday or Saturday BEV sends down a new mecm40 or mecm60 algo to the cards. So far this has come down globally and everyone in the stream gets it as long as there is no blocker. However, this code is sitting on the CAM Encrypted . We cannot decrypt it until we get the new 0907 keyXX for that new mecmXX. Along comes Sunday morning and BEV sends down the 0907 keyXX for the new mecmXX. Again, at this point these have been sent globally, everyone gets these. The nfl tier which usually expires every wednesday is updated or replaced with a new one. These updates are only sent to the subs(in general ).
Now, right before game time they will „activate” the new mecmXX algo. First step in the ecm is the 9F checks the USW and see's if you've received the mecmXX update to the codespace(Each Encrypted mecm algo is 100h bytes long). If you haven't received it, it exits and you have black screen. If you have the correct USW, meaning you got the update, it says, cool, go get the 0907 keyXX and decrypt this @!#$ in the codespace and throw it up in ram at $0100 and execute it so you can get the correct control words and some video. Of course tier check, dt's, etc come into play too. That decrypted @!#$ is where they were running code using the timer registers to morph the control words. The trick to all the timers is if certain bits are set, the card ignores some of the next commands. All is fine on plastic because it really knows what to do when particular bits are set/cleared. However, an emulator may not know all the rules so it follows the orders of the code and sets and clears bits even though the card wouldn't because it's an „illegal” command. Again, the card knows the rules, it is inherent in it's manufacturing, emulators only know the rules they are programmed to know, hence atmega goes down, fta's and anything else that doesn't have the rules right.
BEV has been playing nice actually, they've only been implementing mecm40 or mecm60 during nfl and only on the nfl channels, the rest of the channels have no mecmXX post processing. What I'm suprised they haven't done yet is send down BOTH new mecm40/60 and turn on one for regular channels and the other for nfl. For example, mecm40 for regular and mecm60 for nfl. FTA and other go dark on ALL channels till new algo can be understood and implemented. During the couple of days it takes to „fix” the fta's they've turned off MECM60 since nfl channels go dark anyway at the end of the day and write a new one, then about the time the fta's have released a fix to get the normal channels back up, they've already sent down a new mecm60 algo and just „activate” that promptly to kill the fta release while they start sending down a new mecm40. They can toggle between algo's at will too. Are you starting to see the cycle?
Now, to further add, this is just the beginning of what rev248 can do. Sure sounds like misery for the fta's, no? But wait, there's more. How about those 10-12 „new” map calls sitting down at the bottom of the new rev that are unused so far? Well, as you can see, any plastic „autoroll” option is going to have to allow codespace changes so the new Encrypted algo's can be written. All these map calls load and move map registers. They could be nice and just load the map registers to build keys, so if they load a map register with data from your blocker code, well, you just lost video. However, why would they be so nice?
__________________