Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem running pyrit #39

Closed
GoogleCodeExporter opened this issue Sep 24, 2015 · 2 comments
Closed

Problem running pyrit #39

GoogleCodeExporter opened this issue Sep 24, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

Running:

1. pyrit -r capname.cap analyze 
2. pyrit -r capname.cap -e APNAME -b 00:de:ad:c0:de:00 attack_batch

I get:

Traceback (most recent call last):
  File "/usr/bin/pyrit", line 948, in <module>
    Pyrit_CLI().init()
  File "/usr/bin/pyrit", line 126, in init
    options, commands = getopt.getopt(sys.argv[1:], "u:v:c:e:f:")
  File "/usr/lib/python2.5/getopt.py", line 91, in getopt
    opts, args = do_shorts(opts, args[0][1:], shortopts, args[1:])
  File "/usr/lib/python2.5/getopt.py", line 191, in do_shorts
    if short_has_arg(opt, shortopts):
  File "/usr/lib/python2.5/getopt.py", line 207, in short_has_arg
    raise GetoptError('option -%s not recognized' % opt, opt)
getopt.GetoptError: option -r not recognized


Using Pyrit 0.2.3-dev on BT4. I've also installed CUDA support (with nvidia
drivers), but found out later that the video card is actually Intel. Batch
works fine on both CPU cores(250pmk/s). "delete_essid" doesn't work. Using
a wordlist with 7 mln entires and 6 essids.

Original issue reported on code.google.com by dkaloya...@gmail.com on 31 Aug 2009 at 11:36

@GoogleCodeExporter
Copy link
Author

The attack-functions are supported since 0.2.4

Update your installation

Original comment by lukas.l...@gmail.com on 31 Aug 2009 at 11:57

  • Changed state: Invalid

@GoogleCodeExporter
Copy link
Author

After updating following your instructions in the wiki, everything works like a
charm. Sorry to have wasted your time, but your comment was invaluable in 
solving
this problem. Thank you for the hard work!

Original comment by dkaloya...@gmail.com on 31 Aug 2009 at 1:57

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant