http403 / pyrit

Automatically exported from code.google.com/p/pyrit
0 stars 0 forks source link

new feature request: sort database #73

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
This is a request of new feature, not a bug report.

after I create database with pyrit batch, I can attack database with
pyrit -r captured.cap attack_db.
But the problem is that attack is a SEQUENTIAL attack: in a database with
2^30 hash, if I am unlucky, I must wait till last hash to be tested.

here my 2 cent:
It will be nice to export a database sorted in function of hash: (ie: pyrit
-f my_sorted_db.cow export_cowpatty_sorted) in this way, a simple script
can interrogate the exported file with at maximun 30 test and not 2^30.
Of course sort can need long time but sort could be exeguted by GPU, maybe.

maybe this can help http://en.wikipedia.org/wiki/Sorting_algorithm

Original issue reported on code.google.com by pyrit.lo...@gmail.com on 20 Nov 2009 at 9:38

GoogleCodeExporter commented 9 years ago
I don't get why sorting should be of any use....

Original comment by lukas.l...@gmail.com on 21 Nov 2009 at 11:56

GoogleCodeExporter commented 9 years ago
pyrit attack_db read about (on my system) 400000 k/s.
Im building a database that at the end will be 150 Billion of hash. Datasase 
will be
free to be read several rimes, but in worst case every attack_db need 150
Billion/400000 k/s = 4days. Export in sorted mode will reduce 4 days to few 
minutes.

Original comment by pyrit.lo...@gmail.com on 21 Nov 2009 at 8:59

GoogleCodeExporter commented 9 years ago
The basic assumption Pyrit is working with is that all attack modes that read 
PMKs
from the database are only limited by the harddrive's ability to read that fast
(400.000 PMKs/s = 14mb/s).

For such huge installations you should write a new attack script that resembles
attack_db yourself. Take a look at how the original 'attack_db'-function is
implemented in pyrit_cli.py. You'll find that it uses util.StorageIterator 
which you
want to rewrite so you can save a list of keys (keys to workunits) which you 
already
tested. In case you re-run a attack, you can skip keys that already got tested.

I'll currently not act on this ;-)

Original comment by lukas.l...@gmail.com on 22 Nov 2009 at 4:19