LABERTHREAD zum Thema: Umstellung der SAT-Verschlüsselung bei Sky (Geschlossen)

Micha_123 schrieb:

Ich behaupte mal das der Schritt beim ci+ garnicht gegeben ist.

CI+

N Y0001 Y0002 (nach 38C1 emms)

N N N (jungfräulich)


receiver


Y 5031 Y0001 Y0002

Jungfreulich
Y5031 N N


klingelts?

Zum Vergrößern anklicken....

This function allocates specified number of CA key slots for each key slot type.

Description:

There is a piece of hardware storage allocated for CA key slots. The key slot table has 1530
(Refer to BCMD_XPTSECKEYTABLE_TOP) entries, where each entry has 64 bits. The
total size could be varied from chip to chip.

There are 5 types of key slot being defined. Each key slot in different key slot type consists
of different number of entries as follow:
Key slot type 0 always has 10 entries.
Key slot type 1 always has 12 entries.
Key slot type 2 always has 14 entries.
Key slot type 3 always has 16 entries.
Key slot type 4 always has 16 entries.

This function requests BSP to initialize the specified number of key slots for each key slot type.
the number of key slots can be set to zero if the slot type is not used. As long as the combination of
all the key slots of for each key slot type does not exceed the maximum key slot table capacity,
BSP will return succesfully. No CA key slot can be accessed until this function is called and
returns successfully.

This function also keeps track of the allocation information, which can be used to check if a specific
key slot has been associated with certain pid channel.

Note that this function shall be called only once after system bootup. BSP shall return error if
calling this function more than once. However, the key slot allocation in BSP, resulted from the first
successful function call, remains intact until the chip is reset. For debugging purpose, the
caller can call this function mutiple time, provided the same allocation is specified each time.
Calling this function multiple times with different allocation values shall have an undetermined
consequence.

Zum Vergrößern anklicken....

This function can be used to load the key to the BSP Key RAM and use the key in RSA, DSA,
DH and other cryptographic operation. The function can also load the key to the BSP Key
RAM and then route the key to different CA and CP destination. However, depend on
the access control matrix and OTP progamming, loading control word to certain destination
may be blocked.

The length of selected BSP Key RAM buffer is either 192bits or 2048bits, each with three
allocated buffers. 192-bit buffer is typically used to store keys, with the size of 64/128/192
bits, and is normally used for CA, M2M, HDMI, IV and REMUX modules. 2048-bit buffer
is used to store keys with the size of 1024/2048 bits, and is normally used for
RSA, DSA, or DH operations.

Key slot of certain destination, for example CA, may contain a few keys, such as odd, even and IV
key. This function can load only one key at a time. If the same key slot entry is
loaded multiple times, the last call may overwrite any previous loading.

The loaded key will be kept valid in the key slot until either the key slot is invalidated by
BHSM_InvalidateKey function or the chip is reset. The loaded algorithm and control bits will be
kept in the key slot until either the key slot is reset by BHSM_ResetKeySlotCtrlBits or the
chip is reset.

The key order shall be in big endian. If the actual key bytes to load is shorter than
192 bits or 2048 bits, they will be loaded at at the most significant byte of the aucKeyData
variable. For example 64-bit DES key is occupying first 8 bytes of aucKeyData variable.

Refer to Load key documentation on how to load 3DES-ABA and 3DES-ABC keys.

Note that some systems may require to decrypt the encrypted key for CA and CP.
BHSM_GenerateRouteKey can be used for this purpose.

Zum Vergrößern anklicken....