search

http403 / pyrit

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

Cowpatty Max Hash file size #21

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I have created a large Cowpatty Hash file (4.2gb) and unfortunately 
Cowpatty is unable to read this (I get the error message "could not stat 
Hashfile"). I have found this is because the 32bit file limit is about 2gb 
and unless I upgrade to 64bit I will be unable to use the file.

Would it be possible to add an option to limit the Hash file size of 2gb 
and then create an additional Hashfiles? eg: Hash_1 Hash_2 Hash_3 etc?

Original issue reported on code.google.com by john.cob...@googlemail.com on 27 Jul 2009 at 2:59

GoogleCodeExporter commented 9 years ago 
Which version of cowpatty do you use?

Original comment by lukas.l...@gmail.com on 27 Jul 2009 at 3:38

GoogleCodeExporter commented 9 years ago 
cowpatty 4.6

Original comment by john.cob...@googlemail.com on 27 Jul 2009 at 4:38

GoogleCodeExporter commented 9 years ago 
O/S: Ubuntu 8.04
Kernel: Linux pc 2.6.24-24-generic #1 SMP Tue Jul 7 19:46:39 UTC 2009 i686 
GNU/Linux

Original comment by john.cob...@googlemail.com on 27 Jul 2009 at 4:41

GoogleCodeExporter commented 9 years ago 
OK I've checked this. Cowpatty should not use stat() to check the file's 
existence -
especially on systems that don't define EOVERFLOW.

For the moment you can use piping to circumvent this problem 'cat bigfile.cow |
cowpatty -d - -r whatever.cap -s whatever'

Original comment by lukas.l...@gmail.com on 27 Jul 2009 at 5:03

GoogleCodeExporter commented 9 years ago 
Oh I forgot: You don't need the intermediate cowpatty-file. Just run 
batchprocess and
pipe it directly into cowpatty - all the results will come from the disk:

'pyrit -e whatever -f - batch | cowpatty -d - -r whatever.cap -s whatever'

Original comment by lukas.l...@gmail.com on 27 Jul 2009 at 8:26

GoogleCodeExporter commented 9 years ago 
I've informed cowpatty's author about this problem. We can't fix this in Pyrit.
Please refer to comment #5 for the time being :)

Original comment by lukas.l...@gmail.com on 8 Aug 2009 at 9:14