### New Keys are HERE!!! ###

[skinterz]

we all down in the swansea area, we on VM dbox 2 cant change keys all on auto .

[THFC]

Used Flash FTP in my TW area on DM600 Pli iolite image- latest one

Edited the key.txt file as mentioned - had to use edit not view command in ftp else changes did not occur

Also - Au setting is now (00)

Using (02) it seemed to change my keys back to original values.

Will play around altering this maybe later back to (02) and check again.

All channels cleared immediately on reboot.

Thanks for all the help guys - seemed easy enough - hope above helps others too

[Dr Evil]

Idiots guide to updating your keys on dm500c

Hi All,

I have put together a guide detailing how to manually update your dreambox 500c keys. With any luck it won't be long before we can enjoy auto updates again.

In the example I have used keys taken from the "KeyMaster" application (submitted by DevilFish - cheers) "TW Keys"; Obviously use the set for your area. The guide is also written for use with the DK image.

Best,

Rob

[yid0]

Just been reading on another forum that the C+W keys on keymaster are incorrect and so we have to wait for new ones. This would explain my difficulties> Can anyone else add anymore to this?

Cheers in Advance

That explains my difficulties too. can you post a link to that discussion or keep me posted with developments if you hear of anything?

[dave2014]

That explains my difficulties too. can you post a link to that discussion or keep me posted with developments if you hear of anything?

If I hear anything else I'll post it or let you know mate. Wasnt much to the discussion, I just noticed it said that C+W keys are wrong and we will have to wait for new ones.

[resonance]

ok, used the keymaster and made changes to the keys text file and and changed to gbox instead of evocam and am getting the channels now.

thanks to all concerned

[singhzibit]

hi i was wondering if somebody could help me,my problem is that my sv 3 box has been working for months and i have just done a factory reset then re-scaned and switched on emu but all i get is "data being updated" but moves up to 100%.all i get is free to air channels. please help would be very appreciated if possible please email me on.

[Derekwd]

ex c+w keys from keymaster not working for me. can anyone else confirm exc+w keys dont work?

Same here m8, ex c&w not working with keymaster keys.

Derek

[Kevin'']

hi i was wondering if somebody could help me,my problem is that my sv 3 box has been working for months and i have just done a factory reset then re-scaned and switched on emu but all i get is "data being updated" but moves up to 100%.all i get is free to air channels. please help would be very appreciated if possible please email me on [email protected]

likes already been said VM has most liekly found a way to crackdown on them so you will need new firmware to auto scan in the future

[jholmes]

ex c+w keys from keymaster not working for me. can anyone else confirm exc+w keys dont work?

leeds c&w not working here either, but still havent got any posts back on which is the right provider code to use is it NTL provider code or C&W provider code?

[dave2014]

Same here m8, ex c&w not working with keymaster keys.

Derek

I posted about this earlier, apparently the keys for C+W on keymaster are incorrect and we will have to wait for new ones, not sure when these will appear. If I hear anymore I will post

[dave2014]

leeds c&w not working here either, but still havent got any posts back on which is the right provider code to use is it NTL provider code or C&W provider code?

If your in an ex C&W area you should use the C&W key codes

[Fspiders]

VM have used the swap byte method again (3rd time now). The only survivors of this attack are the original moscs.

The reason your box isn't working is cos the code/card that does your descrambling is a mosc emulator and the calculation formula for swapping the byte isn't in the code where as it is in an original mosc (or if it isn't then it can easily be added at the update). The code/card we are using doesn't have this info (As no emulator can emulate something that hasn't occured) so therefore cannot work it out. In a nutshell it gets the code from the feed and only knows certain ways to calculate the resulting keys. Where as the original VM cards already have the info to do the sums.

The swap byte method is pretty cool as it's telling the box "Here.. this is your keys. use them to get a picture" but in effect one number in each key is false. The box gets totally confused and constantly tries to update.

Now a Guru will look at the logs and work out what formula they're using and then will incorporate it into the code of your updates. Once the emulator has this info they can't use that particular attack again and in future VM will have to use another part of the mosc memory to store another swap byte formula.

This is why non-moscs are hit... It's impossible to defend against something that hasn't happened till it happens.

Regards.

[animal666]

struggling myself here. but im sure we will only need to wwait a while and everything will be sorted out. come on you magicians.

[dave2014]

VM have used the swap byte method again (3rd time now). The only survivors of this attack are the original moscs.

The reason your box isn't working is cos the code/card that does your descrambling is a mosc emulator and the calculation formula for swapping the byte isn't in the code where as it is in an original mosc (or if it isn't then it can easily be added at the update). The code/card we are using doesn't have this info (As no emulator can emulate something that hasn't occured) so therefore cannot work it out. In a nutshell it gets the code from the feed and only knows certain ways to calculate the resulting keys. Where as the original VM cards already have the info to do the sums.

The swap byte method is pretty cool as it's telling the box "Here.. this is your keys. use them to get a picture" but in effect one number in each key is false. The box gets totally confused and constantly tries to update.

Now a Guru will look at the logs and work out what formula they're using and then will incorporate it into the code of your updates. Once the emulator has this info they can't use that particular attack again and in future VM will have to use another part of the mosc memory to store another swap byte formula.

This is why non-moscs are hit... It's impossible to defend against something that hasn't happened till it happens.

Regards.

Great stuff mate. I actually enjoyed reading that and now have a much better idea of what goes on. Cheers