@Colibri.DVB Sir, I've got couple of questions. Can you tell me what is the plain type 08hx00h, 08hxFFh and 08hx000300h for? What's the difference between all of those plain types and B8hx00h, B8hxFFh and B8hx030000? Do I need to download all of those plain types to get the program work?
More than 2000 GB CSA-RBT v1 tables
- Thread starter Colibri.DVB
- Start date
Let me answer what I know,in layman terms.
you generally need the B8xXX tables.
Those numbers mean how the provider send the data we are looking for,different data needs a different table.
The program needs at least one table,but if you provider use a different format,you won;t find the cw,you need the according table.
Start with Bhx00 and BhxFF table 1.
I advice you to read how rainbow tables work in this same forum,you will understand better.
you generally need the B8xXX tables.
Those numbers mean how the provider send the data we are looking for,different data needs a different table.
The program needs at least one table,but if you provider use a different format,you won;t find the cw,you need the according table.
Start with Bhx00 and BhxFF table 1.
I advice you to read how rainbow tables work in this same forum,you will understand better.
guddu09993
Donating Member
- Messages
- 606
plain type is nothing but two words hexa decimal that speicify length and type of encryption being used by the crypt8 algorithm
the first word denotes the length and the second word denotes the typeof encryption
b8h = 184 pay load size
ffh is the transport stream encoding scheme
00h is mpeg2 encoding,
ffh and 030000h are type of mpef 4 encoding
if u want to create new plain type you need to increase the pay load size by 8h. currently three pay load sizes are used. 08, A0 and B8. where 08 is 8 bit pay load size, A0 is 160 bit pay load size and B8 is 184 pay load size. similarly you can load new plain type by incrementing for 8 to 256 in increment of 8.
for example for size 256 bit payload the pain type would be 100hx00h , 100hxffh and 100hx030000h
i think it will help you
if i am wrong please correct me. As far as i know i have this information and understanding.
you should download all files......
the first word denotes the length and the second word denotes the typeof encryption
b8h = 184 pay load size
ffh is the transport stream encoding scheme
00h is mpeg2 encoding,
ffh and 030000h are type of mpef 4 encoding
if u want to create new plain type you need to increase the pay load size by 8h. currently three pay load sizes are used. 08, A0 and B8. where 08 is 8 bit pay load size, A0 is 160 bit pay load size and B8 is 184 pay load size. similarly you can load new plain type by incrementing for 8 to 256 in increment of 8.
for example for size 256 bit payload the pain type would be 100hx00h , 100hxffh and 100hx030000h
i think it will help you
if i am wrong please correct me. As far as i know i have this information and understanding.
you should download all files......
Last edited:
Ok,I was finishing setting up the program and tables i downloaded.
I was testing some of the crypt8 people post in the said thread,and it find the cw in about 6-7 minutes.
Is that an average time?
Considering I am using a sdd external usb,program and all tables in it.
I wonder if search time will improve f I install the ssd internally?
Is not a bad search time for me as it is,but if the difference is really significant,I can install it internally.
In another note,I would like to merge tables,but I am afraid how big will become.Someone before mentioned it got to almost 500gb.
Did anyone merged tables 1 and 2 and how big they got?
I was testing some of the crypt8 people post in the said thread,and it find the cw in about 6-7 minutes.
Is that an average time?
Considering I am using a sdd external usb,program and all tables in it.
I wonder if search time will improve f I install the ssd internally?
Is not a bad search time for me as it is,but if the difference is really significant,I can install it internally.
In another note,I would like to merge tables,but I am afraid how big will become.Someone before mentioned it got to almost 500gb.
Did anyone merged tables 1 and 2 and how big they got?
Last edited:
Thank for answering my question.
By the way, you can merge the tables as big as you want, but many peoples suggest that the table should not bigger than 192 GB because it won't increase the possibility to find the key (The percentage to find the key still 99.2% although your table has 1000 GB) and will spend more minutes to find the key.
By the way, you can merge the tables as big as you want, but many peoples suggest that the table should not bigger than 192 GB because it won't increase the possibility to find the key (The percentage to find the key still 99.2% although your table has 1000 GB) and will spend more minutes to find the key.
Last edited:
A bigger table with no duplicated chains must have a higher chance of finding a key.
I built my original 460 GB tables in partnership with another person. We individually made the chains. It was all pre-planned so that we did not duplicate any.
I agree, that with my table it might take longer to find a key, but it definitely has a higher chance of finding a valid key because of the number of chains within the table.
I built my original 460 GB tables in partnership with another person. We individually made the chains. It was all pre-planned so that we did not duplicate any.
I agree, that with my table it might take longer to find a key, but it definitely has a higher chance of finding a valid key because of the number of chains within the table.
But if the chances grow only 6% from a 200gb table to a 460gb,it does seem it doesn't justify the expense of having more ssd storage,I agree everything is about your budget,if you can afford it,do the best.
But I just installed 4 tables in a 1tb ssd,and there is only 150gb left.I might just move the least used table to make room to merge the more used ones.
This are only table 1,success rates from 86% to 92%,I think I can live with those odds,increasing would mean to expend double than already spent.
In case I do not find a cw...................I'll give the crypt8 to dog-man,he he.
But I just installed 4 tables in a 1tb ssd,and there is only 150gb left.I might just move the least used table to make room to merge the more used ones.
This are only table 1,success rates from 86% to 92%,I think I can live with those odds,increasing would mean to expend double than already spent.
In case I do not find a cw...................I'll give the crypt8 to dog-man,he he.
B8hx00h_table2.z01 its been offline for couple days.
It looks like mega is pushing me to install a firefox mega plugin to get it (and still the question if will be possible after that) ,which i do not want and didn;t need it for any other parts.
Can anyone upload it again to mega??
It looks like mega is pushing me to install a firefox mega plugin to get it (and still the question if will be possible after that) ,which i do not want and didn;t need it for any other parts.
Can anyone upload it again to mega??
Last edited:
guddu09993
Donating Member
- Messages
- 606
Fire fox mega plugin will not help. wait for one or two days it will be online again as i also was facing the same problem with some files in start.
there are many who have fast internet speed and can upload missing files so wait it should be online again.....
there are many who have fast internet speed and can upload missing files so wait it should be online again.....
Liquor Twát
Registered
- Messages
- 160
why dont you analyse the 800gb table to get a list of the chains that are in it and their counts, that will tell you if you have any duplicate chains?
Liquor Twát
Registered
- Messages
- 160
version 1.18f or later has an option from some keystrokes to get into the analyse menus
guddu09993
Donating Member
- Messages
- 606
reupload link for B8hx00h_table2.z01
i have re-uploaded the file and here is the link
https://mega.nz/#!ehchVJRb!Sp7eHyXmRdaFn_yv7H9JoRINqWahRggIX5srOeO_pmI
i have re-uploaded the file and here is the link
https://mega.nz/#!ehchVJRb!Sp7eHyXmRdaFn_yv7H9JoRINqWahRggIX5srOeO_pmI
Thank you very much
Last edited: