Pyrit throws various errors, fails benchmarks, throws exceptions then quits

[GoogleCodeExporter]

What steps will reproduce the problem?
1.

Use this how-to for installing a pyrit-friendly environment on a macbook pro: 
http://console-cowboys.blogspot.com/2011/01/setting-up-pyrit-on-osx.html

2.
Once installation is complete, run the two following commands:
pyrit list_cores

pyrit benchmark

bash-3.2# pyrit list_cores
/Library/Python/2.6/site-packages/cpyrit/cpyrit.py:63: UserWarning: WARNING: 
Version mismatch between <module 'cpyrit._cpyrit_cpu' from 
'/Library/Python/2.6/site-packages/cpyrit/_cpyrit_cpu.so'> ('0.4.1-dev (svn 
r299)') and <module 'cpyrit._cpyrit_cuda' from 
'/Library/Python/2.6/site-packages/cpyrit/_cpyrit_cuda.so'> ('0.3.0')

  "('%s')\n" % (_cpyrit_cpu, _cpyrit_cpu.VERSION, mod, ver))
Pyrit 0.4.1-dev (svn r299) (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3+

The following cores seem available...
#1:  'CUDA-Device #1 'GeForce GT 330M''
#2:  'CPU-Core (SSE2)'
#3:  'CPU-Core (SSE2)'
#4:  'CPU-Core (SSE2)'
#5:  'Network-Clients'

bash-3.2# pyrit benchmark
/Library/Python/2.6/site-packages/cpyrit/cpyrit.py:63: UserWarning: WARNING: 
Version mismatch between <module 'cpyrit._cpyrit_cpu' from 
'/Library/Python/2.6/site-packages/cpyrit/_cpyrit_cpu.so'> ('0.4.1-dev (svn 
r299)') and <module 'cpyrit._cpyrit_cuda' from 
'/Library/Python/2.6/site-packages/cpyrit/_cpyrit_cuda.so'> ('0.3.0')

  "('%s')\n" % (_cpyrit_cpu, _cpyrit_cpu.VERSION, mod, ver))
Pyrit 0.4.1-dev (svn r299) (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3+

Calibrating... Exception in thread CUDA-Device #1 'GeForce GT 330M':
Traceback (most recent call last):
  File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/threading.py", line 522, in __bootstrap_inner
    self.run()
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 113, in run
    self._testComputeFunction(101)
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 103, in _testComputeFunction
    raise ValueError("Test-vector does not result in correct PMK.")
ValueError: Test-vector does not result in correct PMK.

Traceback (most recent call last):
  File "/usr/local/bin/pyrit", line 6, in <module>
    pyrit_cli.Pyrit_CLI().initFromArgv()
  File "/Library/Python/2.6/site-packages/pyrit_cli.py", line 115, in initFromArgv
    func(self, **options)
  File "/Library/Python/2.6/site-packages/pyrit_cli.py", line 1172, in benchmark
    cp.enqueue('foo', ['barbarbar'] * 500)
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 564, in enqueue
    self._check_cores()
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 490, in _check_cores
    raise SystemError("The core '%s' has died unexpectedly" % core)
SystemError: The core 'CUDA-Device #1 'GeForce GT 330M'' has died unexpectedly

3.

What is the expected output? What do you see instead?

I expect pyrit to run a benchmark and not throw errors. It appears as though 
having an old version (which also had errors, but its been quite some time 
since I last touched it) is interfering with this new installation. It would be 
neat if the new installs would either move, or blow away the old libs to avoid 
these errors (but I admit there might be more going on that I'm not seeing, so 
this is speculation)

What version of the product are you using? On what operating system?

pyrit 0.4.1-dev on osx 10.6.7, macbook pro quad core i7 17"

Please provide any additional information below.
Please feel free to have me try stuff, I'll be as useful as I can to try and 
find a solution! I'm excited to have GPU based cracking on my mac!

Original issue reported on code.google.com by viss...@gmail.com on 1 Apr 2011 at 9:37

[GoogleCodeExporter]

I was able to resolve this by removing the offending .so files and reinstalling 
pyrit

Original comment by viss...@gmail.com on 6 Apr 2011 at 8:02

[GoogleCodeExporter]

Original comment by lukas.l...@gmail.com on 7 Apr 2011 at 8:45

• Changed state: WontFix