Since Version 1.2.0.0, Yankse supports Seca2 viewing with the following limitations:
at the moment, only providers 0070, 0071 & 0072 (Sky Italia, Calcio) and 0064 (D+ Spain)
are working, others may follow in the future (I hope).

Update (12-04-2004):
- many/nearly all channels on Sky IT are now using unknown hash table 9X -> no decryption
- some channels on Digital+ (Taquilla at least) are starting also to use 9X -> no decryption

You need a few additional files for enabling S2 in Yankse:
for each provider (70,71,72 are considered as one here)
- the so-called Seca Hash Tables T1 and T2, for each 9x, Bx or Fx selection
  Bx is for instance the key select in use at the moment (BC).
  Each Table is 256 bytes long

  You must follow a strict order: you have two options:
  Table T1 for Bx, then Table T2 for Bx (total: 512 bytes)

  OR

  Table T1 for 9x, 
  Table T1 for Bx,
  Table T1 for FX,
  Table T2 for 9x, 
  Table T2 for Bx,
  Table T2 for FX  (total: 1536 bytes)
  
  If you don't have values for a table, replace it with 256x 00.

  Other kind will be rejected.

Rmk: the table 9x for 70,71 and 72 is not known !

- the so-called mask table MT (or chainmask) 
  it'a file of 16384 bytes.

***
New since 1.22.1, it can also be the complete masktable 
(8192+7 bytes of odd index, then 8192+7 bytes of even index).
Only useful for Sky Italia.
For Digital+, table of length 16384 is expected, and wraps around 0.
***

Then you need a configuration file for seca2 providers
for yankse it MUST be called seca2.cfg and be located in the same directory as
the DLL.

The format of the file is decribed hereafter (it's like a Windows INI file)

The RSA keys are in the form: <modulo> <exponent> [R]
modulo: 90 bytes long (=180 hex digits) value of the RSA key's modulo
exponent: 6 bytes long (=12 hex digits) value of the RSA key's exponent
R: optional field, if R (or r) means that the values must be reversed (last<->first byte)


Seca2.cfg
---------

[seca2_IDID]	; IDID is like 0070
MT=<relative path to Mask Table file>
HashTables=<relative path to Hash tables file>
ECM_1= RSA key for ECM 1 (10.01)
ECM_3= RSA key for ECM 1 (10.03)
ECM_5= RSA key for ECM 1 (10.05)
EMM_1= RSA key for EMM 1 (10.01)
EMM_3= RSA key for EMM 1 (10.03)
EMM_5= RSA key for EMM 1 (10.05)
SHA=<pad>,<end>	; padding and 'end' value (one byte each) for the SHA Signature algorithm				

MT and HashTables are mandatory and must point to valid files.
At this moment, only ECM_1 is needed.
EMM keys are not used in Yankse.

See seca2.cfg.example

-----
In Softcam.key, you could put keys for providers (only 0070, 71 and 72 works now)

S 0070 0C ...
S 0070 0D ...
S 0070 0E ...

S 0071 0C ...
S 0071 0D ...
S 0071 0E ...

S 0072 0C ...
S 0072 0D ...
S 0072 0E ...

--
V/ 12-apr-2004