that is the channel number / service id.
you can open the ts file with tsreader or transedit, and it will show you the service ids.
Every time I open ts reader it looks for a satellitecard :-(
that is the channel number / service id.
you can open the ts file with tsreader or transedit, and it will show you the service ids.
Every time I open ts reader it looks for a satellitecard :-(
If that's a new recording,should not have an 0x83 emm in it.40.5 West
record
http://s5.dosya.tc/server2/cdcfnu/40.5W_3923_V_7000.rar.html
for thanks record otokoc :thum:
Director = Tandberg yes
I don't think so... I captured some Director channels and conditional access is detected as GENERAL INSTRUMENTS, instead of that, those channels with RAS are detected as Tandberg.
It would be nice to start a discussion about Director (GI) isn't it? What I saw is that there is no EMM stream, only ECM and Video/Audio.... perhaps someone has a dump of a receiver to take a look?
poc 1.6
+ now printing active entitlement
+ now supporting raw emm logs (usage: poc emm.bin)
+ now caching unhandled E1 tags until ram keys are received
+ added more permission types
usage:
poc <raw emm stream file>
poc <ts input file> <srvid> <ts output file>
_https://mega.nz/#!UI5lWKhR!o5MGuxtx_ERc3UmMWLladhl5u6DtIHaMvBhDZZoVApE
Is this a bad decrypt?
maybe errors in the TS file? (weak signal)
I don't think so... I captured some Director channels and conditional access is detected as GENERAL INSTRUMENTS, instead of that, those channels with RAS are detected as Tandberg.
It would be nice to start a discussion about Director (GI) isn't it? What I saw is that there is no EMM stream, only ECM and Video/Audio.... perhaps someone has a dump of a receiver to take a look?
Here are some Crypt8 for t@ndberg channels that dont send ECM-keys.
If someone could find the plain CWs, maybe we could brute the ECM-key.
Code:SEE TEXT File attachment
Here are some Crypt8 for t@ndberg channels that dont send ECM-keys.
If someone could find the plain CWs, maybe we could brute the ECM-key.
Code:SEE TEXT File attachment
poc 1.6
+ now printing active entitlement
+ now supporting raw emm logs (usage: poc emm.bin)
usage:
poc <raw emm stream file>
poc <ts input file> <srvid> <ts output file>
vPlug...
poc 1.6
raw EMM mode
[Emu] got EMM nano tag E0 (EMM_TAG_RECEIVER_ALLOCATION_DESCRIPTOR) for the first time
[Emu] got EMM nano tag E4 (EMM_TAG_SECURITY_TABLE_DESCRIPTOR) for the first time
[Emu] Keys found in EMM: new nano E4 ram keys 30 to 3F
[Emu] Keys found in EMM: new nano E4 ram keys 0 to F
[Emu] Keys found in EMM: new nano E4 ram keys 10 to 1F
[Emu] Keys found in EMM: new nano E4 ram keys 20 to 2F