My new Biss Server plans

jenseneverest

Registered
Messages
178
People do not concern yourself with how much my planned server setup would cost. It's my money to spend. I do it because I can. It will be interesting to see the performance of such a system.

It will either be a great bruteforce machine or a great gaming machine. :D

Absolutely
I know some of my other hobbies cost stupid money. This looks like it will be mega once done. Best of luck I will be following the thread with interest.

The Holy grail of on the fly brute force decoding is of course the ultimate goal.
Perhaps a super computer? They can be rented now day's.....
 

campag5242

Feed Hunter
Messages
2,585
If you do get the new hardware Blackcrusader, please post results for fastest & failed v1 rbt search, and BF speed MCW/sec.
 

barney115

Donating Member
Staff member
Administrator
Messages
24,745
Since we already know BISS 2 2610 is already here and in use would it really be worthwhile investing a lot of time and effort and money in an already dying encryption ? :confused:
 

BLACKCRUSADER

Senior Member
Messages
1,994
No that table is not 319GB, it's more like 200GB. If it were 319GB there'd be > 200,000 chains reported as being found.

Here is a scan from AS5 100.5e 3860 v 30000 today

How many chains do I have?

TS file: C:\Users\STADIUM\Desktop\100.5E_3859.718_V_30000_(2021-04-14 09.33.33)_dump.ts
Using PID: 401
Using file limit: 4096 MByte
File length: 3015 MByte
UsingFileLen: 3161720080 bytes
Reading file ...
Searching ...
Using payload size: 184
PID: 191h B8h-Crypt8: 5B AA D2 F6 B5 11 BB 78 [E] Count:211

Time for searching Crypt8 = 3 sec.

Search CW Start
RBT file: D:\Biss V1 file\B8hxFFh\B8hxFFh_table2\CSA_B8hxFFh_10000h.rbt
Calc all 10000h end values for this crypt ... (using file cache)
Search end values in RBT ...
Searching CW in RBT ...
Found 216387 possible chains (harddisk only search time = 114 sec.)

Analysing chains ... (will be 10 times slower if an other thread is keeping the GPU busy)
found CW: AC XX XX XX XX XX XX 34
Search CW done (106 sec.)
 
Last edited:

campag5242

Feed Hunter
Messages
2,585
@ Blackcrusader: That chain count is typical of public table1 + table2 merged, so I'm confident your table has ~28.5 billion chains / file size ~341GB.

File length: 3015 MByte :eek: At 30Mbps that's around 15 minutes of recording. :eek:

Same search, same table size, 10.8s for same CW here.

@barney115: I for one am guilty of spending way too much time on rbt.
 

BLACKCRUSADER

Senior Member
Messages
1,994
No that table is not 319GB, it's more like 200GB. If it were 319GB there'd be > 200,000 chains reported as being found.

As cayoenrique has said, RBT disk performance is about seek time time / random small reads, not continuous / sustained transfers. Go to https://www.userbenchmark.com/ and compare results for Random 4k reads for existing & proposed SSD to see what factor speedup you might obtain.

@ Blackcrusader: That chain count is typical of public table1 + table2 merged, so I'm confident your table has ~28.5 billion chains / file size ~341GB.

File length: 3015 MByte :eek: At 30Mbps that's around 15 minutes of recording. :eek:

Same search, same table size, 10.8s for same CW here.

@barney115: I for one am guilty of spending way too much time on rbt.

I am happy your search only took 10 point 8 seconds to get a CW, must be a very nice V1 system.

Asiasat 5 3860 v 30000 is 67Mbps so that was maybe a 6 minute recording. Normally I only record 300mb but sometimes I get distracted and record larger files as I am online doing other things at the same time.
 
Last edited:

BLACKCRUSADER

Senior Member
Messages
1,994
@ Blackcrusader: That chain count is typical of public table1 + table2 merged, so I'm confident your table has ~28.5 billion chains / file size ~341GB.

File length: 3015 MByte :eek: At 30Mbps that's around 15 minutes of recording. :eek:

ASIASAT 5 100.5E 3860 V 30000 40 second recording......

TS file: C:\Users\STADIUM\Desktop\100.5E_3859.785_V_30000_(2021-04-14 14.14.15)_dump.ts
Using PID: 401
Using file limit: 4096 MByte
File length: 317 MByte
UsingFileLen: 332756240 bytes
Reading file ...
Searching ...
Using payload size: 184
PID: 191h B8h-Crypt8:66 4E B1 36 15 8C 88 12 [E] Count:116314
PID: 191h B8h-Crypt8:00 8A 84 9D C7 71 DB EB [E] Count:68
PID: 191h B8h-Crypt8:00 93 BA A1 1B A9 B1 15 [E] Count:68
PID: 191h B8h-Crypt8:00 F4 E0 1B 5A BB 68 E9 [E] Count:68
PID: 191h B8h-Crypt8:01 3A AC F3 D3 AF E8 71 [E] Count:68
PID: 191h B8h-Crypt8:01 AC C7 24 6E 00 F1 0B [E] Count:68
PID: 191h B8h-Crypt8:02 3B CD D2 F2 03 15 3B [E] Count:68
PID: 191h B8h-Crypt8:02 DF F9 10 C5 BE 38 65 [E] Count:68
...

Time for searching Crypt8 = 0 sec.
Search CW Start
RBT file: D:\Biss V1 file\B8hxFFh\B8hxFFh_table2\CSA_B8hxFFh_10000h.rbt
Calc all 10000h end values for this crypt ... (using file cache)
Search end values in RBT ...
Searching CW in RBT ...
Found 217891 possible chains (harddisk only search time = 97 sec.)


Of course every time a TS stream is recorded we get different results for the tables counted and speed used.
 
Last edited:

BLACKCRUSADER

Senior Member
Messages
1,994
D:\Biss V1 file\B8hxFFh\B8hxFFh_table2
Size on disk 318 GB (341,449,900,032 bytes)
Created ‎Monday, ‎October ‎30, ‎2017, ‏‎11:07:27 PM




Search Crypt8 in TS Start
TS file: C:\Users\STADIUM\Desktop\100.5E_3859.785_V_30000_(2021-04-14 14.14.15)_dump.ts
Using PID: 406
Using file limit: 4096 MByte
File length: 317 MByte
UsingFileLen: 332756240 bytes
Reading file ...
Searching ...
Using payload size: 184
PID: 196h B8h-Crypt8: DD 55 87 35 5B 18 1D E9 [E] Count:393793
PID: 196h B8h-Crypt8: 65 BD A4 CD C3 6A E6 99 [E] Count:68
PID: 196h B8h-Crypt8: D2 96 A2 6E 20 47 35 D2 [E] Count:68
PID: 196h B8h-Crypt8: EA 7B 4B 2D 55 55 63 57 [E] Count:68

Time for searching Crypt8 = 0 sec.
Search CW Start
RBT file: D:\Biss V1 file\B8hxFFh\B8hxFFh_table2\CSA_B8hxFFh_10000h.rbt
Calc all 10000h end values for this crypt ... (using file cache)
Search end values in RBT ...
Searching CW in RBT ...
Found 219226 possible chains (harddisk only search time = 96 sec.)
Analysing chains ... (will be 10 times slower if an other thread is keeping the GPU busy)
found CW: 88 XX XX XX XX XX XX 7F
Search CW done (103 sec.)
 
Last edited:

Sunrise999

Registered
Messages
46
I'd be interested if the video card you chose is in stock over there, here in NA $500 dollar cards are selling for up to $1500. Also CPU's seem to be sparse.
 

BLACKCRUSADER

Senior Member
Messages
1,994
I'd be interested if the video card you chose is in stock over there, here in NA $500 dollar cards are selling for up to $1500. Also CPU's seem to be sparse.

I am a regular customer that buys complete servers. So if I buy a complete motherboard with Ram, GPU, M2 SSD for OS, power supply etc then yes it may take a bit of time but the priority is to known customers.

Nvidia RTX 3090 costs around US$1950 here. Prices are what they are.
 

campag5242

Feed Hunter
Messages
2,585
@blackcrusader, these crypt8 will work your system for a little longer than those selectively chosen (favourable times) you like to post:

25 C0 D1 42 1C 90 F4 13
8A 45 49 D8 E0 67 83 15
86 5F B0 B0 4E 89 20 9E
CF E9 16 E8 75 C8 A2 60
28 5D D1 C0 53 A7 AD B1
94 9D AF E0 2B 14 79 B8

And these even harder:
FB 78 43 9A 0A 91 D3 86
38 B2 6E 93 84 6F 9D 9C

Plain copy/pastes only, no mixing of table sizes v log output (post #12) or turning back time (post #24). I will be able to see if things don't add up.
 

cayoenrique

Member
Messages
475
I need clarification on what is your ystem now.

You started the thread having on hand a "PC (i7-6700 / 8GB / GTX1070TI / SATA3 SSD) ". And with desired to build a new one. Did you put together the new one?

In general I am interested to compare with the speed provided on last post. This means:

"RBT file: D:\Biss V1 file\B8hxFFh\B8hxFFh_table2\CSA_B8hxFFh_10000h.rbt"

I assume Table: V1 ONLY B8hxFFh_table2.z01-z23

And in average ( not to be exact )

**SSD Time: harddisk only search time = 96 sec
**GPU Time: Search CW done (103 sec.)

So Total search time: 103+96 = 199 sec?

Finally can you search an impossible crypt 8. Yes as when result in cw for crypt8 not found. That is the best way to test GPU speed as it should ensure more or lest constant length (the longest). We should create a standard like testing for "00 00 00 00 00 00". I do not know if that gets and impossible but hope you get an Idea.

I give you a personal example, in my case if I search for SEARCH_CW_CRYPT:"37 21 07 9B EE C9 13 FF" I end up using 0 GPU time, as it found on first GPU search. It gets even worst when I do it on second time for that number. As with the PC/HDD cache plus the program ecw file caches I find correct cw on 0 TOTAL time.

My modified RBT table only contains B8hxFFh_table1.z01-z24 and B8hx00h_table1.z01-z30 That is all I have.
 
Last edited:

cayoenrique

Member
Messages
475
campag5242

Yess I see. Thanks for the clarification those are your PC specs.

Also I am sorry if did confuse you but some how my last post got incomplete 1rst time and I was editing it.

And I see you post some crypt8 to used as standard. See we where on same page.

Thanks a lot.
 

cayoenrique

Member
Messages
475
This been good test for me. I have learn a little more on my side.


Hardware
CPU: AMD Phenom(tm) 9600 Quad-Core Processor
MotherBoard: TA785GE 128M
** for Brute-Force the motherboard is a limiting factor due to limited Speed of my x16 PCIE. But for crypt8 should not be of big importance.
Memory 8GB ** but again old type lower speed. Again for crypt8/cw not important.
GPU: ATI Tahiti PRO [Radeon HD 7950
32 Compute Units, that result in 1792 stream core processors @ 800 MHz
3 GB of Memory

OS Linux Debian

RGT -
Original Table 1 ONLY of both CSA_B8hxFFh_10000h.rbt & CSA_B8hxFFh_10000h.rbt
CSA_B8hx00h_10000h.rbt 198.8 GiB (213,406,187,520 bytes)
CSA_B8hxFFh_10000h.rbt 162.8 GiB (174,751,481,856 bytes)
Total 198.8+162.8 = 361.6 GIB
Success rate B8hx00h_table1: 90.4% (904/1000 found)
Success rate B8hxFFh_table1: 86.3% (863/1000 found)


In general I was assuming that my biggest time consumption was in read to disk ( in my case 2 128 ScanDisk + 1 128 Generic Flash ). But I spent the night on the program making sure that I could clearly track my GPU time consumption. So I made some changes. You did not said of what table 00 or FF where each test values. So I did 3 of all. The 2 so called hardest and the first one. In the next post is the rest of my results.

Using Crypt8 String: 38 B2 6E 93 84 6F 9D 9C
Table B8hx00h has been selected
Exhaustive Search: Stop at 1st cw found
ECW Creation
Calc all 10000h end values for this crypt.
GPU: Time creation for 10000h end values (0 min. 39 sec.)
Using file cache: /mnt/sdc6/CSA_RBT/CSA_B8hx00h_10000h_38B26E93846F9D9C.ecw
Chain Analysis
Matching ECW vs RBT Chains
Using Crypt8 String: 38 B2 6E 93 84 6F 9D 9C
9F Found unique:4264 Total:16687 in 20 sec
1F Found unique:4239 Total:16752 in 30 sec
BF Found unique:4245 Total:16806 in 23 sec
1F CW not found. GPU Time (0 min. 24 sec.)
3F Found unique:4272 Total:16720 in 31 sec
DF Found unique:4250 Total:16476 in 24 sec
9F CW not found. GPU Time (0 min. 24 sec.)
FF Found unique:4320 Total:17176 in 23 sec
5F Found unique:4334 Total:17145 in 32 sec
3F CW not found. GPU Time (0 min. 24 sec.)
7F Found unique:4244 Total:16694 in 26 sec
BF CW not found. GPU Time (0 min. 24 sec.)
5F CW not found. GPU Time (0 min. 24 sec.)
DF CW not found. GPU Time (0 min. 24 sec.)
7F CW not found. GPU Time (0 min. 23 sec.)
FF CW not found. GPU Time (0 min. 23 sec.)
GPU Time on DoXRounds (3 min. 13 sec.)
Time on Search(4 min. 0 sec.)
Total Time (4 min. 40 sec.)
Please Press Exit
Done, Please Press Exit

Notice how at the end my GPU is the one consuming time 5x24=120sec
Yes 2 minutes. I hope that if I wait for every 2 threads, I could reduce the GPU time. Interesting Theory.
 
Last edited:

cayoenrique

Member
Messages
475
It seems I can not upload a file to this area. So I will have to paste. Sorry.

Using Crypt8 String: 25 C0 D1 42 1C 90 F4 13
Table B8hx00h has been selected
Exhaustive Search: Stop at 1st cw found
ECW Creation
Calc all 10000h end values for this crypt.
GPU: Time creation for 10000h end values (0 min. 39 sec.)
Using file cache: /mnt/sdc6/CSA_RBT/CSA_B8hx00h_10000h_25C0D1421C90F413.ecw
Chain Analysis
Matching ECW vs RBT Chains
Using Crypt8 String: 25 C0 D1 42 1C 90 F4 13
9F Found unique:4290 Total:17007 in 20 sec
1F Found unique:4203 Total:16731 in 28 sec
BF Found unique:4206 Total:16772 in 20 sec
1F CW not found. GPU Time (0 min. 24 sec.)
3F Found unique:4202 Total:16722 in 29 sec
DF Found unique:4274 Total:17060 in 23 sec
9F CW not found. GPU Time (0 min. 24 sec.)
FF Found unique:4227 Total:16501 in 23 sec
5F Found unique:4415 Total:17278 in 31 sec
3F CW not found. GPU Time (0 min. 24 sec.)
7F Found unique:4353 Total:17362 in 25 sec
BF CW not found. GPU Time (0 min. 24 sec.)
5F CW not found. GPU Time (0 min. 24 sec.)
DF CW not found. GPU Time (0 min. 24 sec.)
7F CW not found. GPU Time (0 min. 24 sec.)
FF CW not found. GPU Time (0 min. 24 sec.)
GPU Time on DoXRounds (3 min. 14 sec.)
Time on Search(3 min. 57 sec.)
Total Time (4 min. 37 sec.)
Please Press Exit
Done, Please Press Exit

Using Crypt8 String: 25 C0 D1 42 1C 90 F4 13
Table B8hxFFh has been selected
Exhaustive Search: Stop at 1st cw found
ECW Creation
Calc all 10000h end values for this crypt.
GPU: Time creation for 10000h end values (0 min. 39 sec.)
Using file cache: /mnt/sdc6/CSA_RBT/CSA_B8hx00h_10000h_25C0D1421C90F413.ecw
Chain Analysis
Matching ECW vs RBT Chains
Using Crypt8 String: 25 C0 D1 42 1C 90 F4 13
1F Found unique:4145 Total:14209 in 22 sec
9F Found unique:4054 Total:13930 in 22 sec
1F CW not found. GPU Time (0 min. 21 sec.)
3F Found unique:4040 Total:13671 in 22 sec
BF Found unique:4142 Total:14377 in 22 sec
9F CW not found. GPU Time (0 min. 21 sec.)
5F Found unique:4071 Total:14048 in 21 sec
DF Found unique:4061 Total:13765 in 24 sec
7F Found unique:4080 Total:13561 in 19 sec
3F CW not found. GPU Time (0 min. 21 sec.)
FF Found unique:4071 Total:13906 in 26 sec
BF CW not found. GPU Time (0 min. 23 sec.)
5F CW not found. GPU Time (0 min. 21 sec.)
DF CW not found. GPU Time (0 min. 21 sec.)
7F CW found. GPU Time (0 min. 21 sec.)
CW: 98 8A 37 59 F6 34 B8 E2
GPU Time on DoXRounds (2 min. 33 sec.)
Time on Search(2 min. 56 sec.)
Total Time (3 min. 36 sec.)
Please Press Exit
Done, Please Press Exit
---------------------------------------------------
Using Crypt8 String: FB 78 43 9A 0A 91 D3 86
Table B8hx00h has been selected
Exhaustive Search: Stop at 1st cw found
ECW Creation
Calc all 10000h end values for this crypt.
GPU: Time creation for 10000h end values (0 min. 39 sec.)
Using file cache: /mnt/sdc6/CSA_RBT/CSA_B8hx00h_10000h_FB78439A0A91D386.ecw
Chain Analysis
Matching ECW vs RBT Chains
Using Crypt8 String: FB 78 43 9A 0A 91 D3 86
9F Found unique:4253 Total:16780 in 21 sec
1F Found unique:4375 Total:17566 in 29 sec
BF Found unique:4349 Total:17185 in 20 sec
1F CW not found. GPU Time (0 min. 24 sec.)
3F Found unique:4192 Total:16667 in 30 sec
DF Found unique:4354 Total:17452 in 21 sec
9F CW not found. GPU Time (0 min. 24 sec.)
FF Found unique:4289 Total:17081 in 20 sec
5F Found unique:4230 Total:16619 in 30 sec
3F CW not found. GPU Time (0 min. 24 sec.)
7F Found unique:4291 Total:17556 in 26 sec
BF CW not found. GPU Time (0 min. 24 sec.)
5F CW not found. GPU Time (0 min. 24 sec.)
DF CW not found. GPU Time (0 min. 24 sec.)
7F CW not found. GPU Time (0 min. 24 sec.)
FF CW not found. GPU Time (0 min. 24 sec.)
GPU Time on DoXRounds (3 min. 14 sec.)
Time on Search(3 min. 58 sec.)
Total Time (4 min. 38 sec.)
Please Press Exit
Done, Please Press Exit

Using Crypt8 String: FB 78 43 9A 0A 91 D3 86
Table B8hxFFh has been selected
Exhaustive Search: Stop at 1st cw found
ECW Creation
Calc all 10000h end values for this crypt.
GPU: Time creation for 10000h end values (0 min. 39 sec.)
Using file cache: /mnt/sdc6/CSA_RBT/CSA_B8hx00h_10000h_FB78439A0A91D386.ecw
Chain Analysis
Matching ECW vs RBT Chains
Using Crypt8 String: FB 78 43 9A 0A 91 D3 86
9F Found unique:4052 Total:13787 in 22 sec
1F Found unique:4083 Total:13787 in 22 sec
1F CW not found. GPU Time (0 min. 21 sec.)
3F Found unique:4151 Total:14178 in 22 sec
BF Found unique:4122 Total:13769 in 22 sec
9F CW not found. GPU Time (0 min. 21 sec.)
DF Found unique:4028 Total:13634 in 21 sec
5F Found unique:4072 Total:13892 in 22 sec
FF Found unique:4061 Total:13739 in 21 sec
3F CW not found. GPU Time (0 min. 21 sec.)
7F Found unique:4125 Total:14034 in 22 sec
BF CW not found. GPU Time (0 min. 21 sec.)
5F CW not found. GPU Time (0 min. 21 sec.)
DF CW not found. GPU Time (0 min. 21 sec.)
7F CW not found. GPU Time (0 min. 21 sec.)
FF CW not found. GPU Time (0 min. 21 sec.)
GPU Time on DoXRounds (2 min. 53 sec.)
Time on Search(3 min. 16 sec.)
Total Time (3 min. 56 sec.)
Please Press Exit
Done, Please Press Exit

---------------------------------------------------
Using Crypt8 String: 38 B2 6E 93 84 6F 9D 9C
Table B8hx00h has been selected
for this see previous post


Using Crypt8 String: 38 B2 6E 93 84 6F 9D 9C
Table B8hxFFh has been selected
Exhaustive Search: Stop at 1st cw found
ECW Creation
Calc all 10000h end values for this crypt.
GPU: Time creation for 10000h end values (0 min. 40 sec.)
Using file cache: /mnt/sdc6/CSA_RBT/CSA_B8hx00h_10000h_38B26E93846F9D9C.ecw
Chain Analysis
Matching ECW vs RBT Chains
Using Crypt8 String: 38 B2 6E 93 84 6F 9D 9C
1F Found unique:4062 Total:13815 in 22 sec
9F Found unique:4124 Total:14279 in 22 sec
1F CW not found. GPU Time (0 min. 21 sec.)
BF Found unique:4088 Total:14044 in 22 sec
3F Found unique:4102 Total:13708 in 22 sec
9F CW not found. GPU Time (0 min. 21 sec.)
5F Found unique:4085 Total:13867 in 22 sec
DF Found unique:4119 Total:14243 in 22 sec
7F Found unique:4128 Total:13866 in 21 sec
3F CW not found. GPU Time (0 min. 21 sec.)
FF Found unique:4133 Total:14365 in 23 sec
BF CW not found. GPU Time (0 min. 21 sec.)
5F CW not found. GPU Time (0 min. 21 sec.)
DF CW not found. GPU Time (0 min. 21 sec.)
7F CW not found. GPU Time (0 min. 21 sec.)
FF CW not found. GPU Time (0 min. 23 sec.)
GPU Time on DoXRounds (2 min. 54 sec.)
Time on Search(3 min. 18 sec.)
Total Time (3 min. 58 sec.)
Please Press Exit
Done, Please Press Exit
 

C0der

Registered
Messages
267
Interesting to see how AMD GPU does compared to nVidia.
Looking at the numbers, you should be able to reduce GPU time to around 1/4 with a lot of optimization.
 

campag5242

Feed Hunter
Messages
2,585
Great job cayoenrique.

Those crypt8 I posted were for B8hxFFh - sorry I should have made that clear. They are all rare examples where the key is only found at chain links F000-FFFFh in the public tables, hence found most slowly by the public tools.
 

BLACKCRUSADER

Senior Member
Messages
1,994
@blackcrusader, these crypt8 will work your system for a little longer than those selectively chosen (favourable times) you like to post:

I didn't selectively choose anything the streams I used were for live events from Asiasat 5 that day. I just scanned when channels were not open. :) IT's not a pissing contest you can do through many of my posts in the CW threads and see how fast my system has been in the last few years.
 

BLACKCRUSADER

Senior Member
Messages
1,994
And these even harder:
FB 78 43 9A 0A 91 D3 86


Plain copy/pastes only, no mixing of table sizes v log output (post #12) or turning back time (post #24). I will be able to see if things don't add up.

Search CW Start
RBT file: D:\Biss V1 file\B8hxFFh\B8hxFFh_table2\CSA_B8hxFFh_10000h.rbt
Calc all 10000h end values for this crypt ... (using file cache)
Search end values in RBT ...
Searching CW in RBT ...
Found 216387 possible chains (harddisk only search time = 99 sec.)
 
Top