Irdeto ACS v5.0 - Page 2

007.4 · #11 (**permalink**) 10-16-2005

Hi mrtoolate

That makes a lot more sense. Certainly a completey new flavour of Irdeto. Interesting to see that they are still using the original encrypted E2/E3 cardfile data!
Thanks for the clarification.

007.4

mrtoolate · #12 (**permalink**) 10-17-2005

this card just for one DVB-T provider from italy
but i have acs5.0 from middle east same as 4.1 exactlly

also E0/E1 cardfile data! same

Geremia · #13 (**permalink**) 10-25-2005

Just for your interest, here is the relationship between those new cam->card commands and standard irdeto commands:

Class 01 02 for example is replaced with D2, 01 05 with D5, 01 00 with D0 ....

Standard irdeto INS value is multiplied by 2, so for example request provider id 00 is 01 02 03 ....and becomes -> D2 06

R1 and R2 are the same

Lenght in standard irdeto is considered without checksum, here is considered with.

Checksum for both commands are the same, in this new commandset it's like the card translate the command to standard irdeto prior to get the data and checksum bytes.

example:

Request provider id 00

01 02 03 03 00 00 [3C] -> D2 06 03 00 01 [3C]

well, there are also ACKs from the card (protocol T=0), and another command to have final answer from the card
here in detail:

TX-> D2 06 03 00 01
RX-> 06 <-ack
TX-> [3C]
RX-> 60 90 21 <- 60 90 means "ok" and 21 means "21 bytes for you to read"
TX-> D2 FE 03 00 21 <-D2 and 03 00 equal to the first command, FE always FE, 21 is the bytes requested to read
RX-> FE <- ack
RX-> 01 02 00 00 03 03 00 18
00 06 63 5A 00 00 00 00 00 00 01 37 01 01 2D 2D 2D 82 62 00 00 00 00 00 [E0] 90 00 <- here the standard irdeto reply included checksum and 90 00 "command executed correctly by the card"