OScam Emu New Method for PVU keys Discussions

Quote from jenseneverest

For me it is just a cleaner more organised file, the end result is the same.

Peeps really should read the wiki

Matching ECM and EMM keys based on transponder (new method - May 2019)

The traditional method of getting ECM keys is based on matching the srvid of the channel only. This means the ECM algorithm does not match the group id at all when searching for the ECM key. If many ECM keys with the same srvid (see Note 1 below) are present in the SoftCam.Key, they are all tried until the correct one is found.

In addition, the EMM algorithm does not match the group id as well. The EMM keys used for auto updating can be chosen from various groups (see Note 3) and as a result wrong EMM keys can be used.

The new approach is to utilize the group id of the channel when the ECM and EMM algorithms run. In order OSCam-Emu to know what is the correct group id to use, it calculates a hash based on tsid, onid and enigma namespace of the transponder. The user then needs to enter a new line in the SoftCam.key telling OSCam-Emu which group id to use for each transponder (hash).

The syntax for this line is the following:

Code

P <hash> GROUP <groupid>

Where:

Code

hash    (4 bytes) :  Transponder hash calculated automatically by OSCam-Emu. Use debug level 2 to display it.
groupid (2 bytes) :  The group id that is used for the ECM and EMM keys.

Example:

Code

P BF175115 GROUP 0080 ; 12303 V, 0.8°W
P ACE05CA0 GROUP 0080 ; 12360 V, 4.8°E

P 9798A8F2 GROUP 0900 ; 11804 V, 9.0°E

Transponders using the same ECM and EMM keys should use the same group (this should be the case for the traditional method as well) and thus multiple "GROUP" entries should exist for that group id.

After adding the GROUP instruction for a group, the next step is to remove all ECM keys for that group and enter a new one with the dummy srvid 0xFFFF. For example:

Code

P 0900FFFF 00 00000000000000 ; ECM Key
P 0900FFFF 01 00000000000000 ; ECM Key

The EMM keys should remain untouched. After restarting the Emu reader, the new method should take over for both the ECM algorithm and the EMM (AU) aglorithm.

The advantages of this new method are many:

• One ECM key is used for all channels in a transponder, so the SoftCam.Key has smaller size and it's easier to maintain and update.
• Memory consumption is lower and getting the correct key is faster.
• All problems described in Note 3 are disappeared, which makes creating a proper, trouble-free SoftCam.Key easier for all.

On the other hand there is a couple of drawbacks:

• The application of this new method is limited to STBs utilizing the enigma namespace, like enigma2 and TVheadend, VDR, etc.
• It cannot be used in the stream relay, because non of the tsid, onid, and enigma namespace are available.

Note 1

For channels with the same service id, the correct ECM key will be detected automatically, but each key needs a unique groupid. If you need different ECM keys for channels with the same service id, make sure they belong to different groups, like in the example:

Code

P 009E0234 01 11223344556677
P 00040234 01 22334455667788
P 013E0234 01 33445566778899

Duplicate keys (same groupid and same srvid) are not allowed. If there are any duplicates, only the last one in the SoftCam.Key file will be used. This also means that as new ECM keys are found and appended to the file, they will automatically replace earlier keys.

Note 2

In order the auto update feature to work, the ECM keys must be seeded. This is done by entering a dummy ECM key and a corresponding (i.e. with the same group id) EMM key, for example:

Code

P 00010004 00 00000000000000
P 00010004 01 00000000000000

P 0001 AABBCCDD 11223344556677

When you tune into the channel with the service id '0004', the auto update function will run. After a while, a new ECM key will be written at the bottom of the SoftCam.Key file. This new ECM key will be used instead of the dummy one when opening the channel. For each service id, a dummy ECM key has to be added. Each EMM key will update all ECM keys in the same group.

Note 3

Multiple EMM keys are allowed for each group, but there is a maximum number of 32 EMM keysthat will be used when auto updating. When the auto update function runs, the algorithm does not match the group id. This means that these 32 EMM keys are chosen among all groups that have an ECM key with the current channel's service id, and not necessarily from the 'correct' group. The effective number of EMM keys for auto updating is thus 32 per service id (channel). This design has two side effects:

• If there are many EMM keys for each group, there is a chance all 32 EMM keys are chosen from the 'wrong' group. Then the auto update function will never update the ECM keys.
• Since no group id is matched, there is a chance the newly found ECM keys to be written to the 'wrong' group.

For best results, it is recommended to have no more than 10 EMM keys in each group, especially if you have many groups in your SoftCam.Key file, and make sure there are no EMM keys with the same UA belonging to different groups.

When using the new method for matching ECM and EMM keys based on transponder, all considerations described above are gone. Only limitation is the maximum number of EMM keys that can be used per group are 32.

Configuring DVB-Api (on compatible devices)

Some receivers support PowerVu through direct DVB-Api decryption. If your device supports it, configure OSCam-Emu as follows:

1. Disable Stream Relay (on by default) through the WebIf:
   Code

    WebIf -> Config -> Stream Relay -> Mode 0 - disabled (use direct DVB-Api decryption)

   or by editing the oscam.conf file:

   Code

    [streamrelay] stream_relay_enabled = 0

2. Select the correct extended CW API:
   Code

    Webif -> Config -> DVB-Api -> API for extended CWs 1 - OE 2.2 2 - OE 2.0

   or by editing the oscam.conf file:

   Code

    [dvbapi] extended_cw_api = 1

Display More

That means only 32 EMM keys in total can be chosen?

Quote from jenseneverest

Quote

When using the new method for matching ECM and EMM keys based on transponder, all considerations described above are gone. Only limitation is the maximum number of EMM keys that can be used per group are 32.

so add more groups if required

So is 32 emm per group?

CONGRATS FOR THE WIN AGAINST BARCA. YOU'RE A HUGE CLUB. (I had to say that.. sorry)

This is how au works with the old method:

1. when you tune to a channel, emu gets the srvid.

2, Then it searches ALL groups that have an ecm key with the same srvid.

3. Then it gets the emm keys from the groups matched in 2. But not all. It starts adding emm keys until it reaches 32. Then it stops adding any more.

This can have some drawbacks as they are explained in note 3:

For example, lets suppose you want to run auto update for afn (9.0E). You tune to a channel from afn with srvid 68. This srvid also exists in the discovery group in 4.8E (I think). This means that the emm keys from these 2 groups (afn and discovery) will be added for au! If you have the discovery group above the afn in your softam.key, then the discovery emm keys will be added first. If they are for example 20 in total, then the final 12 positions will be filled with the emm keys from the afn group. So only the last 12 emm keys are the correct ones, and au has to find ecm keys only using these 12emm keys in practice. If you had 32 emm keys in your discovery group, then all emm keys would have been chosen from it. So, the au will not find any new ecm keys for afn.

The 2nd problem with the old design is that if the same emm key is present in 2 or more groups. the ecm keys in the wrong group could be updated. Take the previous example. If the same emm key is present in both the afn and the discovery groups, and an emm packet comes for this emm key, then the emu will not know which group's ecm keys to update. It will update the ecm keys in the first group it finds in softcam.key, which will be the discovery ones, the wrong ones.

These two problems can be avoided, if you have a smaller number of emm keys for each group in your softcam.key and if you make sure that the same emm key is not present in more than 1 group.

With the new method, these problems do not exist. We match the group from the start, so there is not margin for errors. And we can actually use all 32 emm keys for the correct group for au.

can you guys talk about unmasking mtn

Thanks mate for reply .Naulitus before told try then he disappeared

key are found ok with the new softcam but we get a black screen

johnkiema

The problem is this line:

"Mode CW: 1 (in use)"

We don't have a firmware which contains CW-Modes 1 & 2.

Western firmware's do not contain this one!

It is the working firmware from an official box that is required for disassembly.

Quote from jenseneverest

keys are now found in 10 seconds rather than 15 minutes:joythink::shake1:

how method with came and configfile ?

Quote from Accept157

johnkiema

The problem is this line:

"Mode CW: 1 (in use)"

We don't have a firmware which contains CW-Modes 1 & 2.

Western firmware's do not contain this one!

It is the working firmware from an official box that is required for disassembly.

Display More

Where can we get cw-modes 1&2

johnkiema

No way to get powervu cw-mode 1.

Quote from jenseneverest

keys are now found in 10 seconds rather than 15 minutes:joythink::shake1:

can u provide the files and step wise method

I still have the same issue, I change debug mode to 2 but I can see Channel hash I use a Vu+ solo 4k with OSCam 11.518-emu-r796. BTW y update to OSCam 11.518-emu-r796 but when I used as Cam 1 I cannot see web interface

Quote from Accept157

johnkiema

No way to get powervu cw-mode 1.

Hi bro I saw cw 2 fix is out

Quote from johnkiema

Quote from Accept157

johnkiema

No way to get powervu cw-mode 1.

Hi bro I saw cw 2 fix is out

Fix is out for what receiver?

Hi team

Does anybody know how avoid condition below

TP 3920 H 3000 sat 58w

I got 2 hashname F7F0E447 & 9F9D2482 and is for the same TP, Just one of them can do Autoroll

is nay way that both hashname run autorrol? both use same EMM

hello everyone,





im trying to make this work but cant figure out it



P 550009E0 00 000030FE921B7B ; UC ARG HD (U24)

P 550009E0 01 000030FE921BAE ; UC ARG HD (U24)



P 55000C70 00 000030FE921B7B ; OS Download S22

P 55000C70 01 000030FE921BAE ; OS Download S22



P 55000A20 00 000030FE921B7B ; Su ARG HD (SU26)

P 55000A20 01 000030FE921BAE ; SU ARG HD (SU26)



P 550009C0 00 000030FE921B7B ; SU CHILE HD (SU23)

P 550009C0 01 000030FE921BAE ; SU CHILE HD (SU23)



P 55000A00 00 000030FE921B7B ; UC CHILE HD (UC25)

P 55000A00 01 000030FE921BAE ; UC CHILE HD (UC25)



P 5500 004D8155 716C0D6B5905DB ; emm



same EMM KEY on dreamDVB on my pc is working great



and on my VU Solo se v2 is not working



55.5W - 3814-H-15000





this is what working on my dreamdvb



ECM: 80 30 3D 30 37 20 0E 00 00 00 00 10 A0 00 DE FF E2 A9 33 5F 2A 92 5C 33 CB 2E 00 56 00 09 E0 00 00 FD DE F6 3E B6 71 F8 C4 7C 3E C2 0F 98 16 F2 ED 70 12 36 08 F2 50 DE B7 92 CB A9 ED 07 73 5A

IsDecrypted: True

DVB Scrambling Algo: DES

Needs Unmasking: False

ECM Counter: $10

Nanos: [5]->($20, $36)

Nano $20 Extra Data Length: 0

Mode CW: 0, Unmask: 0

Hash Mode CW: 0, ECM: 0

Seed CW ECM: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

ECM CalculateSeed: 80 30 3D 30 37 20 0E 00 00 00 00 10 A0 00 0E 2A 55 22 7A A0 AC 47 FD 35 E6 9A 9A AC 00 09 E0 00 00 18 00 5F 93 B8 01 01 D9 BD 3F 06 92 02 02 20 82 30 00 00 00 52 00 00 00 55 09 E0 ED 07 73 5A

Base Cw: AC 47 FD 35 E6 9A 9A

Seed VPid: 43 5F D7 B4 ED 28 00 00

Seed APid-1: 89 37 E9 59 56 51 00 00

Seed APid-2: 89 37 E9 59 56 51 00 00

Seed APid-3: 53 E0 9D 57 55 C8 00 00

Seed APid-4: 53 E0 9D 57 55 C8 00 00

Seed HSD: 43 37 14 A1 28 47 00 00

S-Box Type: Primary Tables

Xor Mode: Normal mode[0]

Ident: $9E0

KeyIdx: 0

Key: 67 F9 6F 3E 33 5C 35

OddCwAudio1: 16 97 15 58 2A CB 67 4C

EvenCwAudio1: 25 B9 04 97 CD 8A CD 26

OddCwAudio2: 16 97 15 58 2A CB 67 4C

EvenCwAudio2: 25 B9 04 97 CD 8A CD 26

OddCwAudio3: 85 67 C1 EA 15 D0 31 6B

EvenCwAudio3: FE D3 D9 0D 61 31 1F 92

OddCwAudio4: 85 67 C1 EA 15 D0 31 6B

EvenCwAudio4: FE D3 D9 0D 61 31 1F 92

OddCwVideo: E0 19 C7 4A E9 46 F2 25

EvenCwVideo: EF 8C 0B 51 1A 2F 15 9B

OddCwHSD: 1F B3 34 57 86 BC AD B5

EvenCwHSD: EF B9 3B 32 4A 2C B6 1C





i have here the image

i did read alot but having hard time to make work on this new method have be around for coulpe years on PV world but this one im lost.

please HELP.

thank you very much
















please help