http403 / pyrit

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

Enter one-line summary #136

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. pyrit batch
2.
3.

What is the expected output? What do you see instead?
Expected: creation of PMKs
Instead: 
root@bt:~# pyrit batch
Pyrit 0.3.1-dev (svn r228) (C) 2008-2010 Lukas Lueg http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3+

Connecting to storage at 'file://'...  connected.
Working on ESSID 'FRITZ!Box Fon WLAN 7141'
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.5/site-packages/cpyrit/cpyrit.py", line 114, in run
    res = self.solve(essid, pwlist)
SystemError: CUDA_ERROR_LAUNCH_TIMEOUT

Exception in thread Thread-2:
Traceback (most recent call last):
  File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.5/site-packages/cpyrit/cpyrit.py", line 108, in run
    essid, pwlist = self.queue._gather(self.buffersize, timeout=0.5)
  File "/usr/lib/python2.5/site-packages/cpyrit/cpyrit.py", line 552, in
_gather
    self._check_cores()
  File "/usr/lib/python2.5/site-packages/cpyrit/cpyrit.py", line 410, in
_check_cores
    raise SystemError("The core '%s' has died unexpectedly" % core)
SystemError: The core 'CUDA-Device #1 'Quadro NVS 135M'' has died unexpectedly

Traceback (most recent call last):
  File "/usr/bin/pyrit", line 6, in <module>
    pyrit_cli.Pyrit_CLI().initFromArgv()
  File "/usr/lib/python2.5/site-packages/pyrit_cli.py", line 106, in
initFromArgv
    func(self, **options)
  File "/usr/lib/python2.5/site-packages/pyrit_cli.py", line 574, in
batchprocess
    for results in dbiterator:
  File "/usr/lib/python2.5/site-packages/cpyrit/util.py", line 141, in next
    self.cp.enqueue(self.essid, passwords)
  File "/usr/lib/python2.5/site-packages/cpyrit/cpyrit.py", line 484, in
enqueue
    self._check_cores()
  File "/usr/lib/python2.5/site-packages/cpyrit/cpyrit.py", line 410, in
_check_cores
    raise SystemError("The core '%s' has died unexpectedly" % core)
SystemError: The core 'CUDA-Device #1 'Quadro NVS 135M'' has died unexpectedly

What version of the product are you using? On what operating system?
Pyrit 0.3.1-dev (svn r228) / pyrit-cuda 0.3.1 
Backtrack 4 Final (Ubuntu 8.10)
Nvidia Backtrack Driver Package 190.18
Core2Duo Mobile 2x2,20Ghz 

#1:  'CUDA-Device #1 'Quadro NVS 135M''
#2:  'CPU-Core (SSE2)'

Please provide any additional information below.

When I run "pyrit batch" within a TTY so without starting X-Server/KDE it
works fine.

Whats also strange is that since I installed the NVidia Drivers I only see
one Core instead of two Cores which I had seen before.

Thanks for your help in advance.

Best regards,
Flow

Original issue reported on code.google.com by flow.off...@googlemail.com on 6 Apr 2010 at 4:52

GoogleCodeExporter commented 9 years ago
The NVS 135M is just too slow. The call by Pyrit is interrupted by X to prevent 
the
screen from locking up completely. There is no solution :-)

Please see the FAQ regarding the number of cores.

Original comment by lukas.l...@gmail.com on 6 Apr 2010 at 5:09

GoogleCodeExporter commented 9 years ago
OK I checked FAQ ;) Thanks!

Is it really that slow? It runs with 1400PMK/s for a onboard card still fast in 
TTY 
;)
So it is too slow to handle both X and Pyrit and the X-Server does recognize 
this?!
I did not know that XServer ist that intelligent ;)

Might there be any workaround?

Thanks for the fast answer ;)

Best regards,
Flow

Original comment by flow.off...@googlemail.com on 7 Apr 2010 at 12:23

GoogleCodeExporter commented 9 years ago
its actually not the X server but the driver itself. The driver detects the 
running
X-Server and enforces a five-second-timeout.

You can edit cpyrit/cpyrit.py, modify the line "self.buffersize = 4096" in
CUDACore.__init__ and set it to a lower value (e.g. 2048)

Original comment by lukas.l...@gmail.com on 7 Apr 2010 at 4:59

GoogleCodeExporter commented 9 years ago
are you really getting 1400 PMK/s with that card?

i have that card and im not even getting a quarter of that amount...similiar 
spec cpu
as well

Original comment by psychona...@gmail.com on 24 Apr 2010 at 7:20