Re: Oscam Plugins & Sky de
Posted: Mon Feb 14, 2022 9:14 pm
I suppose the checksum of the "crypted word", the key itself, that goes to ProgDVB from plugin to descramble the encoding.
here's what it looks like from plugin side:
00:20:02.750: Ch: 126 - 2X2
00:20:02.750: PMT: 007E(126), SID: 0722(1826)
00:20:02.846: ***** PMT found... [007E] *****
00:20:02.846: ***** ADD ECM [101E][0500/00040610] *****
00:20:03.301: ***** CAT found... [0001] *****
00:20:03.311: newcamd 0: ECM [101E][0500/00040610/0B01] found (324)
00:20:03.312: 0 O: :5FEA0CB383179103
00:20:03.313: 0 E: 0EE5A4717C60A82F:
00:20:06.894: newcamd 0: ECM [101E][0500/00040610/0B01] found (325)
00:20:06.895: 0 O: :E4F7DF23CCEE7689
00:20:16.899: newcamd 0: ECM [101E][0500/00040610/0B01] found (324)
00:20:16.900: 0 E: B57708C8A99A1BCB:
00:20:26.908: newcamd 0: ECM [101E][0500/00040610/0B01] found (325)
00:20:26.909: 0 O: :3F0B6B8B79D5ABF0
00:20:36.924: newcamd 0: ECM [101E][0500/00040610/0B01] found (327)
00:20:36.925: 0 E: 2E3AF8CDBB1B179A:
00:20:46.976: newcamd 0: ECM [101E][0500/00040610/0B01] found (325)
00:20:46.977: 0 O: :64A914D7DF8E129C
00:20:56.990: newcamd 0: ECM [101E][0500/00040610/0B01] found (324)
00:20:56.991: 0 E: 81C2E43149ACEE0D:
00:21:07.012: newcamd 0: ECM [101E][0500/00040610/0B01] found (324)
00:21:07.013: 0 O: :2447E29931718A83
00:21:17.090: newcamd 0: ECM [101E][0500/00040610/0B01] found (324)
00:21:17.090: 0 E: CF35A0B825AFBA91:
00:21:27.096: newcamd 0: ECM [101E][0500/00040610/0B01] found (324)
00:21:27.096: 0 O: :840A65B714567744
even/odd CW's are received by ProgDVB from plugin evety 10 seconds.
may there be any additional procedure that checks the CW inside ProgDVB engine before sending it to descrambler?
it is not a bad idea to do such a testing so that no junk goes to descrambler, but since the guys at Viaccess decided to disable it - that is not a straight rule any more, I think.
maybe there's a way that we can troubleshoot this behaviour by compiling a test-version that will log down everything that is being received from plugin and what comes to descrambler at the final step? it may be helpful, at last.
here's what it looks like from plugin side:
00:20:02.750: Ch: 126 - 2X2
00:20:02.750: PMT: 007E(126), SID: 0722(1826)
00:20:02.846: ***** PMT found... [007E] *****
00:20:02.846: ***** ADD ECM [101E][0500/00040610] *****
00:20:03.301: ***** CAT found... [0001] *****
00:20:03.311: newcamd 0: ECM [101E][0500/00040610/0B01] found (324)
00:20:03.312: 0 O: :5FEA0CB383179103
00:20:03.313: 0 E: 0EE5A4717C60A82F:
00:20:06.894: newcamd 0: ECM [101E][0500/00040610/0B01] found (325)
00:20:06.895: 0 O: :E4F7DF23CCEE7689
00:20:16.899: newcamd 0: ECM [101E][0500/00040610/0B01] found (324)
00:20:16.900: 0 E: B57708C8A99A1BCB:
00:20:26.908: newcamd 0: ECM [101E][0500/00040610/0B01] found (325)
00:20:26.909: 0 O: :3F0B6B8B79D5ABF0
00:20:36.924: newcamd 0: ECM [101E][0500/00040610/0B01] found (327)
00:20:36.925: 0 E: 2E3AF8CDBB1B179A:
00:20:46.976: newcamd 0: ECM [101E][0500/00040610/0B01] found (325)
00:20:46.977: 0 O: :64A914D7DF8E129C
00:20:56.990: newcamd 0: ECM [101E][0500/00040610/0B01] found (324)
00:20:56.991: 0 E: 81C2E43149ACEE0D:
00:21:07.012: newcamd 0: ECM [101E][0500/00040610/0B01] found (324)
00:21:07.013: 0 O: :2447E29931718A83
00:21:17.090: newcamd 0: ECM [101E][0500/00040610/0B01] found (324)
00:21:17.090: 0 E: CF35A0B825AFBA91:
00:21:27.096: newcamd 0: ECM [101E][0500/00040610/0B01] found (324)
00:21:27.096: 0 O: :840A65B714567744
even/odd CW's are received by ProgDVB from plugin evety 10 seconds.
may there be any additional procedure that checks the CW inside ProgDVB engine before sending it to descrambler?
it is not a bad idea to do such a testing so that no junk goes to descrambler, but since the guys at Viaccess decided to disable it - that is not a straight rule any more, I think.
maybe there's a way that we can troubleshoot this behaviour by compiling a test-version that will log down everything that is being received from plugin and what comes to descrambler at the final step? it may be helpful, at last.