Encryption Projects as SU group
- Thread starter cayoenrique
- Start date
Sunrise999
Registered
- Messages
- 155
Being your testing is at top level did or can run more than 1 instance at a time .CW Finder 1.0
The search using BF (without cw list)
Options > Set Process Priority > Highest
Options > Set Search Thread Priority > Highest
I ran the search for exactly 1 minute and got this result:
This means for 1 minute
Presence of encrypted .ts file on SSD means nothing to this kind of search.
- achieved speed is 4,641,296 CW/s (4.641 MKPS) in this app
- this app checked 278,477,776 keys
- and got from 00 00 00 00 00 00 to 00 00 10 B6 90 E0.
- The remaining time to perform full search is 01 years 11 months 6 days 22 hours 01 minute and 51 seconds.
My PC is an older rig running on Win10 64bit, nothing exceptional nowadays:
- CPU AMD Ryzen 9 3950x
- RAM KINGSTON HyperX Fury RGB 32 GB (2x16 GB) DDR4 3466 MHz CL16
- SSD PCIe 4.0 M.2 NVMe Gen4 Aorus Gigabyte
I did not see this post, was it deleted? doesn;'t Cwfinder only use cpu? open the task manager check if its using all cores and threads.
Is there a source code? the processing needs to be moved to gpu like with cudabiss. Or something like https://github.com/HigherOrderCO/Bend
Is there a source code? the processing needs to be moved to gpu like with cudabiss. Or something like https://github.com/HigherOrderCO/Bend
Sunrise999
Registered
- Messages
- 155
Post 4 in this thread has a screen shot. in cw finder thread download is there.
My cpu was showing 5.56 so try your luck seem a bit slow .
My cpu was showing 5.56 so try your luck seem a bit slow .
Sunrise999
Registered
- Messages
- 155
With all the help think best to not bother with even trying this app.
The truth cuda biss is the best public app. out there.
The truth cuda biss is the best public app. out there.
orangebirds
Well Known Member
- Messages
- 2,246
Hi! recently I got a new laptop with RTX 4060
I got to day the difference between CudaBiss12_3_VS22_4xxx.exe and Cudabiss102464.exe is significant in my case with the former took 2668088576 keys/s and the latter took 1766839424 keys/s on one instance
i don't have any other version that is recently compiled other than that...
Also, anybody know how to make cudabiss run into random mode instead of sequential searching? thanks!
I got to day the difference between CudaBiss12_3_VS22_4xxx.exe and Cudabiss102464.exe is significant in my case with the former took 2668088576 keys/s and the latter took 1766839424 keys/s on one instance
i don't have any other version that is recently compiled other than that...
Also, anybody know how to make cudabiss run into random mode instead of sequential searching? thanks!
ViaHussun
Donating Member
- Messages
- 4,119
GitHub - aycwabtu/aycwabtu: AYCWABTU is a brute force control word calculation tool for the DVB common scrambling algorithm (csa) that finds keys in encrypted transport streams
AYCWABTU is a brute force control word calculation tool for the DVB common scrambling algorithm (csa) that finds keys in encrypted transport streams - aycwabtu/aycwabtu
github.com
Has anyone tried this application?
How can I run it in windows?
Sunrise999
Registered
- Messages
- 155
Maybe Windows Subsystem for Linux Google is your friend .
orangebirds
Well Known Member
- Messages
- 2,246
Or maybe a reverse mode (from FF FF FF - 00 00 00)...
It's been a few months, was wondering if any progress was made?
klickklack
Donating Member
- Messages
- 2,117
tu-wien
3.3.1 Existing Implementations Markus Diett [3] implemented a brute-force approach in software as well as in hardware. The software implementation could test approximately 784000 keys per second, which could iterate the entire 2 48 key space in approximately 4155 days. Note that these results are of course hardware specific, but unfortunately Diett did not elaborate on the testing system specifications. The hardware implementation on the Copacobana [6] could operate in two different frequencies (96 MHz and 108 MHz) with each of the 120 FPGAs testing a key in 4 clock cycles. This brings the rate of the hardware implementation to 2.88 ∗ 109 with 96 MHz and 3.24 ∗ 109 with 108MHz. The 2 48 key space could be searched in approximately 27.15 hours with 96 MHz and 24.13 hours with 108 MHz. There also exists another software based brute-force implementation called AYCWABTU [8] that is also based on the bit splice method as in the implementation of Diett [3]. It was implemented as a proof of concept that a brute-force attack on the DVB CSA is indeed possible. On a computer equipped with an Intel i5 3337U (1.80- 2.70 GHz) running on Debian 8, a rate of approximately 4000000 keys per second was achieved. The entire 2 48 key space could be iterated in approximately 814 days.
3.3.1 Existing Implementations
Markus Diett [3] implemented a brute-force approach in software as well as in hardware. The software
implementation could test approximately 784000 keys per second, which could iterate the entire 2
48 key space
in approximately 4155 days. Note that these results are of course hardware specific, but unfortunately Diett did
not elaborate on the testing system specifications. The hardware implementation on the Copacobana [6] could
operate in two different frequencies (96 MHz and 108 MHz) with each of the 120 FPGAs testing a key in 4 clock
cycles. This brings the rate of the hardware implementation to 2.88 ∗ 109 with 96 MHz and 3.24 ∗ 109 with 108
MHz. The 2
48 key space could be searched in approximately 27.15 hours with 96 MHz and 24.13 hours with
108 MHz.
There also exists another software based brute-force implementation called AYCWABTU [8] that is also based
on the bit splice method as in the implementation of Diett [3]. It was implemented as a proof of concept that a
brute-force attack on the DVB CSA is indeed possible. On a computer equipped with an Intel i5 3337U (1.80-
2.70 GHz) running on Debian 8, a rate of approximately 4000000 keys per second was achieved. The entire 2
48
key space could be iterated in approximately 814 days.
Table 5.4: Worst case execution time of CUDABISS 2.5 for different GPUs.
GPU Brute-force Key Rate (k/s) Time to iterate 2
48 key space
NVidia GTX 570 166 ∗ 106 471h 1m
NVidia GTX 980 Ti 465 ∗ 106 168h 9m
this i posted twice-time.
3.3.1 Existing Implementations Markus Diett [3] implemented a brute-force approach in software as well as in hardware. The software implementation could test approximately 784000 keys per second, which could iterate the entire 2 48 key space in approximately 4155 days. Note that these results are of course hardware specific, but unfortunately Diett did not elaborate on the testing system specifications. The hardware implementation on the Copacobana [6] could operate in two different frequencies (96 MHz and 108 MHz) with each of the 120 FPGAs testing a key in 4 clock cycles. This brings the rate of the hardware implementation to 2.88 ∗ 109 with 96 MHz and 3.24 ∗ 109 with 108MHz. The 2 48 key space could be searched in approximately 27.15 hours with 96 MHz and 24.13 hours with 108 MHz. There also exists another software based brute-force implementation called AYCWABTU [8] that is also based on the bit splice method as in the implementation of Diett [3]. It was implemented as a proof of concept that a brute-force attack on the DVB CSA is indeed possible. On a computer equipped with an Intel i5 3337U (1.80- 2.70 GHz) running on Debian 8, a rate of approximately 4000000 keys per second was achieved. The entire 2 48 key space could be iterated in approximately 814 days.
3.3.1 Existing Implementations
Markus Diett [3] implemented a brute-force approach in software as well as in hardware. The software
implementation could test approximately 784000 keys per second, which could iterate the entire 2
48 key space
in approximately 4155 days. Note that these results are of course hardware specific, but unfortunately Diett did
not elaborate on the testing system specifications. The hardware implementation on the Copacobana [6] could
operate in two different frequencies (96 MHz and 108 MHz) with each of the 120 FPGAs testing a key in 4 clock
cycles. This brings the rate of the hardware implementation to 2.88 ∗ 109 with 96 MHz and 3.24 ∗ 109 with 108
MHz. The 2
48 key space could be searched in approximately 27.15 hours with 96 MHz and 24.13 hours with
108 MHz.
There also exists another software based brute-force implementation called AYCWABTU [8] that is also based
on the bit splice method as in the implementation of Diett [3]. It was implemented as a proof of concept that a
brute-force attack on the DVB CSA is indeed possible. On a computer equipped with an Intel i5 3337U (1.80-
2.70 GHz) running on Debian 8, a rate of approximately 4000000 keys per second was achieved. The entire 2
48
key space could be iterated in approximately 814 days.
Table 5.4: Worst case execution time of CUDABISS 2.5 for different GPUs.
GPU Brute-force Key Rate (k/s) Time to iterate 2
48 key space
NVidia GTX 570 166 ∗ 106 471h 1m
NVidia GTX 980 Ti 465 ∗ 106 168h 9m
this i posted twice-time.