i don't know your box type, but my 04k is much simpler (see attached), after 11521 update.d624a6046e1835c06b8.png

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

....but it takes twice the time to find the keys, vs old method. So, what is the advantage of cleaner key file over longer time ?

Quote from tonispa

Hello

I have only this file libcrypto.so.0.9.7

it's possible emu oscam-svn11517-mipsel_OE2.0-webif-oscam-emu-795.zip can running ?

tks for your answer

Display More

you should add this one:

libcrypto.so.0.9.8.zip

You may have to install in usr/lib this file & change attribute to 755:

libcrypto.so.0.9.8.zip

I'm using oscam-svn11517-sh_4-webif-emu-r795 (can be found here) , in my amiko 8900 (sti 7111) with

openpli taaapat, and is working fine.

new oscam-emu

New bin:

thx, but i'm not a member...

Doesn't work for zero4k.

I'm back to 11495

anyone else having issues with 11501 ?

Quote from odem2014

Mr please help me to know the difference between these two files ?

oscam-svn11503-sh4-webif-oscam-emu-patched

oscam-svn11503-sh4-webif-dvbapi-libusb-upx

And which one is the best with st7111 like Truman premier one plus ?

they are 2 different files:

.....-SH-4-....

and ....-SH_4-..... this is the one for st7111.

Quote from ashiqnaveed

Quote from ahmed gazye

OSCam svn11.490- Emu -r786 as at 29/1/2019

Oscam svn11.490Emu -r786 -Build

Thanks to audi06_19

Thanks toDreamOSat

oscam-svn11490-sh_4-webif-oscam-emu-patched.tar.gz

oscam-svn11490-sh4-webif-oscam-emu-patched.tar.gz

Good luck

Display More

dear alway two files dont understand why

Display More

one is for SH_4 boxes

the other is for SH-4 boxes!

latest version:

oscam-11479-mipsoe20-emu.zip

oscam-11479-openpli40-emu.zip

same here on vu+zero4.

last good working version is 11462r785.

since then, all new flood of versions are fake.eb736f5027a952f6.jpg

4912f06364.jpg

same here on vu zero. last working oscam is 11461?!?

new file is here:

oscam-svn11460-sh_4-webif-oscam-emu-patched.tar.gz

Since oscam-emu R780 version,

[reader]

label = AFN

is not necessary any more.

attached is my latest oscam.reader, working on dm & vu+.

Quote from tpmm

Hi - thx for the reply. I have been reading that for a while but I think what I need is a working oscam.server config with the correct reader section[s] to get oscam-emu to read the key files

the attached works on my dm+openpli

Quote from supwiddiss

Quote from master G

Quote from supwiddiss

Can anyone direct me to the one that will work?
And where will the configs be after I do get it running?

Both questions depend on which image is used.

Ahh. Currently using oscam 11438 with a bin file size of 1,984,400Kb.
oscam-1.20_svn-r11438.
Files in /etc/tuxbox/config.
Ideas?

you must use oscam 11439R777 witch fixed the hash mode 20 & 21.

do you have an oscam.services file in the same directory as oscam.server file ?

see attachment

ok, it did cleared all same id channels.

had to wait a little longer.

thx again.