[Python-apps-commits] r5637 - in packages/pyrit/trunk (19 files)
chrisk-guest at users.alioth.debian.org
chrisk-guest at users.alioth.debian.org
Fri Jun 18 18:22:03 UTC 2010
Date: Friday, June 18, 2010 @ 18:21:54
Author: chrisk-guest
Revision: 5637
[svn-inject] Applying Debian modifications (0.3.0-1) to trunk
Added:
packages/pyrit/trunk/debian/
packages/pyrit/trunk/debian/README.Debian
packages/pyrit/trunk/debian/changelog
packages/pyrit/trunk/debian/compat
packages/pyrit/trunk/debian/control
packages/pyrit/trunk/debian/copyright
packages/pyrit/trunk/debian/docs
packages/pyrit/trunk/debian/manpages
packages/pyrit/trunk/debian/patches/
packages/pyrit/trunk/debian/patches/0001-Add-OpenSSL-linking-exception-from-upstream.patch
packages/pyrit/trunk/debian/patches/0002-Clean-up-after-unit-tests.patch
packages/pyrit/trunk/debian/patches/0003-Add-man-page-for-pyrit-1.patch
packages/pyrit/trunk/debian/patches/0004-Fixed-depreciation-warning-generated-by-sql-alchemy.patch
packages/pyrit/trunk/debian/patches/series
packages/pyrit/trunk/debian/pyversions
packages/pyrit/trunk/debian/rules
packages/pyrit/trunk/debian/source/
packages/pyrit/trunk/debian/source/format
packages/pyrit/trunk/debian/watch
Property changes on: packages/pyrit/trunk/debian
___________________________________________________________________
Added: mergeWithUpstream
+ 1
Added: packages/pyrit/trunk/debian/README.Debian
===================================================================
--- packages/pyrit/trunk/debian/README.Debian (rev 0)
+++ packages/pyrit/trunk/debian/README.Debian 2010-06-18 18:21:54 UTC (rev 5637)
@@ -0,0 +1,18 @@
+pyrit for Debian
+----------------
+
+Pyrit consists of a standalone application and optional extensions for various
+GPGPU-technologies.
+
+This package provides the full-featured application which should run on
+any x86- or x86-64-based system with SSE2 support. python-scapy and
+python-sqlalchemy (as well as a backend, eg python-sqlite) aren't strictly
+required, but you really want them if you're only going to use a Pyrit on a
+single node.
+
+Depending on what Debian version you are using, the optional extensions might be
+available as packages in the contrib section. These should be named "pyrit-*".
+If your system does not have these packages, you may want to get them directly
+from upstream's homepage.
+
+ -- Christian Kastner <debian at kvr.at> Wed, 19 May 2010 23:25:37 +0200
Added: packages/pyrit/trunk/debian/changelog
===================================================================
--- packages/pyrit/trunk/debian/changelog (rev 0)
+++ packages/pyrit/trunk/debian/changelog 2010-06-18 18:21:54 UTC (rev 5637)
@@ -0,0 +1,10 @@
+pyrit (0.3.0-1) unstable; urgency=low
+
+ * Initial release (Closes: #570918)
+ * debian/patches:
+ - 0001-Add-OpenSSL-linking-exception-from-upstream
+ - 0002-Clean-up-after-unit-tests
+ - 0003-Add-man-page-for-pyrit-1
+ - 0004-Fixed-depreciation-warning-generated-by-sql-alchemy
+
+ -- Christian Kastner <debian at kvr.at> Thu, 20 May 2010 14:43:26 +0200
Added: packages/pyrit/trunk/debian/compat
===================================================================
--- packages/pyrit/trunk/debian/compat (rev 0)
+++ packages/pyrit/trunk/debian/compat 2010-06-18 18:21:54 UTC (rev 5637)
@@ -0,0 +1 @@
+7
Added: packages/pyrit/trunk/debian/control
===================================================================
--- packages/pyrit/trunk/debian/control (rev 0)
+++ packages/pyrit/trunk/debian/control 2010-06-18 18:21:54 UTC (rev 5637)
@@ -0,0 +1,37 @@
+Source: pyrit
+Section: net
+Priority: optional
+Maintainer: Python Applications Packaging Team <python-apps-team at lists.alioth.debian.org>
+Uploaders: Christian Kastner <debian at kvr.at>
+Build-Depends:
+ debhelper (>= 7.0.50~),
+ python-all-dev (>= 2.5),
+ python-support (>= 0.90),
+ python-scapy,
+ python-sqlalchemy (>= 0.6.1),
+ python-sqlite,
+ libssl-dev
+Standards-Version: 3.8.4
+Homepage: http://code.google.com/p/pyrit/
+Vcs-Svn: svn://svn.debian.org/python-apps/packages/pyrit/trunk/
+Vcs-Browser: http://svn.debian.org/viewsvn/python-apps/packages/pyrit/trunk/
+
+Package: pyrit
+Architecture: i386 amd64
+Depends:
+ ${python:Depends},
+ ${misc:Depends},
+ ${shlibs:Depends}
+Recommends:
+ python-scapy,
+ python-sqlalchemy (>= 0.6.1),
+ python-sqlite | python-psycopg2 | python-pymssql | python-mysqldb
+Description: A GPGPU-driven WPA/WPA2-PSK key cracker
+ Pyrit allows to create massive databases, pre-computing part of the
+ WPA/WPA2-PSK authentication phase in a space-time-tradeoff. Exploiting the
+ computational power of Many-Core- and other platforms through ATI-Stream,
+ Nvidia CUDA, OpenCL and VIA Padlock, it is currently by far the most powerful
+ attack against one of the world's most used security-protocols.
+ .
+ This package contains the basic version of pyrit. Support for non-free
+ technologies such as CUDA can be added through extensions.
Added: packages/pyrit/trunk/debian/copyright
===================================================================
--- packages/pyrit/trunk/debian/copyright (rev 0)
+++ packages/pyrit/trunk/debian/copyright 2010-06-18 18:21:54 UTC (rev 5637)
@@ -0,0 +1,58 @@
+Format-Specification: http://svn.debian.org/wsvn/dep/web/deps/dep5.mdwn?op=file&rev=135
+Name: Pyrit
+Maintainer: Lukas Lueg <lukas.lueg at gmail.com>
+Source: http://code.google.com/p/pyrit/
+
+Copyright: 2008-2010, Lukas Lueg <lukas.lueg at gmail.com>
+License: GPL-3+
+ This package is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 3 of the License, or
+ (at your option) any later version.
+ .
+ This package is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+ .
+ You should have received a copy of the GNU General Public License
+ along with this package; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
+ .
+ Additional permission under GNU GPL version 3 section 7
+ .
+ OpenSSL linking exception
+ --------------------------
+ If you modify this Program, or any covered work, by linking or
+ combining it with the OpenSSL project's "OpenSSL" library (or a
+ modified version of that library), containing parts covered by
+ the terms of OpenSSL/SSLeay license, the licensors of this
+ Program grant you additional permission to convey the resulting
+ work. Corresponding Source for a non-source form of such a
+ combination shall include the source code for the parts of the
+ OpenSSL library used as well as that of the covered work.
+ .
+ On Debian systems, the complete text of the GNU General
+ Public License version 3 can be found in
+ `/usr/share/common-licenses/GPL-3'.
+
+Files: debian/*
+Copyright: 2010, Christian Kastner <debian at kvr.at>
+License: GPL-3+
+ This package is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 3 of the License, or
+ (at your option) any later version.
+ .
+ This package is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+ .
+ You should have received a copy of the GNU General Public License
+ along with this package; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
+ .
+ On Debian systems, the complete text of the GNU General
+ Public License version 3 can be found in
+ `/usr/share/common-licenses/GPL-3'.
Added: packages/pyrit/trunk/debian/docs
===================================================================
--- packages/pyrit/trunk/debian/docs (rev 0)
+++ packages/pyrit/trunk/debian/docs 2010-06-18 18:21:54 UTC (rev 5637)
@@ -0,0 +1 @@
+README
Added: packages/pyrit/trunk/debian/manpages
===================================================================
--- packages/pyrit/trunk/debian/manpages (rev 0)
+++ packages/pyrit/trunk/debian/manpages 2010-06-18 18:21:54 UTC (rev 5637)
@@ -0,0 +1 @@
+pyrit.1
Added: packages/pyrit/trunk/debian/patches/0001-Add-OpenSSL-linking-exception-from-upstream.patch
===================================================================
--- packages/pyrit/trunk/debian/patches/0001-Add-OpenSSL-linking-exception-from-upstream.patch (rev 0)
+++ packages/pyrit/trunk/debian/patches/0001-Add-OpenSSL-linking-exception-from-upstream.patch 2010-06-18 18:21:54 UTC (rev 5637)
@@ -0,0 +1,37 @@
+From: Christian Kastner <debian at kvr.at>
+Date: Thu, 20 May 2010 04:32:28 +0200
+Subject: [PATCH] Add OpenSSL linking exception from upstream
+
+Upstream has added a linking exception for OpenSSL in SVN. Upstream has
+authorized me to add this exception to the current version 0.3.0.
+
+Origin: upstream, http://code.google.com/p/pyrit/source/detail?r=257
+Applied-Upstream: 0.3.1
+Last-Update: 2010-05-19
+---
+ cpyrit/_cpyrit_cpu.c | 11 +++++++++++
+ 1 files changed, 11 insertions(+), 0 deletions(-)
+
+diff --git a/cpyrit/_cpyrit_cpu.c b/cpyrit/_cpyrit_cpu.c
+index b082b74..63a0008 100644
+--- a/cpyrit/_cpyrit_cpu.c
++++ b/cpyrit/_cpyrit_cpu.c
+@@ -16,6 +16,17 @@
+ #
+ # You should have received a copy of the GNU General Public License
+ # along with Pyrit. If not, see <http://www.gnu.org/licenses/>.
++#
++# Additional permission under GNU GPL version 3 section 7
++#
++# If you modify this Program, or any covered work, by linking or
++# combining it with the OpenSSL project's "OpenSSL" library (or a
++# modified version of that library), containing parts covered by
++# the terms of OpenSSL/SSLeay license, the licensors of this
++# Program grant you additional permission to convey the resulting
++# work. Corresponding Source for a non-source form of such a
++# combination shall include the source code for the parts of the
++# OpenSSL library used as well as that of the covered work.
+ */
+
+ #include <Python.h>
+--
Added: packages/pyrit/trunk/debian/patches/0002-Clean-up-after-unit-tests.patch
===================================================================
--- packages/pyrit/trunk/debian/patches/0002-Clean-up-after-unit-tests.patch (rev 0)
+++ packages/pyrit/trunk/debian/patches/0002-Clean-up-after-unit-tests.patch 2010-06-18 18:21:54 UTC (rev 5637)
@@ -0,0 +1,35 @@
+From: Christian Kastner <debian at kvr.at>
+Date: Thu, 20 May 2010 01:50:51 +0200
+Subject: [PATCH] Clean up after unit tests
+
+The setup code for unit tests in test/ creates temporary directories without
+removing them afterwards. This patch does this.
+
+Forwarded: yes
+Last-Update: 2010-05-19
+---
+ test/test_pyrit.py | 3 ++-
+ 1 files changed, 2 insertions(+), 1 deletions(-)
+
+diff --git a/test/test_pyrit.py b/test/test_pyrit.py
+index 939abb3..cb11695 100755
+--- a/test/test_pyrit.py
++++ b/test/test_pyrit.py
+@@ -21,6 +21,7 @@
+ from __future__ import with_statement
+
+ import os
++import shutil
+ import random
+ import unittest
+ import cStringIO
+@@ -44,7 +45,7 @@ class Pyrit_CLI_TestFunctions(unittest.TestCase):
+ self.cli.verbose = False
+
+ def tearDown(self):
+- pass
++ shutil.rmtree(self.storage_path)
+
+ def _createPasswords(self, filename, count=5000):
+ test_passwds = ['test123%i' % i for i in xrange(count-1)]
+--
Added: packages/pyrit/trunk/debian/patches/0003-Add-man-page-for-pyrit-1.patch
===================================================================
--- packages/pyrit/trunk/debian/patches/0003-Add-man-page-for-pyrit-1.patch (rev 0)
+++ packages/pyrit/trunk/debian/patches/0003-Add-man-page-for-pyrit-1.patch 2010-06-18 18:21:54 UTC (rev 5637)
@@ -0,0 +1,486 @@
+From: Christian Kastner <debian at kvr.at>
+Date: Thu, 20 May 2010 01:53:00 +0200
+Subject: [PATCH] Add man page for pyrit(1)
+
+The Debian project requires that all commands provide a man page. This patch
+adds a man page for the pyrit command to section 1.
+
+Forwarded: yes
+Last-Update: 2010-05-09
+---
+ pyrit.1 | 465 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ 1 files changed, 465 insertions(+), 0 deletions(-)
+ create mode 100644 pyrit.1
+
+diff --git a/pyrit.1 b/pyrit.1
+new file mode 100644
+index 0000000..342ce64
+--- /dev/null
++++ b/pyrit.1
+@@ -0,0 +1,465 @@
++.TH PYRIT 1 "2010-05-08" "pyrit" PYRIT
++.SH NAME
++pyrit \- A GPGPU-driven WPA/WPA2-PSK key cracker
++.SH SYNOPSIS
++.B pyrit
++.RI [ options ]
++.I command
++.SH DESCRIPTION
++\fBpyrit\fP exploits the computational power of many-core- and GPGPU-platforms
++to create massive databases, pre-computing part of the WPA/WPA2-PSK
++authentication phase in a space-time tradeoff. It is a powerful attack against
++one of the world's most used security-protocols.
++.sp
++This document tries to describe and explain all functions the commandline-client
++\fBpyrit\fP provides.
++One or more \fBoptions\fP may be given on the commandline to customize a
++\fBcommand\fP. The exact behaviour of \fBoptions\fP depends on the
++\fBcommand\fP.
++.SH OPTIONS
++\fBPyrit\fP recognizes the following options:
++.TP
++.BR \-b " BSSID"
++Specifies a BSSID. Can be used to restrict commands to certain Access-Points.
++.TP
++.BR \-e " ESSID"
++Specifies the ESSID. Commands usually refer to all ESSIDs in the database when
++this option is omitted.
++.TP
++.BR \-i " infile"
++Specifies a filename to read from; the special filename '\fB-\fP' can be used
++for \fBstdin\fP. The file may be gzip-compressed in which case its name must
++end in \fB.gz\fP for transparent decompression.
++.TP
++.BR \-o " outfile"
++Specifies a filename to write to; the special filename '\fB-\fP' can be used
++for \fBstdout\fP. Filenames that end in \fB.gz\fP cause \fBpyrit\fP to
++gzip-compress the file on the fly.
++.TP
++.BR \-r " capfile"
++Specifies a packet-capture file in pcap format (possibly gzip-compressed).
++.TP
++.BR \-u " URL"
++Specifies the URL of the storage-device in the form of
++.sp
++.RS 12
++.nf
++driver://username:password@host:port/database
++.fi
++.RE
++.sp
++.RS
++\fBPyrit\fP can use the filesystem, a remote Pyrit-Relay-Server and, if the
++package \fBpython-sqlalchemy\fP is installed, SQL-Databases as storage. The
++driver \fIfile://\fP refers to \fBpyrit\fP's own filesystem-based storage,
++\fIhttp://\fP connects to a Pyrit-Relay-Server and all other URLs are passed
++directly to \fBpython-sqlalchemy\fP, if available. The default storage-URL
++can also be specified by the key \fBdefaultstorage\fP in \fBpyrit\fP's
++configuration file (see \fBFILES\fP below).
++.RE
++.SH COMMANDS
++.TP
++.B analyze
++Parse one or more packet-capture files (in pcap-format, possibly
++gzip-compressed) given by the option \fB-r\fP and try to detect
++Access-Points, Stations and EAPOL-handshakes. For example:
++.sp
++.RS 12
++.nf
++pyrit \-r "test*.pcap" analyze
++.fi
++.RE
++.sp
++.RS
++The suffix 'handshake found' is appended to the Station's BSSID if the
++communication between the Access-Point and the Station seems to include a valid
++EAPOL-handshake.
++.RE
++.TP
++.B attack_batch
++Attack an EAPOL-handshake found in the packet-capture file(s) given by the
++option \fB-r\fP using the Pairwise Master Keys and passwords stored in the
++database. The options \fB-b\fP and \fB-e\fP can be used to specify the
++Access-Point to attack; it is picked automatically if both options are omitted.
++The password is written to the filename given by the option \fB-o\fP if
++specified. For example:
++.sp
++.RS 12
++.nf
++pyrit \-r test.pcap \-e MyNetwork \-b 00:de:ad:c0:de:00 \\
++ \-o MyNetworkPassword.txt attack_batch
++.fi
++.RE
++.sp
++.RS
++Pairwise Master Keys that have been computed and stored in the database
++previously are taken from there; all other passwords are translated into their
++respective Pairwise Master Keys and added to the database for later re-use.
++ESSIDs are created automatically in the database if necessary.
++.RE
++.TP
++.B attack_cowpatty
++Attack an EAPOL-handshake found in the packet-capture file(s) given by the
++option \fB-r\fP using Pairwise Master Keys from a cowpatty-like file (e.g.
++generated by \fB\`\`genpmk''\fP from \fBcowpatty\fP(1), or
++\fB\`\`export_cowpatty''\fP) given by the option \fB-f\fP. The options
++\fB-b\fP and \fB-e\fP can be used to specify the Access-Point to attack;
++it is picked automatically if both options are omitted. The password is
++written to the filename given by the option \fB-o\fP if specified.
++The cowpatty-file may be gzip-compressed and must match the chosen ESSID.
++For example:
++.sp
++.RS 12
++.nf
++pyrit \-r test.pcap \-e MyOwnNetwork \\
++ \-i MyOwnNetwork.cow.gz \-o \- attack_cowpatty
++.fi
++.RE
++.sp
++.RS
++\fBPyrit\fP's own database is not touched by \fBattack_cowpatty\fP.
++.RE
++.TP
++.B attack_db
++Attack an EAPOL-handshake found in the packet-capture file(s) given by the
++option \fB-r\fP using the Pairwise Master Keys stored in the database. The
++options \fB-b\fP and \fB-e\fP can be used to specify the Access-Point to
++attack; it is picked automatically if both options are omitted.
++The password is written to the filename given by the option \fB-o\fP if
++specified. For example:
++.sp
++.RS 12
++.nf
++pyrit \-r test.pcap \-e MyOtherNetwork attack_db
++.fi
++.RE
++.sp
++.RS
++Only Pairwise Master Keys that have been computed previously and are stored in
++the database are used by \fBattack_db\fP.
++.RE
++.TP
++.B attack_passthrough
++Attack an EAPOL-handshake found in the packet-capture file given by the option
++\fB-r\fP using the passwords read from the file given by the option \fB-i\fP.
++The options \fB-b\fP and \fB-e\fP can be used to specify the Access-Point to
++attack; it is picked automatically if both options are omitted. The password is
++written to the filename given by the option \fB-o\fP if specified. For example:
++.sp
++.RS 12
++.nf
++pyrit \-r test.pcap \-b 00:de:ad:be:ef:00 \\
++ \-i words.txt attack_passthrough
++.fi
++.RE
++.sp
++.RS
++This command circumvents \fBPyrit\fP's database and should only be used if
++storage-space is a problem (e.g. on LiveCDs). You should consider using
++\fBattack_batch\fP otherwise.
++.RE
++.TP
++.B batch
++.br
++Start to translate all passwords in the database into their respective PMKs and
++store the results in the database. The option \fB-e\fP may be used to restrict
++this command to a single ESSID; if it is ommitted, all ESSIDs are processed one
++after the other in undefined order. For example:
++.sp
++.RS 12
++.nf
++pyrit \-e NETGEAR batch
++.fi
++.RE
++.sp
++.RS
++The option \fB-o\fP can be used to specify a filename the results should
++additionally be written to in \fBcowpatty\fP's binary format. The option
++\fB-e\fP becomes mandatory and the ESSID is automatically created in the
++database if necessary. Pairwise Master Keys that previously have been computed
++and stored in the database are exported from there without further processing.
++\fBpyrit\fP stops and exits if an \fBIOError\fP is raised while writing to the
++specified file but signals success on exit. This makes it very convenient to
++pipe results directly to other programs but also keep them for later use. For
++example:
++.RE
++.sp
++.RS 12
++.nf
++pyrit \-e NETGEAR \-o \- batch | \\
++ cowpatty \-d \- \-r wpatestcapture.cap \-s NETGEAR
++.fi
++.RE
++.TP
++.B benchmark
++Determine the peak-performance of the available hardware by computing
++dummy-results. For example:
++.sp
++.RS 12
++.nf
++pyrit benchmark
++.fi
++.RE
++.TP
++.B create_essid
++Add the ESSID given by \fB-e\fP to the database. Re-creating an existing ESSID
++does not result in an error. For example:
++.sp
++.RS 12
++.nf
++pyrit \-e NETGEAR create_essid
++.fi
++.RE
++.TP
++.B delete_essid
++Delete the ESSID given by \fB-e\fP from the database. This includes all results
++that may have been stored for that particular ESSID. For example:
++.sp
++.RS 12
++.nf
++pyrit \-e NETGEAR delete_essid
++.fi
++.RE
++.TP
++.B eval
++.br
++Count all available passwords, all ESSIDs and their respective results in the
++database. For example:
++.sp
++.RS 12
++.nf
++pyrit eval
++.fi
++.RE
++.TP
++.B export_passwords
++Write all passwords that are currently stored in the database to a new file
++given by \fB-o\fP. Passwords are terminated by a single newline-character
++("\\n"). Existing files are overwritten without confirmation. For example:
++.sp
++.RS 12
++.nf
++pyrit \-o myword.txt.gz export_passwords
++.fi
++.RE
++.TP
++.B export_cowpatty
++Write all results for the ESSID given by \fB-e\fP to the file given by \fB-o\fP
++in \fBcowpatty\fP's binary format. Existing files are overwritten without
++confirmation. For example:
++.sp
++.RS 12
++.nf
++pyrit \-o NETGEAR.cow \-e NETGEAR export_cowpatty
++.fi
++.RE
++.TP
++.B export_hashdb
++Write all results currently stored in the database to the airolib-ng-database
++given by \fB-o\fP. The database is created with a default table layout if the
++file does not yet exist. The option \fB-e\fP can be used to limit the export
++to a single ESSID. For example:
++.sp
++.RS 12
++.nf
++pyrit \-o NETGEAR.db \-e NETGEAR export_hashdb
++.fi
++.RE
++.TP
++.B import_passwords
++Read the file given by \fB-i\fP and import one password per line to the
++database. The passwords may contain all characters (including NULL-bytes) apart
++from the terminating newline-character ("\\n").
++Passwords that are not suitable for being used with WPA-/WPA2-PSK are ignored.
++\fBPyrit\fP's storage-implementation guarantees that all passwords remain
++unique throughout the entire database. For example:
++.sp
++.RS 12
++.nf
++pyrit \-i dirty_words.txt import_passwords
++.fi
++.RE
++.TP
++.B import_unique_passwords
++Read the file given by \fB-i\fP and import one password per line to the
++database. The passwords may contain all characters (including NULL-bytes) apart
++from the terminating newline-character ("\\n"). Passwords that are not suitable
++for being used with WPA-/WPA2-PSK are ignored. This command does \finot\fP check
++if there are duplicating passwords within the file or between the file and the
++database; it should be used with caution to prevent the database from getting
++poisoned with duplicated passwords. This command however can be much faster than
++\fBimport_passwords\fP. For example:
++.sp
++.RS 12
++.nf
++pyrit -i dirty_words.txt import_unique_passwords
++.fi
++.RE
++.TP
++.B list_cores
++Show a list of all available hardware modules \fBpyrit\fP currently uses. For
++example:
++.sp
++.RS 12
++.nf
++pyrit list_cores
++.fi
++.RE
++.TP
++.B list_essids
++Show a list of all ESSIDs currently stored in the database. This function is
++faster than \fBeval\fP in case you don't need to know the number of computed
++results. For example:
++.sp
++.RS 12
++.nf
++pyrit list_essids
++.fi
++.RE
++.TP
++.B passthrough
++.br
++Read passwords from the file given by \fB-i\fP and compute their PMKs for the
++ESSID given by \fB-e\fP. The results are written to the file specified by
++\fB-o\fP in \fBcowpatty\fP's binary format and are not stored in the
++database for later use. This command therefor circumvents the entire database
++and should only be used if storage-space is a problem (e.g. when using
++\fBpyrit\fP on a LiveCD). The \fBbatch\fP-command provides exactly the same
++functionality as \fBpassthrough\fP but can give much better performance as
++results may be read from the database instead of recomputing them. For
++example:
++.sp
++.RS 12
++.nf
++pyrit \-i dirty_words.txt.gz \-e NETGEAR \\
++ \-o \- passthrough | cowpatty \-d \- \\
++ \-r wpatestcapture.cap \-s NETGEAR
++.fi
++.RE
++.TP
++.B relay
++.br
++Start a server to relay another storage device via XML-RPC; other
++\fBpyrit\fP-clients can use the server as storage-device. This allows to have
++network-based access to storage source that don’t provide network-access on
++their own (like \fIfile://\fP and \fIsqlite://\fP) or hide a SQL-database
++behind a firewall and let multiple clients access that database only via
++\fBpyrit\fP’s RPC-interface. The TCP-port 17934 must be open for this function
++to work. For example, on the server (where the database is):
++.sp
++.RS 12
++.nf
++pyrit \-u sqlite://var/local/pyrit.db relay
++.fi
++.RE
++.sp
++.RS
++and the client (where the big GPU is):
++.RE
++.sp
++.RS 12
++.nf
++pyrit \-u http://192.168.0.100:17934 batch
++.fi
++.RE
++.TP
++.B selftest
++Run an extensive selftest for about 60 seconds. This test includes the entire
++scheduling-mechanism and all cores that are listed by \fBlist_cores\fP. You can
++use this function to detect broken hardware-modules or malicious
++network-clients. For example:
++.sp
++.RS 12
++.nf
++pyrit selftest
++.fi
++.RE
++.TP
++.B serve
++.br
++Start a server that provides access to the local computing hardware to help
++other \fBpyrit\fP-clients. The server's IP-address should be added to the
++clients' configuration file (see \fBFILES\fP) as a space-separated list under
++\fBknown_clients\fP. These clients' \fBrpc_server\fP-setting must also be
++set to 'true'. The TCP- and UDP-Port 17935 must be accessible. For
++example, on the server (where the GPU is):
++.sp
++.RS 12
++.nf
++pyrit serve
++.fi
++.RE
++.sp
++.RS
++and the clients (the server's IP-address has been added to
++\fBknown_clients\fP and \fBrpc_server\fP is set to 'true'):
++.RE
++.sp
++.RS 12
++.nf
++pyrit \-r test.pcap \-b 00:de:ad:be:ef:00 \\
++ \-i words.txt attack_passthrough
++.fi
++.RE
++.TP
++.B strip
++.br
++Parse one or more packet-capture files given by the option \fB-r\fP, extract
++only packets that are necessary for EAPOL-handshake detection and write a new
++dump to the filename given by the option \fB-o\fP. The options \fB-e\fP and
++\fB-b\fP can be used to filter certain Access-Points. For example:
++.sp
++.RS 12
++.nf
++pyrit \-r "large_dumps_*.pcap" \-e MyNetwork \\
++ \-o tiny_compressed_dump_MyNetwork.dump.gz strip
++.fi
++.RE
++.TP
++.B stripLive
++Parse a packet-capture file given by the option \fB-r\fP, extract only packets
++that are necessary for EAPOL-handshake detection and write a new dump to the
++file given by the option \fB-o\fP. This command differs from \fBstrip\fP as the
++capture-file can be any character device including sockets and other
++pseudo-files that \fIlook like\fP files in pcap-format. \fBstripLive\fP writes
++relevant packets to the new file given by \fB-o\fP as they arrive instead of
++trying to read the entire capture-file first.
++.sp
++.RS 12
++.nf
++pyrit \-r /temp/kismet_dump \-o small_dump.pcap stripLive
++.fi
++.RE
++.TP
++.B verify
++.br
++Randomly pick 10% of the results stored in the database and verify their value
++by recomputation. You need this function if you suspect broken hardware or
++malicious network-clients. For example:
++.sp
++.RS 12
++.nf
++pyrit \-e NETGEAR verify
++.fi
++.RE
++.SH EXIT STATUS
++If \fBcommand\fP succeeds, \fBpyrit\fP's process exit status is set to 0;
++otherwise it is set to 1 and (usually) an error message or a python-traceback is
++written to stderr.
++.SH FILES
++.TP
++.I ~/.pyrit/config
++ The \fBpyrit\fP configuration file
++.SH NOTES
++The author does not encourage or support using \fBpyrit\fP for the infringement
++of peoples' communication-privacy. The exploration and realization of the
++technology discussed here motivate as a purpose of their own; this is
++documented by the open development, strictly sourcecode-based distribution and
++\'copyleft'-licensing.
++.SH SEE ALSO
++.BR cowpatty (1)
++.SH AUTHOR
++cowpatty was written by Lukas Lueg <lukas.lueg at gmail.com>.
++.PP
++This manual page was written by Christian Kastner <debian at kvr.at>,
++for the Debian project (but may be used by others).
+--
Added: packages/pyrit/trunk/debian/patches/0004-Fixed-depreciation-warning-generated-by-sql-alchemy.patch
===================================================================
--- packages/pyrit/trunk/debian/patches/0004-Fixed-depreciation-warning-generated-by-sql-alchemy.patch (rev 0)
+++ packages/pyrit/trunk/debian/patches/0004-Fixed-depreciation-warning-generated-by-sql-alchemy.patch 2010-06-18 18:21:54 UTC (rev 5637)
@@ -0,0 +1,51 @@
+From: Christian Kastner <debian at kvr.at>
+Date: Wed, 9 Jun 2010 22:25:09 +0200
+Subject: [PATCH] Fixed depreciation warning generated by sql-alchemy
+
+sql.Binary was renamed to sql.LargeBinary in sql-alchemy v0.6.1. This generates
+a warning everytime pyrit is run.
+
+Bug: http://code.google.com/p/pyrit/issues/detail?id=134
+Forwarded: no
+Last-Update: 2010-06-09
+---
+ cpyrit/storage.py | 11 +++++++----
+ 1 files changed, 7 insertions(+), 4 deletions(-)
+
+diff --git a/cpyrit/storage.py b/cpyrit/storage.py
+index a31cb73..69787c5 100644
+--- a/cpyrit/storage.py
++++ b/cpyrit/storage.py
+@@ -738,7 +738,8 @@ if 'sqlalchemy' in sys.modules:
+
+ essids_table = sql.Table('essids', metadata, \
+ sql.Column('essid_id', sql.Integer, primary_key=True),
+- sql.Column('essid', sql.Binary(32), nullable=False),
++ sql.Column('essid', sql.LargeBinary(32), \
++ nullable=False),
+ sql.Column('uid', sql.String(32), unique=True, \
+ nullable=False), \
+ mysql_engine='InnoDB')
+@@ -747,8 +748,9 @@ if 'sqlalchemy' in sys.modules:
+ sql.Column('_key', sql.String(32), primary_key=True),
+ sql.Column('h1', sql.String(2), nullable=False),
+ sql.Column('numElems', sql.Integer, nullable=False),
+- sql.Column('collection_buffer', sql.Binary(2**24-1), \
+- nullable=False), \
++ sql.Column('collection_buffer', \
++ sql.LargeBinary(2**24-1), \
++ nullable=False), \
+ mysql_engine='InnoDB')
+
+ results_table = sql.Table('results', metadata, \
+@@ -759,7 +761,8 @@ if 'sqlalchemy' in sys.modules:
+ sql.ForeignKey('essids.essid_id'), \
+ primary_key=True),
+ sql.Column('numElems', sql.Integer, nullable=False),
+- sql.Column('results_buffer', sql.Binary(2**24 - 1), \
++ sql.Column('results_buffer', \
++ sql.LargeBinary(2**24 - 1), \
+ nullable=False), \
+ mysql_engine='InnoDB')
+
+--
Added: packages/pyrit/trunk/debian/patches/series
===================================================================
--- packages/pyrit/trunk/debian/patches/series (rev 0)
+++ packages/pyrit/trunk/debian/patches/series 2010-06-18 18:21:54 UTC (rev 5637)
@@ -0,0 +1,4 @@
+0001-Add-OpenSSL-linking-exception-from-upstream.patch
+0002-Clean-up-after-unit-tests.patch
+0003-Add-man-page-for-pyrit-1.patch
+0004-Fixed-depreciation-warning-generated-by-sql-alchemy.patch
Added: packages/pyrit/trunk/debian/pyversions
===================================================================
--- packages/pyrit/trunk/debian/pyversions (rev 0)
+++ packages/pyrit/trunk/debian/pyversions 2010-06-18 18:21:54 UTC (rev 5637)
@@ -0,0 +1 @@
+2.5-
Added: packages/pyrit/trunk/debian/rules
===================================================================
--- packages/pyrit/trunk/debian/rules (rev 0)
+++ packages/pyrit/trunk/debian/rules 2010-06-18 18:21:54 UTC (rev 5637)
@@ -0,0 +1,20 @@
+#!/usr/bin/make -f
+# -*- makefile -*-
+
+# Uncomment this to turn on verbose mode.
+#export DH_VERBOSE=1
+
+PYVERS = $(shell pyversions -r -v)
+BUILD_LIBROOT = build/lib.$(DEB_BUILD_ARCH_OS)-$(shell uname -m)
+
+%:
+ dh $@
+
+override_dh_auto_test:
+ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))
+ set -e ;\
+ cd test ;\
+ for py in $(PYVERS); do \
+ PYTHONPATH=$(CURDIR)/$(BUILD_LIBROOT)-$$py python$$py test_pyrit.py; \
+ done
+endif
Property changes on: packages/pyrit/trunk/debian/rules
___________________________________________________________________
Added: svn:executable
+ *
Added: packages/pyrit/trunk/debian/source/format
===================================================================
--- packages/pyrit/trunk/debian/source/format (rev 0)
+++ packages/pyrit/trunk/debian/source/format 2010-06-18 18:21:54 UTC (rev 5637)
@@ -0,0 +1 @@
+3.0 (quilt)
Added: packages/pyrit/trunk/debian/watch
===================================================================
--- packages/pyrit/trunk/debian/watch (rev 0)
+++ packages/pyrit/trunk/debian/watch 2010-06-18 18:21:54 UTC (rev 5637)
@@ -0,0 +1,5 @@
+version=3
+opts=\
+downloadurlmangle=s|.*[?]name=(.*?)&.*|http://pyrit.googlecode.com/files/$1|,\
+filenamemangle=s|[^/]+[?]name=(.*?)&.*|$1| \
+http://code.google.com/p/pyrit/downloads/detail[?]name=pyrit-([0-9.]+).tar.gz&.*
More information about the Python-apps-commits
mailing list