hi for oscam Soon we reach the goal

There are 13 replies in this Thread which was already clicked 6,558 times. The last Post () by Cyberscitymaste.

  • You probably didn't notice that the DCW for nano 01 is different than it should be. the 4th, 8th, 12th and 16th bytes are the control sums. Take a look:



    TF1 HD




    81 00 61 33 11 00 07 5C 00 06 35 A6 61 AD 1E 23


    1B EB 37 37 C7 D8 07 58 54 E5 1D 8B 38 DA 14 59


    54 B1 F1 8D D2 00 40 C7 1A 21 C6 F3 5F 25 89 C5


    09 08 86 8D 2E A8 96 F2 E8 8F 84 BA 97 24 8F 19


    B0 DE A6 0F B2 5C D5 83 61 5D 61 6D 41 73 DD BC


    1B BF F6 F4 0E 92 F6 19 D7 CB EA E7 CC C5 32 81


    7D 91 16 A8




    dcw E6 22 33 3B F0 48 69 A1 42 4B AE 3B F8 2B 97 BA




    E6 + 22 + 33 gives 13B, so the fourth byte is 3B
    E6 + 22 + 33 donne 13B, So the byte is 4è 3B


    F0 + 48 + 69 gives 1A1 so the eighth byte is A1
    F0 + 48 + 69 donne 1A1 So the byte is 8èmt A1


    42 + 4B + AE gives 13B so the twelvth byte is 3B
    42 + 4B + AE donne 13BSo the byte is 12èmt 3B


    F8 + 2B + 97 gives 1BA so the sixteenth byte is BA
    F8 + 2B + 97 donne 1BA sdonc leSo the byte is 4é BA


    Now, take a look at nano 01 which is on the HD channels.



    80 00 61 33 11 01 07 5C 00 AC A8 D6 08 2D DD 47


    07 73 53 1F 2D EA 76 CD 64 47 BC 5A 37 B3 50 5E


    C6 74 27 54 F4 C0 17 8D 80 F2 36 ED B8 45 3A 3F


    06 E5 1A 94 A8 9D 7B 88 E1 EE 07 C8 97 3D DD 99


    AE EB 20 6B FD 3B 8E 85 15 0A E5 65 A2 8F E1 05


    3C 1A 69 FD 41 0F 59 48 95 C4 25 C3 AA 87 F8 67




    dcw D8 08 F4 8C B4 CF FB 3A 38 19 ED 56 E5 1B 4C B1




    D8 + 08 + F4 gives 1D4 instead of 8C
    B4 + CF + FB gives 27E instead of 3A
    38 + 19 + ED gives 13E instead of 56
    E5 + 1B + 4C gives 14C instead of B1


    I think we need to focus on that why the control sum is calculated wrongly. Gentlemen, is there anyone who could log these ECMs on original boxes and put here the communication logs? E.g. you can use the Season/logger interface. Then we would have to check how the same ECMs are being decoded in Oscam or other softcam, e.g. newcs


    The solution might be to implement a better calculation of these control sums for nano 01.Vous pouvez utilisez un season logger.


    My colleague pointed out that Oscam has got automatic control sum correction



    Code source


    for (i=0; i<16; i+=4)
    {
    c=((er->cw[i]+er->cw[i+1]+er->cw[i+2]) & 0xff);
    if (er->cw[i+3]!=c)
    {
    cs_debug_mask(D_TRACE, "notice: changed dcw checksum byte cw[%i] from %02x to %02x", i+3, er->cw[i+3],c);
    er->cw[i+3]=c;
    }
    }



    You can quickly test it by disabling this option and if it does not help, then you have to test the ECMs in original boxes versus the softcams.
    Probably there is some sort of pairing in Seca and you'll have to dump the firmware of these boxes. Please check it out whether the original boxes have some glue on onboard chipsets. If not, then you should start organizing some dumps


    Below you can find a dump of Polish Seca HD cam that was officially sold by the provider. According to my colleague, it may already have some pairing instructions which could have been used in your case. Maybe you have some debugging knowledge and you'll find out something interesting.


    2shared - download hd_cam.zip



    This course information and as each member is solely responsible for what he does with the information held on this forum.

  • this is my first map that n as not been updated in the deco off


    >type: SECA, caid: 0100, serial: xxxxxxxxxxxx, card: Canal+ NL v10.0
    [seca-reader] provider: 1, valid: 1, name: ADMIN, expiry date: 2011/12/29
    [seca-reader] SA: YYYYYYYY
    [seca-reader] provider: 2, valid: 1, name: CANALSAT, expiry date: 2011/09/22
    [seca-reader] SA: YYYYYYYY
    [seca-reader] provider: 3, valid: 1, name: CANAL+, expiry date: 2011/09/22
    [seca-reader] SA:YYYYYYYY
    [seca-reader] provider: 4, valid: 0, name: CANALPRO, expiry date: 1992/01/01
    [seca-reader] provider: 5, valid: 0, name: CSAT 1, expiry date: 1992/01/01
    [seca-reader] provider: 6, valid: 0, name: CSAT 2, expiry date: 1992/01/01
    providers: 6 (3341,3311,3315,3317,331B,331D)
    [seca-reader] no PBM for provider 1
    [seca-reader] PBM for provider 2: B010818DB5BE20FE
    [seca-reader] PBM for provider 3: 8000000000000044
    [seca-reader] PBM for provider 4: 8000000000000000
    [seca-reader] PBM for provider 5: 8000000000000000
    [seca-reader] PBM for provider 6: 8000000000000000


    this is my second card as it was updated in the deco off


    >type: SECA, caid: 0100, serial: xxxxxxxxxx, card: Canal+ NL v10.0
    [seca-reader] provider: 1, valid: 1, name: ADMIN, expiry date: 2011/12/24
    [seca-reader] SA: YYYYYYYY
    [seca-reader] provider: 2, valid: 1, name: CANALSAT, expiry date: 2011/09/23
    [seca-reader] SA: YYYYYYYY
    [seca-reader] provider: 3, valid: 1, name: CANAL+, expiry date: 2011/09/22
    [seca-reader] SA: YYYYYYYY
    [seca-reader] provider: 4, valid: 0, name: CANALPRO, expiry date: 1992/01/01
    [seca-reader] provider: 5, valid: 0, name: CSAT 1, expiry date: 1992/01/01
    [seca-reader] provider: 6, valid: 0, name: CSAT 2, expiry date: 1992/01/01
    providers: 6 (3341,3311,3315,3317,331B,331D)
    [seca-reader] no PBM for provider 1
    [seca-reader] PBM for provider 2: B010818585BE20FE
    [seca-reader] PBM for provider 3: 8000000000000044
    [seca-reader] PBM for provider 4: 8000000000000000
    [seca-reader] PBM for provider 5: 8000000000000000
    [seca-reader] PBM for provider 6: 8000000000000000


    I notice a difference in SA of a provider and two 2 and 3 of which have been updated.


    have fun

  • Several point: the decor deals with an additional algo an algorithm symmetric.
    The CRC is bad becaufe the DW is bad, do not recalculate and correct the DW to be good.
    The dump module SECA HD will not help in my opinion, because the card does not work in this module, and enabled by pairing Cyfra Poland is different.


    There is only one solution, dump the decoder to have the dump Flash & RAM (SDRAM), flat all the latest generation decoders are protected for the Jtag level of the probe.
    Unless an old HD receiver without this protection exists and allows the dump Flash and RAM.


    The DW = are consecutive then the algorithm is symmetric of 8 bytes, it is not much of algorithms.


    DES or 3DES ......


    Place your bets, you need to do is find the key :47_002:

  • here's what I get it when I put on Canal + HD (black screen) and conect to the server, tomorrow j have both the machine you will live, I would TF1 HD canalsat (we also get a black screen) and TF1HD TNTSAT has the same hours and then go on TF1 and TF1 canalsat SD with SD TNTSAT.


    here are the cw channel + black screen therefore nano


    # OSCam cardserver v1.10rc-svn - OSCam
    # control word log file for use with tsdec offline decrypter
    # DATE 2011-08-02, TIME 22:20:09, TZ CEST
    # CAID 0x0100, SID 0x2275, SERVICE "0100:2275_unknown"
    1 52 B3 33 38 96 71 77 7E # 22:20:09
    0 B9 C8 06 87 C2 0F DF B0 # 22:20:20
    1 64 98 7F 7B A0 B5 9D F2 # 22:20:30
    0 D3 78 E8 33 71 78 BB A4 # 22:20:40
    1 2C E9 4E 63 4A 5F 7F 28 # 22:20:50
    0 88 82 78 82 D7 79 08 58 # 22:20:59
    1 A6 3F FF E4 6D 4E 9F 5A # 22:21:09
    0 0D 3F 7B C7 1E 7E 59 F5 # 22:21:19
    1 F3 D8 E6 B1 0D 05 46 58 # 22:21:29
    0 62 4C AD 5B AB 7E 95 BE # 22:21:38
    1 B4 19 E2 AF A7 72 08 21 # 22:21:47
    0 E3 CA 4C F9 EB D3 9C 5A # 22:21:57
    1 FB E1 EB C7 1B 51 E8 54 # 22:22:07
    0 A2 A3 E4 29 05 7E C1 44 # 22:22:17
    1 5D EE B6 01 26 B8 18 F6 # 22:22:27
    0 43 1B 23 81 EB 66 F8 49 # 22:22:37
    1 EA 26 91 A1 B4 E3 B3 4A # 22:22:47
    0 CD 6C EC 25 44 26 74 DE # 22:22:57
    1 DA E2 C4 80 6D 4F 92 4E # 22:23:07
    0 72 ED B3 12 C8 C6 8E 1C # 22:23:17
    1 67 52 2F E8 A5 1F 48 0C # 22:23:27
    0 C3 BB A8 26 83 85 22 2A # 22:23:37
    1 8B DF 01 6B C8 C2 5B E5 # 22:23:47
    0 59 44 56 F3 92 BC 50 9E # 22:23:58
    1 E4 08 1D 09 05 77 4D C9 # 22:24:08
    0 49 AC BC B1 3B 7A A3 58 # 22:24:18
    1 60 14 9F 13 08 9F B9 60 # 22:24:28
    0 5D 0B 01 69 67 BF 5D 83 # 22:24:38
    1 A3 9B 4D 8B 6B 86 93 84 # 22:24:48
    0 4C BA 79 7F A6 4E B4 A8 # 22:24:57
    1 69 AA B1 C4 9F DF 65 E3 # 22:25:07
    0 78 0A 2C AE BE A7 E3 48 # 22:25:17
    1 C3 91 8D E1 06 29 C7 F6 # 22:25:27
    0 5A D2 02 2E 8D 20 3A E7 # 22:25:37
    1 CA 5B 18 3D B8 A5 D1 2E # 22:25:48
    0 9D CA 34 9B 99 75 74 82 # 22:25:57
    1 F2 08 6D 67 31 ED A3 C1 # 22:26:07
    0 16 E3 00 F9 15 FF 88 9C # 22:26:19
    1 9A 86 CC EC FA D1 A8 73 # 22:26:28
    0 B4 D2 23 A9 54 B0 81 85 # 22:26:38
    1 10 1F 37 66 05 2D 80 B2 # 22:26:49
    0 49 60 D5 7E E9 50 9F D8 # 22:26:58
    1 4F 87 99 6F E4 CC E3 93 # 22:27:09
    0 7B 6C 6D 54 55 CF 25 49 # 22:27:20
    1 7F 6C 5A 45 A1 FA 73 0E # 22:27:29
    0 94 8F 0E 31 BB CF 0F 99 # 22:27:39
    1 48 DB 11 34 3A 5F 57 F0 # 22:27:50



    for PC made on TF1 HD does not work.
    And again calculating the checksum is correct on these frames:


    0 94 8F 0E 31 BB CF 0F 99 # 22:27:39
    1 48 DB 11 34 3A 5F 57 F0 # 22:27:50


    94+8F+0E=131 BB+CF+0F=199
    48+DB+11=134 3A+5F+57=F0


    This therefore shows that not all of the resulting frame is only surencryptée each group of 3 bytes.


    have fun

  • Guys,


    If you want to make some comparisons, you have to check deeper into oscam logs! These CW values are probably already corrected by automatic functionality within oscam. That's why the checksums may be correct. Try to make a 30 minute log from TF1 HD from 018 card (seca with nano 01) and at the same time try to log the same logs from viaccess card. Please be aware that the debug should be enough to see the postprocessing of the control sum by oscam. You can practise that with debug level 255


    Use at least 2-3 seca cards and 2 viaccess cards at the same time and then we can make the comparison. If this channel is in simulcrypt, then the CW will have to be the same in order to decode it. Obviously, the one from viaccess will be the correct one assuming that there is no postprocessing (e.g. by using some AES keys) of the DW by receiver.

  • Re all I see that no one intereeser by my research so I will not post more then me everything is ok seca hd cards 018 thank you to you for accepting me on this forum soon.


    Best Regards

  • ciao bip su nds it si può implementare la season loggen con oscam vi ringrazio


    google translated:


    hello bip nds it can be implemented on the season loggen with oscam thank you

  • argo1


    use English language in future or we will have to delete the posts


    google translated:


    usare la lingua inglese in futuro o dovremo eliminare i messaggi

    If I take a while to respond, you can see why.....


    :red:

  • That doesn't surprise me that the Kyng team have figured it out. Never had an issue with TNTSat with my old Cristor Atlas. I'm actually regretting selling it now. Had TNTSat and Fransat cards in it, and both worked perfectly.


    Has anyone got any experience here with the Cristor Atlas HD box. My old one was the Cristor Atlas-E box which wasn't the best but it decoded the cards perfectly :haha:


    When TNTSat changed the AESKey it was normally in their firmware within a few days working again.


    Nano

  • hi with cristor atlas hd alls chanels ok tnt sat and somes mores fr chanels open with emulador

  • 2015/01/21 21:26:49 910CDD8 r Relince [seca] Received an encrypted controlword from the card that needs postprocessing by the receiver!
    2015/01/21 21:26:49 910CDD8 r Relince [seca] WARNING: Encrypted controlwords detected-> disabling controlword crc checking!

  • master G

    Set the Label from TnTSat OSCam to Viaccess Cards OSCam

OSCam Support Forum

Configs, discussion, downloads and guides for OSCam Softcam.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!