Basic FAQ about keys, emu, softcams etc.

GaryM

Inactive User
Joined
Feb 24, 2007
Messages
585
Reaction score
3
That explains what Emus, Cams and Keys are, also what purpose they serve in an image and why we would use different ones?
I'd love to know for certain so if anybody can point me to a relevant post or even try to explain I'd appreciate it.
 
There are two types of channel that are sent out by the cable company; FTA (free-to-air) and encrypted.

Free-to-air channels are basically freeview channels. You don't need to subscribe to a package to get these channels. If you use an image without an emu or keys you would still get these channels.

Encrypted channels are channels that the cable company want you to pay for. These channels are encrypted before being sent out and normally you would pay the cable company for a smartcard which you would slot into your recevicer and this will allow you to receive the encrypted channels. It's kinda like when you buy software and you get a key with it. You won't be able to use the software without knowing the key.

Keys are also included in the cable stream. Normally your digital smartcard will extract the keys from the stream and store them in memory. It would then use these keys to decrypt the channels when you flick through them. Since we don't use a smartcard with a dbox we need something else to decrypt the channels. This is where the softcam (also known as a cam or emulator (emu)) comes in. The box or image itself doesn't know what to do with the keys, it's the softcam that grabs the keys from the stream and stores them in a file (keylist.txt, Autoroll.key, Autoupdate.key). If the keys are changed by the cable company the softcam will update the keys stored in the file.

The enctytion that the cable companies use is called Nagra1. So we also need to include nagra rom files in our images. These go in /var/scce and /var/keys.

There are several different softcams that we can use; evocamd, mgcamd, newcamd & gbox. It doesn't really matter what one you use, they all do the same thing. Some emu won't work in certain areas or on certain providers so it's good there are alternatives. The emu can also cause problems with direct recording over ethernet so if you have a blocky recording, try changing the emu or the tuner driver.

The different emu can be found at dreamboxworld.com.

I hope this is what you were looking for. :)
 
Last edited:
Excellent reading and very helpful. Thanks.
 
One more if I may?

Once you install a cam in an image will the cam sort the keys out?
So a generic image, all thats needed is cams and a cables.xml file?
 
Depending on what emu you have running there will be a different key file and different auto update file.

mgcamd - Softcam.key, Autoroll.key
evocamd - Keylist.key, Autoupdate.key

When the cable company changes the keys, known as rolling the keys, the softcam detects a command that's sent to the subbed boxes and automatically grabs the new set of keys and updates the appropriate file.

So you can take a basic image and what you need to do get it working on uk cable is...

Add cables.xml (for scanning)
Add keys and nagra roms (for decoding encrypted channels)
Add softcam (evocamd, mgcamd, etc) (for autoupdating the keys)
 
Last edited:
The enctytion that the cable companies use is called Nagra1. So we also need to include nagra rom files in our images. These go in /var/scce and /var/keys.

This is where I am confused.Where do you get the nagra rom files ? I have tried to mod images in the past and installed say ecocamd 2.14, but when i scan, no "scrambled" channels will clear. The image is missing the roms. When i copy the roms over, all is well. What i am asking is, when you install an EMU, does that install the roms or do they need to b e installed separately ?? Hope this makes sense !!!!!!!
 
Have a search for satan key bundle has everything inside you need.

Frenchman
 
does the Emus, Cams and Keys come included with the dw image or or they installed seperate ?
 
Great replys but am still none the wiser as to where one gets the rom files from.( I sound like the queen ( one had an anus horribulus) LOL.
 
I'm not sure where they originally came from. Maybe we got them when someone opened up a cable company card...I don't really know?
 
I uploaded them here a while back - special files, courtsey osborne82
 
Just come across this interesting old thread. Is it possible to start with a blank keylist.txt? Will evocamd write the keys into a blank keylist.txt or does it have to the providers already in the the keylist? i.e. N 5A01 XXXXXXXXXXXXXX ;date etc...?
 
Yes you can have a blank file...completely empty.

The DW v2.0 image comes this way. Both keylist.txt and Softcam.key files are naked!

In fact, I've never tested it before but you might even get away with not having a file at all. When you run gbox for the first time, it creates a file called 'nagra' to store the keys. Evocamd and mgcamd might do the same but never tested it, just thought of it there lol.
 
Thanks Devilfish, trying to get to the bottom of why evo wont au for me. Going to try this, also going to manually install the emu. Is it a good idea to have the roms in the keys file aswell as the scce folder?
 
Just had another thought, am I right in saying that all evocamd requires to work is /usr/keys/Keylist.key, Autoupdate.key, camd_cfg & rom 7 files in scce? Can all other files be deleted?
 
Yes m8, that's correct.

The later versions of evocamd, i.e. 2.16 & 2.17 require a newcamd-client.txt and feynman.cfg file. Not 100% sure why but think it's cardsharing related so doesn't affect the cable scene, but it still looks for these files and doesn't go past that point until it has them. That's why you're better off with 2.12 or 2.13.

I'm sure you only need the rom files in /scce but some images have a symlink from /scce to /keys so it's necessary to have all files in /keys. You can by all means try it out, they can be deleted if it doesn't work.
 
Last edited:
WOO HOO SUCCESS!!!!!!!!

Thankyou Devilfish :)

Cleared contents of keylist.txt. Already had newcamd-client.txt in keys folder, added feynman.cfg. Chmodded etc..Switched back to evocamd 2.17 xmas fix, rebooted. Few secs later it au'd :)

Checked keylist.txt which was blank, new keys had auto written to file. So happy :)

I hate things beating me & wasn't going to back down until I found the answer.

So a big thanks to everyone who has made suggestions in various threads.

/me is a very very happy man LOL.

Perhaps it might be an idea to state in this thread https://www.digitalworldz.co.uk/index.php?threads/139503/ under Evocamd that 2.16 onwards requires newcamd-client.txt and feynman.cfg.

Again a big thanks to all.

Perhaps it might be an idea to make this thread a sticky.
 
Last edited by a moderator:
Back
Top