New Pyrit Features

[purehate]

I am putting this in general IT because I am not ready to add this version of pyrit to the .iso. ebfe has released a stable 2.3 and I have added that to the repository for now.

Pyrit has some exciting new features in svn. there is no longer any need for cowpatty. Pyrit can crack the hash's on its own. To check out this new feature you will need to compile pyrit and cpyrit your self from svn source.

kracker ~ # pyrit
WARNING: IPv6 support disabled in Python. Cannot load scapy IPv6 layers.
Pyrit 0.2.4-dev (svn r146) (C) 2008, 2009 Lukas Lueg http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3

Usage: pyrit [options] command

Recognized options:
  -e    : ESSID
  -b    : BSSID
  -f    : filename for input/output ('-' is stdin/stdout)
  -r    : packet capture file in pcap format

Recognized commands:
  analyze            : Analyze a packet-capture file
  attack_db          : Attack a handshake with PMKs from the db
  attack_batch       : Attack a handshake with PMKs/passwords from the db
  attack_passthrough : Attack a handshake with passwords from a file
  batch              : Batchprocess the database
  benchmark          : Determine performance of available cores
  create_essid       : Create a new ESSID
  delete_essid       : Delete a ESSID and corresponding results
  eval               : Count the available passwords and matching results
  export_cowpatty    : Export results to a new cowpatty file
  export_hashdb      : Export results to an airolib database
  export_passwords   : Export passwords to a file
  import_passwords   : Import passwords from a file
  list_cores         : List available cores
  list_essids        : List all ESSIDs but don't count matching results
  passthrough        : Compute PMKs on the fly and write to stdout
  selftest           : Test all cores to ensure they compute correct results
  verify             : Verify 10% of the results by recomputation

[Nemis]

I have added that to the repository for now.

i see 0.2.3.bt0 on apt-get or synaptic

[kidFromBigD]

i see 0.2.3.bt0 on apt-get or synaptic

What am I missing? Isn't that EXACTLY what pureh@te said? If you upgrade from repo, count on getting 0.2.3 - right?

Then he went on to say getting 0.2.4-dev means you upgrade from svn, which means you're on your own.

[Nemis]

What am I missing? Isn't that EXACTLY what pureh@te said? If you upgrade from repo, count on getting 0.2.3 - right?

Then he went on to say getting 0.2.4-dev means you upgrade from svn, which means you're on your own.

sorry my bad english, read i 'have added that' . i have thought 'that' was 0.2.4 .

so error when compile svn by
gcc -lcuda

[kidFromBigD]

For all the BT4pf users out there, note that scapy (/usr/bin/scapy) needs to be upgraded to version 2+ for the newest pyrit stuff to work. Spent about an hour fussing over this, some hopefully you don't have to. As pureh@te has said many times before: If you install from repo, you should be safe. But if you're daring, installing pyrit from svn 'forks' your BT4pf system and future repo installs may break stuff. Caveat Emptor.

Anyway, onto the steps(Found this link with some Google 'Fu: Download and Installation — Scapy v2.0.1 documentation )

Perform these steps as root on your box:

$ cd /tmp
$ wget scapy.net
$ unzip scapy-latest.zip
$ cd scapy-2.*
$ sudo python setup.py install

Once installed, pyrit r146+ is happy with scapy 2.0.1 and you're flying high again.

[Nemis]

For all the BT4pf users out there, note that scapy (/usr/bin/scapy) needs to be upgraded to version 2+ for the newest pyrit stuff to work. Spent about ....

Once installed, pyrit r146+ is happy with scapy 2.0.1 and you're flying high again.

ok i have pyrit 0.2.5 from svn but if i compile cpyrit_cuda (for nvidia gpu) i have error :

root@BackTrack:/pentest/wireless/pyrit_svn/cpyrit_cuda# python setup.py build
running build
running build_ext
Compiling CUDA module using nvcc 2.2, V0.2.1221...
ptxas info : Compiling entry function 'cuda_pmk_kernel'
ptxas info : Used 42 registers, 24+20 bytes smem, 12 bytes cmem[1]
Building modules...
building 'cpyrit._cpyrit_cuda' extension
creating build
creating build/temp.linux-i686-2.5
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/opt/cuda/include -I/usr/include/python2.5 -c _cpyrit_cuda.c -o build/temp.linux-i686-2.5/_cpyrit_cuda.o -DVERSION="0.2.5-dev (svn r169)"
creating build/lib.linux-i686-2.5
creating build/lib.linux-i686-2.5/cpyrit
gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions build/temp.linux-i686-2.5/_cpyrit_cuda.o -lssl -lcuda -lz -o build/lib.linux-i686-2.5/cpyrit/_cpyrit_cuda.so
/usr/bin/ld: cannot find -lcuda
collect2: ld returned 1 exit status
error: command 'gcc' failed with exit status 1

[kidFromBigD]

I feel your pain. Best bet may be to submit this error directly to the pyrit googlecode page. The author will have pity and try to help - at least that's been my experience.

Try here: Troubleshooting - pyrit - FAQ and troubleshooting - Project Hosting on Google Code

Best of luck. Report back if/when you get a solution.

[Nemis]

fixed with :
"sudo ln -s /usr/lib/libcuda.so.1 /usr/lib/libcuda.so"

found here aur.archlinux.org/packages.php?ID=19844&O=&L=&C=&K=&SB=&SO=&PP=&do_O rphans=&SeB=