What steps will reproduce the problem?
1.
update snv vers
2.
jacob@lappy:~/svn/pyrit_svn$ pyrit -u postgres://pyrit:@127.0.0.1/pyrit -f
/home/jacob/wordlist/1 import_passwords
Traceback (most recent call last):
File "/usr/local/bin/pyrit", line 6, in <module>
pyrit_cli.Pyrit_CLI().initFromArgv()
File "/usr/local/lib/python2.6/dist-packages/pyrit_cli.py", line 62, in
initFromArgv
args, commands = getopt.getopt(sys.argv[1:], 'u:v:c:e:i:o:r:b:')
File "/usr/lib/python2.6/getopt.py", line 91, in getopt
opts, args = do_shorts(opts, args[0][1:], shortopts, args[1:])
File "/usr/lib/python2.6/getopt.py", line 191, in do_shorts
if short_has_arg(opt, shortopts):
File "/usr/lib/python2.6/getopt.py", line 207, in short_has_arg
raise GetoptError('option -%s not recognized' % opt, opt)
getopt.GetoptError: option -f not recognized
jacob@lappy:~/svn/pyrit_svn$
3.jacob@lappy:~/svn/pyrit_svn$ pyrit -f /home/jacob/wordlist/1
import_passwordsTraceback (most recent call last):
File "/usr/local/bin/pyrit", line 6, in <module>
pyrit_cli.Pyrit_CLI().initFromArgv()
File "/usr/local/lib/python2.6/dist-packages/pyrit_cli.py", line 62, in
initFromArgv
args, commands = getopt.getopt(sys.argv[1:], 'u:v:c:e:i:o:r:b:')
File "/usr/lib/python2.6/getopt.py", line 91, in getopt
opts, args = do_shorts(opts, args[0][1:], shortopts, args[1:])
File "/usr/lib/python2.6/getopt.py", line 191, in do_shorts
if short_has_arg(opt, shortopts):
File "/usr/lib/python2.6/getopt.py", line 207, in short_has_arg
raise GetoptError('option -%s not recognized' % opt, opt)
getopt.GetoptError: option -f not recognized
jacob@lappy:~/svn/pyrit_svn$
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
svn 187
Please provide any additional information below.
Computed 1964.32 PMKs/s total.
#1: 'CUDA-Device #1 'GeForce 8700M GT'': 1537.4 PMKs/s (Occ. 98.1%; RTT 2.9)
#2: 'CPU-Core (SSE2)': 464.8 PMKs/s (Occ. 98.0%; RTT 2.6)
:)
Original issue reported on code.google.com by cha...@gmail.com on 19 Oct 2009 at 7:26
Original issue reported on code.google.com by
cha...@gmail.com
on 19 Oct 2009 at 7:26