[Python-apps-commits] r5745 - in packages/pyrit/trunk/debian/patches (1 file)

Sun Jul 4 18:24:59 UTC 2010

Date: Sunday, July 4, 2010 @ 18:24:40
  Author: chrisk-guest
Revision: 5745

Add final polishing to man page

Modified:
  packages/pyrit/trunk/debian/patches/0003-Add-man-page-for-pyrit-1.patch

Modified: 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	2010-07-04 08:11:02 UTC (rev 5744)
+++ packages/pyrit/trunk/debian/patches/0003-Add-man-page-for-pyrit-1.patch	2010-07-04 18:24:40 UTC (rev 5745)
@@ -12,12 +12,11 @@
  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 @@
+Index: pyrit-0.3.0/pyrit.1
+===================================================================
+--- /dev/null	1970-01-01 00:00:00.000000000 +0000
++++ pyrit-0.3.0/pyrit.1	2010-07-04 15:25:09.445842450 +0200
+@@ -0,0 +1,468 @@
 +.TH PYRIT 1 "2010-05-08" "pyrit" PYRIT
 +.SH NAME
 +pyrit \- A GPGPU-driven WPA/WPA2-PSK key cracker
@@ -26,7 +25,7 @@
 +.RI [ options ]
 +.I command
 +.SH DESCRIPTION
-+\fBpyrit\fP exploits the computational power of many-core- and GPGPU-platforms
++Pyrit 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.
@@ -36,8 +35,12 @@
 +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.
++.sp
++At the time of this writing, cowpatty is not available in Debian.
++References to cowpatty and its commands are nevertheless preserved for the sake
++of completeness.
 +.SH OPTIONS
-+\fBPyrit\fP recognizes the following options:
++Pyrit recognizes the following options:
 +.TP
 +.BR \-b " BSSID"
 +Specifies a BSSID. Can be used to restrict commands to certain Access-Points.
@@ -69,9 +72,9 @@
 +.RE
 +.sp
 +.RS
-+\fBPyrit\fP can use the filesystem, a remote Pyrit-Relay-Server and, if the
++Pyrit 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,
++driver \fIfile://\fP refers to Pyrit'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
@@ -121,8 +124,8 @@
 +.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
++generated by \`\`genpmk'' from cowpatty, or \fBexport_cowpatty\fP
++below) 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.
@@ -137,7 +140,7 @@
 +.RE
 +.sp
 +.RS
-+\fBPyrit\fP's own database is not touched by \fBattack_cowpatty\fP.
++Pyrit's own database is not touched by \fBattack_cowpatty\fP.
 +.RE
 +.TP
 +.B attack_db
@@ -174,7 +177,7 @@
 +.RE
 +.sp
 +.RS
-+This command circumvents \fBPyrit\fP's database and should only be used if
++This command circumvents Pyrit'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
@@ -194,11 +197,11 @@
 +.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
++additionally be written to in cowpatty'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
++Pyrit 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:
@@ -265,7 +268,7 @@
 +.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
++in cowpatty's binary format. Existing files are overwritten without
 +confirmation. For example:
 +.sp
 +.RS 12
@@ -291,7 +294,7 @@
 +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
++Pyrit's storage-implementation guarantees that all passwords remain
 +unique throughout the entire database. For example:
 +.sp
 +.RS 12
@@ -317,7 +320,7 @@
 +.RE
 +.TP
 +.B list_cores
-+Show a list of all available hardware modules \fBpyrit\fP currently uses. For
++Show a list of all available hardware modules Pyrit currently uses. For
 +example:
 +.sp
 +.RS 12
@@ -341,10 +344,10 @@
 +.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
++\fB-o\fP in cowpatty'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
++Pyrit 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:
@@ -360,11 +363,11 @@
 +.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
++Pyrit-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
++Pyritâ€™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
@@ -398,9 +401,9 @@
 +.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
++other Pyrit clients. The server's IP-address should be added to the
++client's configuration file (see \fBFILES\fP) as a space-separated list under
++\fBknown_clients\fP. The client's \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
@@ -411,7 +414,7 @@
 +.RE
 +.sp
 +.RS
-+and the clients (the server's IP-address has been added to
++and on the client (the server's IP-address has been added to
 +\fBknown_clients\fP and \fBrpc_server\fP is set to 'true'):
 +.RE
 +.sp
@@ -469,18 +472,16 @@
 +.SH FILES
 +.TP
 +.I ~/.pyrit/config
-+    The \fBpyrit\fP configuration file
++The \fBpyrit\fP configuration file. You can find a documented example in
++\fI/usr/share/doc/pyrit/examples/config.example\fP.
 +.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>.
++\fBpyrit\fP was written by Lukas Lueg <lukas.lueg at gmail.com>.
 +.PP
-+This manual page was written by Christian Kastner <debian at kvr.at>,
++This manual page was written by Christian Kastner <debian at kvr.at>
 +for the Debian project (but may be used by others).
--- 


