What is on CSA-RBT v2.05 table

[cayoenrique]

I took a break a day or two before. And I decided to download and look at tables v2.05. I did have trouble downloading as others do. But I got enough to look at the file. lets say for example CSA_B8hxFFh_1000h_6AFFFFFEh_80666663h.rbt2

busybox od -t x1 -N 600 -v CSA_B8hxFFh_1000h_6AFFFFFEh_80666663h.rbt2-{80f1f449-5d68-4de1-82ed-1e4e8150b155}.dtapart

0000000 22 ca 66 15 b9 98 28 53 b7 28 16 bc 07 48 7e da
0000020 90 6a c1 c2 80 98 34 61 96 fd d2 2d 21 5f dc 31
0000040 54 13 24 2e dc a2 ee 6b d9 0a d1 e9 12 50 b6 d5
0000060 41 d5 39 bf c1 44 17 04 29 cc ff 03 70 d0 07 46
0000100 db 6d ca 5d 0a ba a4 7c 01 c2 90 bc 0d 5f 3b d5
0000120 d9 c9 14 ba 00 1e fd d2 0d c1 0b 59 e5 ec a4 a8
0000140 cc 40 9b e9 73 7d 31 ed d5 bd 7a f6 4f f5 25 c8
0000160 b0 79 96 df be e1 d5 00 4b 59 ad 67 3a 2a 59 72
0000200 a2 ac 68 44 32 ad c6 c4 fd 53 c4 e6 52 8a 76 12
0000220 05 37 0e fa 9b ca da 12 0d db e5 13 ba 28 ef 43
0000240 29 c0 9f 75 db 90 7e 26 7c 83 1d 46 6e 4b 70 e7
0000260 d2 d7 a2 47 56 3d 78 9c e7 60 a6 dc 02 6e 1d 24
0000300 1c e6 39 ea a8 50 d3 6d 64 ff 37 06 94 62 9b 02
0000320 79 61 d4 f3 cb c6 d7 a2 eb 41 a2 a7 d9 bd 86 f9
0000340 60 03 7e a9 66 a2 aa 74 f1 58 47 dc 3b 91 37 f1
0000360 b5 c3 97 e8 ab 2d 38 20 fb 73 a6 28 d1 30 be 03
0000400 6d b5 5d d6 88 d9 92 aa 11 b9 22 33 10 a0 fe 22
0000420 00 9b 49 8b 16 60 f9 3d 00 00 00 00 00 00 00 00
0000440 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000460 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000500 7d 42 92 b6 25 4f c2 ea a7 4b d6 00 82 c3 db 4b
0000520 4e 81 1f 43 b0 32 88 c6 76 13 34 95 ec 69 f6 23
0000540 48 a6 f0 f8 fa 31 25 c0 17 1d 0f 4a 65 f2 a8 b6
0000560 1d 63 7d e6 af 3b 3c 30 27 b0 6c d4 84 06 9f 3e
0000600 de fe 10 f9 e1 47 2f b0 98 cf 2e cd 79 c8 82 5b
0000620 ed 54 ae 9c 69 0d 98 1c fd dd 3b d4 80 22 75 ed
0000640 62 01 32 2e 35 d6 b0 32 94 aa 76 34 a5 04 b2 5e
0000660 4a 39 fe 20 cd 55 a2 a5 1b 6c c0 2f 8e 43 89 de
0000700 9e 69 9a d8 43 2c ef 4d 86 2f 6c 21 20 b2 84 cf
0000720 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000740 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000760 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0001000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0001020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0001040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0001060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0001100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0001120 00 00 00 00 00 00 00 00
0001130

So my question is , if any of you know how to interpret this bytes. With the intention to provide in the future a tool that can be used to use this tables but that can be done in OpenCL. Clearly to allow those that do not have Nvidia GPU to use the tables.

2) ChainAuthor_415.txt
Clearly show a list of rbt vs I guess user that help colibri on that table. For example "CSA_08hx000300h_10000h_009F30h,pengky"
Do you also know what is the purpose of binary file ChainAuthor.map
And Can any one explain me what are this binary file do or contain : ChainAuthor.map

Thanks

 

[sattechtips]

2) ChainAuthor_415.txt
Clearly show a list of rbt vs I guess user that help colibri on that table. For example "CSA_08hx000300h_10000h_009F30h,pengky"
Do you also know what is the purpose of binary file ChainAuthor.map
And Can any one explain me what are this binary file do or contain : ChainAuthor.map

http://colibri.bplaced.net/CSA-Rainbow-Table-Tool-V2 Documentation_V1.00.pdf
v2 nowadays to is more useless, when price of ssd are too cheap and v1 can be used in other soft

 

[moonbase]

ChainAuthor_415.txt
Clearly show a list of rbt vs I guess user that help colibri on that table. For example "CSA_08hx000300h_10000h_009F30h,pengky"
Do you also know what is the purpose of binary file ChainAuthor.map
And Can any one explain me what are this binary file do or contain : ChainAuthor.map

Thanks

If a chain file is not recorded in the ChainAuthor.map file that chain cannot be merged to be used in a v2 rainbow table.

The ChainAuthor.map file is a control file created by Colibri to force v2 chain creators to publicly upload the v2 chain files they had created to the forum that hosted the project topics.
This forced v2 chain creators to publicly share their v2 chain files. If they did not share, these v2 chains were useless and could never be used.

Only Colibri could update the ChainAuthor.map file and it was only updated for v2 chain files that were publicly shared. Nobody else could update the ChainAuthor.map file.
The ChainAuthor.map file was created to stop the leeches and maggots who created thousands of v1 chain files and did not share them publicly on the forum that hosted the projects.

 

[cayoenrique]

I see. So colibri was forcing people to share from quite some time. Interesting, Never thought on that.

Yes I have a very short download of V1 that was given to me sometime ago. And I like it. But was giving, second thought to help those that had no good Nvidia GPU. But without this missing map info/decode then there is not much to do.

"leeches and maggots" this is a force you can not compete or think you can make them change. People with this behavior have been in the Face of Earth from the creation. And in fact if you think a little you can see this behavior in economics. The 1% of the population that have most of the riches of the world uses the other 99% to increase even more their pocket.

Look at my last threads, some how they are the most reads in forum lately, but most of the users here that read those threads do not post and share the knowledge they already have.

 

[moonbase]

Look at my last threads, some how they are the most reads in forum lately, but most of the users here that read those threads do not post and share the knowledge they already have.

Yes, I agree, your recent topics have been viewed a lot of times and input has been from only a few members, perhaps a lot of the viewers are lurkers?
It is a shame there have not been more members providing feedback as I think the topics are interesting and you have done a lot of good work.

However, in one of your topics you asked people not to share results if the speed of their key search was faster than the benchmark.
Here is what you requested in the "GPGU using Opencl" topic

"Now as a Personal request, if you find the code to go faster than your KPS column for your device PLEASE do not post publicly results here..."

Once you have shared the code or the exe files on a public forum I do not see the point of asking users not not publicly share their results back on the same forum.
If the Chinese box manufacturers are interested, they will have already downloaded the software tools and could be testing the speeds, the bird is flying....

 

[cayoenrique]

moonbase

I understand your point of view, in fact is the official view of the forum some how. Something like if it is public post is ok.

The specs to change CSA has been submitted from mid 2000 decade. But CSA survive. It was the Chinese with the UA thing that force some operators to come up with implementation of BISS2.

It is simple I do not want to be remember as the guy that brought Darkness to TV SAT. All what we see is base on CSA, well with some exceptions lime powervu DES and some others.
If I post the sources is to teach others so that a possible solution to AES can be promoted. The release is not for the ones that hope to claim they are the master of the problem, just because they have the economic power to purchase the latest GPU. The last sentence has no user name attached to it. It is a generic thought.

Simple, learn, test your self and teach others.

If we adapt this concept to economics, it will be like communism. Make money, enjoy your money and give up to others part of the money you earn. Clearly those one that base their life in economics will not do: "give up to others part of the money you earn"

One more time, I like to be remember of one that did share what he learned. Not the one that kill CSA.

 

[moonbase]

.... It was the Chinese with the UA thing that force some operators to come up with implementation of BISS2.

It is simple I do not want to be remember as the guy that brought Darkness to TV SAT. ...

One more time, I like to be remember of one that did share what he learned. Not the one that kill CSA.

@cayoenrique

To correct an earlier comment you made, the biss2 protocol was developed and implemented before the Chinese started manufacture of their AU boxes.
My view is that biss2 development began by the EBU shortly after the rainbow table tool v1 was released on another forum in June/July 2012.
There is evidence that the v1 rainbow table tool was operational as early as November 2011 but was not publicly shared for another 8 or 9 months.

Publication of the v1 tool and subsequently the v2 tool made the EBU realise biss was breached so they acted to remedy this with biss2.
All of this was years before the Chinese came along with their AU receivers, the Chinese AU boxes simply increased the user base with the capability to view biss feeds.

I would not worry about being labelled as the guy who killed CSA. The biss2 protocol has been in operation for years before you started making your recent posts on the forum.

 

[cayoenrique]

We are saying the same thing. BISS2/AES is a very old Spec. A theory but not in used for many many years. Sure there where test seen on sats. But not used in any real feeds.

Where we disagree, is that I say that the so called AU was the reason for operators to IMPLEMENT BISS2/AES on today's Feeds.

Now as you know BISS may use CSA. And also as you know CSA is in fact the basics Video encryption for most of all CAS. We agree in this.

What we disagree , is that I say, CSA may still useful for the near future 5-10 or so years. Instead that future can show up earlier, in month or just one/two years if we push to hard.

I do not when I did became active in sat, most likely in the 2015. I wish I knew colibri's work on the start of the 2010 decade.
I never met colibri. I assume he is just a sat enthusiast, no professional cryptographer. Assuming he is just an enthusiasts he is not likely the real creator of RBT and CSA attacks. He most has been one of the lucky guys to read the many papers publish on the subject. Colibri most likely the 1rst one to implement such papers in real hands on practical work. And here we are, yes we including me, the "leeches and maggots" that enjoy his work.

Listen, I been trying to learn from old papers many many years ago. But I did not study cryptography. So I understood 1% of what it was written. But once I found colibris pdf. I understood most of it from the very 1rst time. Impressive work. Long live colibri.

 

[moonbase]

We are saying the same thing. BISS2/AES is a very old Spec. A theory but not in used for many many years. Sure there where test seen on sats. But not used in any real feeds...


I never met colibri. ...Assuming he is just an enthusiasts he is not likely the real creator of RBT and CSA attacks.

1. There are real feeds that use biss2 on a daily basis, some of the big broadcasters in Europe use biss2 regularly, there are often posts on this forum listing these feeds.
2. Rainbow tables may have been in existence before the work of Colibri? However, the biss rainbow tools and tables used today by enthusiasts for satellite feeds were his creation.

In addition to the biss contribution, to the best of my knowledge, Colibri was also the person who found the Tandberg and PowerVu hacks that were subsequently implemented in various tools and later on in the Chinese boxes?

Standard biss is used globally but biss2 is used mainly in the EBU zone. Outside the EBU zone there is not much use of biss2.
This is to be expected, the big broadcasters who are based in countries within the EBU zone are expected to comply with EBU regulations with their feeds for main sporting events.

Again, do not worry that your recent topics will cause dark screens, they will not.
If you get a hack for NS3/NS4, viaccess, irdeto or conax and publish it then you can expect a knock on your door.

 

[C0der]

Agreed with Enrique: We shouldnt "push too hard".
(And no, Colibri wasnt the first with PowerVu, just the one who published stuff.)

Back to topic:
In case you are asking about Rv2.10 too...They are assumed to be encrypted in an unknown way.

 

[cayoenrique]

Listen I am having some fun with Stream Crypt. Nothing important but interesting. I sit every day in front of computer to try to write some code. Never start, keep thinking in the way to handle. HE HE HE.
Well I am about to start. So from spare time to spare time I thought in doing something more easy. Well I thought it was easy to handle RBT V2 tables. Just to find out, they are obfuscated.

I know you are going to ask. In my books, look for
p5a1.pdf ANALYSIS OF THE DVB COMMON SCRAMBLING ALGORITHM

Then read Chapter 4 Analysis of the Stream Cipher

 

[C0der]

About that paper: There was another paper that said, the small cycle lengths were wrong.

 

[cayoenrique]

I just want to look at the problem. Work or not it is interesting how he split the operation in three part. Clearly is not that easy due to the feedback path. But still interesting, more easy to understand.

 

[klickklack]

I took a break a day or two before. And I decided to download and look at tables v2.05. I did have trouble downloading as others do. But I got enough to look at the file. lets say for example CSA_B8hxFFh_1000h_6AFFFFFEh_80666663h.rbt2

busybox od -t x1 -N 600 -v CSA_B8hxFFh_1000h_6AFFFFFEh_80666663h.rbt2-{80f1f449-5d68-4de1-82ed-1e4e8150b155}.dtapart

0000000 22 ca 66 15 b9 98 28 53 b7 28 16 bc 07 48 7e da
0000020 90 6a c1 c2 80 98 34 61 96 fd d2 2d 21 5f dc 31
0000040 54 13 24 2e dc a2 ee 6b d9 0a d1 e9 12 50 b6 d5
0000060 41 d5 39 bf c1 44 17 04 29 cc ff 03 70 d0 07 46
0000100 db 6d ca 5d 0a ba a4 7c 01 c2 90 bc 0d 5f 3b d5
0000120 d9 c9 14 ba 00 1e fd d2 0d c1 0b 59 e5 ec a4 a8
0000140 cc 40 9b e9 73 7d 31 ed d5 bd 7a f6 4f f5 25 c8
0000160 b0 79 96 df be e1 d5 00 4b 59 ad 67 3a 2a 59 72
0000200 a2 ac 68 44 32 ad c6 c4 fd 53 c4 e6 52 8a 76 12
0000220 05 37 0e fa 9b ca da 12 0d db e5 13 ba 28 ef 43
0000240 29 c0 9f 75 db 90 7e 26 7c 83 1d 46 6e 4b 70 e7
0000260 d2 d7 a2 47 56 3d 78 9c e7 60 a6 dc 02 6e 1d 24
0000300 1c e6 39 ea a8 50 d3 6d 64 ff 37 06 94 62 9b 02
0000320 79 61 d4 f3 cb c6 d7 a2 eb 41 a2 a7 d9 bd 86 f9
0000340 60 03 7e a9 66 a2 aa 74 f1 58 47 dc 3b 91 37 f1
0000360 b5 c3 97 e8 ab 2d 38 20 fb 73 a6 28 d1 30 be 03
0000400 6d b5 5d d6 88 d9 92 aa 11 b9 22 33 10 a0 fe 22
0000420 00 9b 49 8b 16 60 f9 3d 00 00 00 00 00 00 00 00
0000440 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000460 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000500 7d 42 92 b6 25 4f c2 ea a7 4b d6 00 82 c3 db 4b
0000520 4e 81 1f 43 b0 32 88 c6 76 13 34 95 ec 69 f6 23
0000540 48 a6 f0 f8 fa 31 25 c0 17 1d 0f 4a 65 f2 a8 b6
0000560 1d 63 7d e6 af 3b 3c 30 27 b0 6c d4 84 06 9f 3e
0000600 de fe 10 f9 e1 47 2f b0 98 cf 2e cd 79 c8 82 5b
0000620 ed 54 ae 9c 69 0d 98 1c fd dd 3b d4 80 22 75 ed
0000640 62 01 32 2e 35 d6 b0 32 94 aa 76 34 a5 04 b2 5e
0000660 4a 39 fe 20 cd 55 a2 a5 1b 6c c0 2f 8e 43 89 de
0000700 9e 69 9a d8 43 2c ef 4d 86 2f 6c 21 20 b2 84 cf
0000720 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000740 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000760 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0001000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0001020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0001040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0001060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0001100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0001120 00 00 00 00 00 00 00 00
0001130

So my question is , if any of you know how to interpret this bytes. With the intention to provide in the future a tool that can be used to use this tables but that can be done in OpenCL. Clearly to allow those that do not have Nvidia GPU to use the tables.

2) ChainAuthor_415.txt
Clearly show a list of rbt vs I guess user that help colibri on that table. For example "CSA_08hx000300h_10000h_009F30h,pengky"
Do you also know what is the purpose of binary file ChainAuthor.map
And Can any one explain me what are this binary file do or contain : ChainAuthor.map

Thanks

These tables could be updated by everyone with new chains, but only with the new implementation of Colibri in the chainauthor.map could they be used. In the end, only 16-18% unfound CWs remained. These update files had to be uploaded publicly!