How to find Crypt8 like ENC-1

bh62549

Registered
Messages
657
Asia 5, 3925H7200 signal ID is ENC-1. I recorded TS file for 10 minutes, but I still can't find Crypt8. I don't know how to find Crypt8 and calculate CW with the ID of ENC-1, ENC-3 and service-1.

Crypt8 did not find the video

Time for searching Crypt8 = 4 sec.
Search Crypt8 in TS Start
TS file: D:\biss key\TS\100.5E_3925.147_H_7200_(2019-08-03 16.59.45)_dump.ts
Using all PIDs
Using file limit: 4096 MByte
File length: 1194 MByte
UsingFileLen: 1252096920 bytes
Reading file ...
Searching ...
Using payload size: 184
PID: 21h B8h-Crypt8:32 A0 43 DE 13 ED DF BF [E] Count:24
PID: 21h B8h-Crypt8:78 97 B7 43 CC 73 FB E5 [E] Count:24
PID: 21h B8h-Crypt8:BA 39 26 A3 70 BC D9 F3 [E] Count:24
PID: 21h B8h-Crypt8:DE E1 07 75 AB B4 35 13 [E] Count:24
PID: 21h B8h-Crypt8:E6 3B D9 2C 46 12 90 E8 [E] Count:22
PID: 21h B8h-Crypt8:CC 8C 07 7D 04 63 EA 9F [E] Count:21
PID: 21h B8h-Crypt8:37 73 89 27 21 15 59 BC [E] Count:17
PID: 21h B8h-Crypt8:1A 2E EB DA 0E 2A A2 EB [E] Count:16
...

PID: 22h B8h-Crypt8:27 96 F4 2D ED 75 F2 54 [E] Count:75
PID: 22h B8h-Crypt8:2D 8B A2 AF B5 A8 A3 18 [E] Count:75
PID: 22h B8h-Crypt8:9F 72 23 53 B8 EC 9D E0 [E] Count:75
PID: 22h B8h-Crypt8:B3 57 87 0B EA 68 6A C6 [E] Count:75
PID: 22h B8h-Crypt8:D7 89 25 5D 1F EE 07 81 [E] Count:75
PID: 22h B8h-Crypt8:F8 A6 F4 2B E1 BA 4E 7B [E] Count:75
PID: 22h B8h-Crypt8:2A A3 35 4F C2 4B 6C D1 [E] Count:74

PID: 23h B8h-Crypt8:F8 A6 F4 2B E1 BA 4E 7B [E] Count:13311
PID: 23h B8h-Crypt8:27 96 F4 2D ED 75 F2 54 [E] Count:13310
PID: 23h B8h-Crypt8:2A A3 35 4F C2 4B 6C D1 [E] Count:13310
PID: 23h B8h-Crypt8:2D 8B A2 AF B5 A8 A3 18 [E] Count:13310
PID: 23h B8h-Crypt8:9F 72 23 53 B8 EC 9D E0 [E] Count:13310
PID: 23h B8h-Crypt8:B3 57 87 0B EA 68 6A C6 [E] Count:13310
PID: 23h B8h-Crypt8:D7 89 25 5D 1F EE 07 81 [E] Count:13310

Time for searching Crypt8 = 3 sec.







 
Last edited:

bh62549

Registered
Messages
657
Channel 1/1
On Table_ID: 0x42 (current mux)
Service Name: ENC 1
Provider Name: MX1
Transport Stream ID: 1 (0x0001)
Original Network ID: 65535 (0xffff)
 

barney115

Donating Member
Staff member
Administrator
Messages
24,733
On ku band "service-1" feeds have been Tandberg Encrypted recently for EPL Coverage and highlights no solution was found as yet for Tandberg .

ID of ENC-1, ENC-3 etc..are MX-1 USA Feeds
sometimes they provide a good Crypt8 but a lot of times u have to just keep trying until a good C8 with a big high count comes along ..this Crypt8 you posted above is likely the best example of a fake/Fail C8 where a key will never get found

, sometimes it helps a lot when you can try using CWFinder09 => https://www.sat-universe.com/showpost.php?p=2037030231&postcount=1044

CWFinder 1.0 => https://www.sat-universe.com/showpost.php?p=2037031406&postcount=1046

There is a decent chance to find a valid key with those tools when valid Crypt8's are just not being found .
perhaps even investing in a cheap China Box with Biss AU may help too it does work for about 85-90% of feeds when servers are online and working .
 

Stefan2k16

Registered
Messages
44
CWFinder uses a list of previously found keys. If the key they are using happens to be one that's already been found and in that list, Using a list of known keys is a quick way to find already known keys. However, it doesn't work for new and unknown keys. Then you'll need to use Cudabiss. Cudabiss is a brute force method of finding keys and should eventually find a key. It just takes a bit longer. How long depends on how many cuda devices you have working simultaneously and how fast they are. Hint, you can run multiple instances of Cudabiss and assign each instance to a separate CUDA device. So, if, for example, you have a system with 8 GTX 1080 cards, you can have all 8 cards searching a different range of keys for the same key. Of course the list attack and crypt8 attack are usually quicker and you should therefore try them first. But if those 2 methods fail, Cudabiss is the final solution and should find the key. It just takes more time and/or more resources.

It's a shame that Cudabiss stopped being developed. Perhaps with more modern cards, there could have been greater optimizations that would have made it faster.
 

MarinaLee

Registered
Messages
81
On ku band "service-1" feeds have been Tandberg Encrypted recently for EPL Coverage and highlights no solution was found as yet for Tandberg .

ID of ENC-1, ENC-3 etc..are MX-1 USA Feeds
sometimes they provide a good Crypt8 but a lot of times u have to just keep trying until a good C8 with a big high count comes along ..this Crypt8 you posted above is likely the best example of a fake/Fail C8 where a key will never get found

I wonder why no one wants to remember about the bundle with the program HEX editor?

It's a shame that Cudabiss stopped being developed. Perhaps with more modern cards, there could have been greater optimizations that would have made it faster.

Thank you for remembering about CUDABISS, that is good programm, just found a solution to work with this program with new processors. With the help of which good results were obtained in the calculations of time.:)
 
Top