summaryrefslogtreecommitdiffstats
path: root/usr.sbin/wicontrol
diff options
context:
space:
mode:
authorimp <imp@FreeBSD.org>2001-08-10 04:17:55 +0000
committerimp <imp@FreeBSD.org>2001-08-10 04:17:55 +0000
commit4de67820e0b1f27aa8498e0910c74b3d6249aaac (patch)
tree3a32e132aacadce28d4cc081d3d6d711d2a0ad3b /usr.sbin/wicontrol
parenta9e7523870a1a45ea3fdb5b432e20a788b42944c (diff)
downloadFreeBSD-src-4de67820e0b1f27aa8498e0910c74b3d6249aaac.zip
FreeBSD-src-4de67820e0b1f27aa8498e0910c74b3d6249aaac.tar.gz
Incorporate feedback about the level of security that WEP gives you:
Not much, but it is better than nothing as it discourages the extremely lazy. Please read the actual text (the last text was softer than the commit message about it) before giving me feedback. Also, in the last commit I also tagged the newly optional elements in the command line as optional.
Diffstat (limited to 'usr.sbin/wicontrol')
-rw-r--r--usr.sbin/wicontrol/wicontrol.827
1 files changed, 19 insertions, 8 deletions
diff --git a/usr.sbin/wicontrol/wicontrol.8 b/usr.sbin/wicontrol/wicontrol.8
index 5ad989a..e64f2d9 100644
--- a/usr.sbin/wicontrol/wicontrol.8
+++ b/usr.sbin/wicontrol/wicontrol.8
@@ -266,13 +266,13 @@ which means the key can be specified as either a 13 character text
string or 26 hex digits in addition to the formats supported by the
Silver cards.
.Pp
-Both 128-bit and 64-bit WEP have been broken.
+Note: Both 128-bit and 64-bit WEP have been broken.
See the BUGS section for details.
.It Fl i Ar iface Fl T Ar 1|2|3|4
Specify which of the four WEP encryption keys will be used to
encrypt transmitted packets.
.Pp
-Both 128-bit and 64-bit WEP have been broken.
+Note: Both 128-bit and 64-bit WEP have been broken.
See the BUGS section for details.
.It Fl i Ar iface Fl r Ar RTS threshold
Set the RTS/CTS threshold for a given interface.
@@ -365,24 +365,35 @@ better signal quality).
.Xr wi 4 ,
.Xr ifconfig 8
.Sh BUGS
-WEP has been broken.
-Do not use it.
-Use IPSEC instead.
-Do not trust access points.
+The WEP encryption method has been broken so that third parties
+can recover the keys in use relatively quickly at distances that are
+surprising to most people.
+Do not rely on WEP for anything but the most basic, remedial security.
+IPSEC will give you a higher level of security and should be used
+whenever possible.
+Do not trust access points or wireless machines that connect through
+them as they can provide no assurance that the traffic is legitimate.
+MAC addresses can easily be forged and should therefore not be used as
+the only access control.
.Pp
The attack on WEP is a passive attack, requiring only the ability to
sniff packets on the network.
The passive attack can be launched at a distance larger, up to many
miles, than one might otherwise expect given a specialized antenna
used in point to point applications.
-The attacker can recover the keys from a 128-bit WEP network after
-at most 5,000,000 or 6,000,000 packets.
+The attacker can recover the keys from a 128-bit WEP network with only
+5,000,000 to 6,000,000 packets.
While this may sound like a large number of packets, emperical
evidence suggests that this amount of traffic is generated in a few
hours on a partially loaded network.
+Once a key has been compromised, the only remedial action is to
+discontinue it and use a new key.
.Pp
See http://www.cs.rice.edu/~astubble/wep/wep_attack.html for details
of the attack.
+.Pp
+If you must use WEP, you are strongly encouraged to pick keys whose
+bytes are random and not confined to ASCII characters.
.Sh HISTORY
The
.Nm
OpenPOWER on IntegriCloud