--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: 'man weplab' typos: "DICTIONNARY", "aditional", "aproach", "apropiate", "begining", "canditate", "carefull", "conjuntion", "dictionnary", "efectiveness", "futher", "maximun", "memmory", "minimun", "neccesary", "oportunity", "proccessor", "sintax", "succesfully", "usefull", etc.
- From: "A. Costa" <agcosta@gis.net>
- Date: Fri, 7 Oct 2011 15:35:16 -0400
- Message-id: <20111007153516.d048300622b649544e4cdb62@gis.net>
Package: weplab
Version: 0.1.5-2
Severity: minor
Tags: patch
Found some typos in '/usr/share/man/man1/weplab.1.gz', see attached '.diff'.
Hope this helps...
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Versions of packages weplab depends on:
ii libc6 2.13-2
ii libpcap0.8 1.1.1-4
weplab recommends no packages.
weplab suggests no packages.
-- no debconf information
--- weplab.1 2007-12-02 14:17:50.000000000 -0500
+++ /tmp/weplab.1 2011-10-07 01:29:56.784760519 -0400
@@ -7,7 +7,7 @@
weplab is a tool to review the security of WEP
encryption in wireless networks from an educational point of view.
Several attacks are available (including advanced statistical attacks)
-so it can be measured the efectiveness and minimun requirements of
+so it can be measured the effectiveness and minimum requirements of
each one.
.PP
On the other hand, weplab can also be saw as
@@ -31,7 +31,7 @@
find the right one.
Please, that this can take lot of time depending on the key size and your
-processor speed. Refer to Bruteforce method above in this document for futher
+processor speed. Refer to Bruteforce method above in this document for further
information.
If no BSSID was specified, those packets who belong to the same network
@@ -51,7 +51,7 @@
This method is very advanced. You are fully encouraged to understand it
reading its section on this document. Although it use to work fine with default
options and having, enough packets, its better to understand how it works so
-you can tweak the procedure using the apropiate parameters.
+you can tweak the procedure using the appropriate parameters.
If no BSSID was specified, those packets who belong to the same network
as the first one, will be used for the crack.
@@ -62,7 +62,7 @@
Many WEP keys are derived from pass\-phrases, entered by the network
administrator. When, this happens and you do not have enough packets to
launch a statistical attack, it is better to use a dictionary based cracking
-than a bruteforce aproach.
+than a bruteforce approach.
On dictionary attack, John the Ripper is used to generate the words that
weplab will use to derive the WEP key. So, John the Ripper must be present and
@@ -75,8 +75,8 @@
\-k, \-\-key \fI<key_length>\fR
Specify the key length. It can be either 64 or 128\-bit
-This option is only usefull within a cracking method, so \-y, \-r or \-b
-must be used in conjuntion with it.
+This option is only useful within a cracking method, so \-y, \-r or \-b
+must be used in conjunction with it.
Default: 64 bits.
.TP
@@ -95,14 +95,14 @@
packets
Depending on your driver and how did you set your card into monitor mode
-, it is possible than logged packets have an aditional tail of 1 byte length.
+, it is possible than logged packets have an additional tail of 1 byte length.
Best way to find out if your card/drivers needs this, is trying to break
your own network. This way, as you already know the key, if it does not get
cracked without FCS, try with it.
-This option is only usefull within a cracking method, so \-y, \-r or \-b
-must be used in conjuntion with it.
+This option is only useful within a cracking method, so \-y, \-r or \-b
+must be used in conjunction with it.
Default: fcs not present.
.TP
@@ -111,17 +111,17 @@
on all logged packets
Depending on your driver and how did you set your card into monitor mode
-, it is possible than logged packets have an aditional header of 144 bytes length.
+, it is possible than logged packets have an additional header of 144 bytes length.
If you want to know if you need it or not, just analyze the file with
-weplab. If prismheader is not necessary it will tell you. If it is neccesary, you
-will see lot of bogus BSSIDs, and no adversice about not using prismehader
+weplab. If prismheader is not necessary it will tell you. If it is necessary, you
+will see lot of bogus BSSIDs, and no advice about not using prismeheader
Anyway, cracking your own WEP key is the best method to know if you need it
or not.
-This option is only usefull within a cracking method, so \-y, \-r or \-b
-must be used in conjuntion with it. From weplab 0.1.2 you will also need to specify
+This option is only useful within a cracking method, so \-y, \-r or \-b
+must be used in conjunction with it. From weplab 0.1.2 you will also need to specify
it with \-a in order weplab to show you the right BSSIDs found.
Default: prismheader not present.
@@ -136,8 +136,8 @@
Use \-a with your file if you want to see all detected BSSIDs
-This option is only usefull within a cracking method, so \-y, \-r or \-b
-must be used in conjuntion with it.
+This option is only useful within a cracking method, so \-y, \-r or \-b
+must be used in conjunction with it.
Default: none
.TP
@@ -149,7 +149,7 @@
needed.
In order to save diskspace when logging packets for the statistical attack,
-ony the begining of the packet should be logged
+only the beginning of the packet should be logged
If you specify 0 here, the whole packet will be logged.
@@ -187,13 +187,13 @@
the key\-space is smaller the attack is faster.
.TP
\-\-perc \fI<probability>\fR
-Specify the desired minimun probability for the statistical attack.
+Specify the desired minimum probability for the statistical attack.
It means that at least enough candidate key bytes will be tested to fit this probability.
In order to fully understand this option you are encouraged to read carefully the
"Statistical Attacks" caption, above in this document.
-Please note that the higher the minimun probability the slowest the attack.
+Please note that the higher the minimum probability the slowest the attack.
For most cases 50% is fine. You can increase to 60 or 70% if you get the KEY NOT FOUND with 50, but never
increase it to 100% because you will be waiting for ever.
.TP
@@ -219,7 +219,7 @@
.TP
\-\-debugkey \fI<key>\fR
if you want to test how a set of statistical attacks works with a known WEP key, then
-this parameter will give you the oportunity to get the final result without going trhow all the possible
+this parameter will give you the opportunity to get the final result without going through all the possible
branches.
Using this option you tell weplab about the WEP key used to encrypt the packets. Only the real branch
@@ -237,16 +237,16 @@
by root.
.PP
if you are installing it from source code distribution, the configure script should be able to detect
-your proccessor type to optimize the code specifically for your platform.
+your processor type to optimize the code specifically for your platform.
.PP
-At least 128 MB of free RAM memmory are required to run FMS statistical attack in weplab,
+At least 128 MB of free RAM memory are required to run FMS statistical attack in weplab,
64 MB of free ram for capturing packets, and nothing special for the other features.
.PP
Weplab is reported to work fine under GNU/Linux for intel, GNU/Linux for PPC and MacOSX.
.PP
Windows version cannot capture packets due to the lack of a opensource method to do it, but its
other features works fine. Please read Windows Platform section under Capture Packets caption for
-futher information about how to deal with this issue under Windows.
+further information about how to deal with this issue under Windows.
.SH "CAPTURING PACKETS"
First you will need to capture 802.11b encrypted packets to crack the wep key.
The way weplab cracks the key is using passive attacks to an already captured packet set.
@@ -301,7 +301,7 @@
weplab \-\-debug 1 \-c \-i wlan0 ./packets.log
There is no need to log the entire packet, just the 802.11 header and the IV, but to verify
-possible canditate keys the whole packet encrypted payload must be present. That's why you must
+possible candidate keys the whole packet encrypted payload must be present. That's why you must
specify two files in weplab when using FMS attack. One file must have just 10 packets with the
whole payload, and the other file contains weak packets that don't need to have payload logged.
.PP
@@ -309,7 +309,7 @@
one file, and then just log the first bytes of all other possible packets, to be used as possible
weak packet for FMS attack.
.PP
-You can specify maximun captured bytes per packet with \-\-caplen bytes
+You can specify maximum captured bytes per packet with \-\-caplen bytes
weplab \-c \-i wlan0 \-\-debug 1 ./verification_packets.logweplab \-c \-i wlan0 \-\-debug 1 \-\-caplen 100 ./weak_packets.log
@@ -344,21 +344,21 @@
Bruteforce cracking means testing all possible keys to find the right one.
That means that each key byte can take values from 0 to 255. So a quick calculus will reveal
that for a 64 bits key the total combinations are 2^40, so at 100.000 c/s cracking the key
-will take you 4100061318 seconds maximun. 127 days working fulltime.
+will take you 4100061318 seconds maximum. 127 days working fulltime.
.PP
With a 128\-bit key the total combinations possible are 2^104, so at 100.000 c/s
-the total maximun amount of time will be 6520836420927105974 YEARS!!
+the total maximum amount of time will be 6520836420927105974 YEARS!!
I guess you will never try to launch a bruteforce attack to a 128\-bit key.
Anyway, weplab gives you the possibility to do it ;)
.PP
You will need at least 10 full wep encrypted data captured packets in order
to launch a bruteforce attack avoiding false positives.
-.SH "DICTIONNARY CRACKING"
-Guess what ? Users often use simple words as their WEP key. The dictionnary cracking
+.SH "DICTIONARY CRACKING"
+Guess what ? Users often use simple words as their WEP key. The dictionary cracking
mode gives you the ability to check if the WEP key isn't a so\-simple\-to\-guess word. Using
-this mode in addition to John\-the\-Ripper could produce some usefull results.
+this mode in addition to John\-the\-Ripper could produce some useful results.
.PP
-Weplab reads the dictionnary words from STDIN, so if you want statistics, you want
+Weplab reads the dictionary words from STDIN, so if you want statistics, you want
be able to press SPACE. However, you'll have statistics printed on STDOUT every 10 seconds.
.PP
Dictionary cracking can use two different modes :
@@ -412,14 +412,14 @@
You want to test the tool so you collect 1.5M packets from your own wireless LAN.
You just want to know if weplab would be able to crack it.
-You can use first \-\-debugkey. If you are using a 128\-bit key the right sintax would be:
+You can use first \-\-debugkey. If you are using a 128\-bit key the right syntax would be:
.PP
weplab \-r./packets.log \-\-debugkey 01:02:03:04:05:06:07:08:09:10:11:12:13 \-\-debug 1
\-\-key 128 ./packets.log
.PP
You should see the statistics and guesses for each byte of the key so you can see the viability
-of the attack. At the end you should see "key succesfully cracked". If you do not see such message,
-perhaps your captured packets have the FCS tail so it will be neccesary to issue \-\-fcs
+of the attack. At the end you should see "key successfully cracked". If you do not see such message,
+perhaps your captured packets have the FCS tail so it will be necessary to issue \-\-fcs
.PP
weplab \-r./packets.log \-\-debugkey 01:02:03:04:05:06:07:08:09:10:11:12:13
\-\-fcs \-\-debug 1 \-\-key 128 ./packets.log
@@ -450,7 +450,7 @@
Example 3. Capturing packets.
.PP
In order to capture packets you have to put your wireless card in monitor mode in the right channel.
-Be carefull to configure monitor mode to ignore WEP bit.
+Be careful to configure monitor mode to ignore WEP bit.
Once you have your card in monitor mode, you can capture packets using tcpdump or weplab \-c \-i interface
.PP
weplab \-c \-i wlan0 \-\-debug 1 \-\-caplen 150 ./packets.log
@@ -464,9 +464,9 @@
.PP
weplab \-a \-\-debug 1 ./pcap.log
.PP
-Example 5. Cracking a 64 WEP key using a dictionnary file with John the Ripper
+Example 5. Cracking a 64 WEP key using a dictionary file with John the Ripper
.PP
-john \-w:/path/to/my/big/dictionnaryfile \-rules \-stdout | weplab \-y \-d 1 \-\-key 64 capt.dump
+john \-w:/path/to/my/big/dictionaryfile \-rules \-stdout | weplab \-y \-d 1 \-\-key 64 capt.dump
.SH VERSION
This man page is correct for version 0.1.3 of weplab
.SH AUTHOR
--- End Message ---