tweak the wep section somewhat, to bring it into line with what

we say for those devices which support wpa;

10 files changed, 94 insertions, 111 deletions

diff --git a/share/man/man4/acx.4 b/share/man/man4/acx.4
index 6ae0b791d13..87171f7efca 100644
--- a/share/man/man4/acx.4
+++ b/share/man/man4/acx.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: acx.4,v 1.31 2008/04/17 14:01:22 jmc Exp $
+.\"	$OpenBSD: acx.4,v 1.32 2008/07/29 17:03:35 jmc Exp $
 .\"
 .\" Copyright (c) 2006 Theo de Raadt.
 .\" Copyright (c) 2006 The DragonFly Project.  All rights reserved.
@@ -30,7 +30,7 @@
 .\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: April 17 2008 $
+.Dd $Mdocdate: July 29 2008 $
 .Os
 .Dt ACX 4
 .Sh NAME
@@ -80,16 +80,16 @@ capture packets from networks which it wouldn't normally have access to,
 or to scan for access points.
 .El
 .Pp
+The
 .Nm
-supports software WEP for ACX111 and hardware WEP for ACX100.
-Wired Equivalent Privacy (WEP) is the de facto encryption standard
-for wireless networks.
-It can be typically configured in one of three modes:
-no encryption; 40-bit encryption; or 104-bit encryption.
-Unfortunately, due to serious weaknesses in WEP protocol
-it is strongly recommended that it not be used as the
-sole mechanism to secure wireless communication.
-WEP is not enabled by default.
+driver can be configured to use
+Wireless Equivalent Privacy (WEP)
+in software for ACX111
+or in hardware for ACX100.
+It is strongly recommended that WEP
+not be used as the sole mechanism
+to secure wireless communication,
+due to serious weaknesses in it.
 .Pp
 The transmit speed is user-selectable or can be adapted automatically by the
 driver depending on the number of hardware transmission retries.
diff --git a/share/man/man4/an.4 b/share/man/man4/an.4
index 401667cf19f..672feb22a55 100644
--- a/share/man/man4/an.4
+++ b/share/man/man4/an.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: an.4,v 1.35 2008/04/17 14:01:22 jmc Exp $
+.\"	$OpenBSD: an.4,v 1.36 2008/07/29 17:03:35 jmc Exp $
 .\"
 .\" Copyright (c) 1997, 1998, 1999
 .\"	Bill Paul <wpaul@ee.columbia.edu>. All rights reserved.
@@ -32,7 +32,7 @@
 .\"
 .\" $FreeBSD: src/share/man/man4/an.4,v 1.5 2000/03/02 14:53:45 sheldonh Exp $
 .\"
-.Dd $Mdocdate: April 17 2008 $
+.Dd $Mdocdate: July 29 2008 $
 .Dt AN 4
 .Os
 .Sh NAME
@@ -105,16 +105,14 @@ capture packets from networks which it wouldn't normally have access to,
 or to scan for access points.
 .El
 .Pp
+The
 .Nm
-supports hardware WEP.
-Wired Equivalent Privacy (WEP) is the de facto encryption standard
-for wireless networks.
-It can be typically configured in one of three modes:
-no encryption; 40-bit encryption; or 104-bit encryption.
-Unfortunately, due to serious weaknesses in WEP protocol
-it is strongly recommended that it not be used as the
-sole mechanism to secure wireless communication.
-WEP is not enabled by default.
+driver can be configured to use hardware
+Wireless Equivalent Privacy (WEP).
+It is strongly recommended that WEP
+not be used as the sole mechanism
+to secure wireless communication,
+due to serious weaknesses in it.
 .Pp
 The
 .Nm
diff --git a/share/man/man4/ath.4 b/share/man/man4/ath.4
index 03888b6608b..7c12f4db7d6 100644
--- a/share/man/man4/ath.4
+++ b/share/man/man4/ath.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ath.4,v 1.40 2008/04/17 14:01:22 jmc Exp $
+.\"	$OpenBSD: ath.4,v 1.41 2008/07/29 17:03:35 jmc Exp $
 .\"     $NetBSD: ath.4,v 1.5 2004/07/03 16:58:18 mycroft Exp $
 .\"
 .\" Copyright (c) 2002, 2003 Sam Leffler, Errno Consulting
@@ -42,7 +42,7 @@
 .\" $FreeBSD: /repoman/r/ncvs/src/share/man/man4/ath.4,v 1.16 2004/02/18 08:30:08 maxim Exp $
 .\" parts from $FreeBSD: /repoman/r/ncvs/src/share/man/man4/ath_hal.4,v 1.7 2004/01/07 20:49:51 blackend Exp $
 .\"
-.Dd $Mdocdate: April 17 2008 $
+.Dd $Mdocdate: July 29 2008 $
 .Dt ATH 4
 .Os
 .Sh NAME
@@ -121,16 +121,14 @@ capture packets from networks which it wouldn't normally have access to,
 or to scan for access points.
 .El
 .Pp
+The
 .Nm
-supports hardware WEP.
-Wired Equivalent Privacy (WEP) is the de facto encryption standard
-for wireless networks.
-It can be typically configured in one of three modes:
-no encryption; 40-bit encryption; or 104-bit encryption.
-Unfortunately, due to serious weaknesses in WEP protocol
-it is strongly recommended that it not be used as the
-sole mechanism to secure wireless communication.
-WEP is not enabled by default.
+driver can be configured to use hardware
+Wireless Equivalent Privacy (WEP).
+It is strongly recommended that WEP
+not be used as the sole mechanism
+to secure wireless communication,
+due to serious weaknesses in it.
 .Pp
 AR5211 and AR5212 support the AES, TKIP, and Michael cryptographic
 operations required for WPA but at this time the driver does not support them.
diff --git a/share/man/man4/atu.4 b/share/man/man4/atu.4
index 1a8d5b64e95..5e9dbf53f2f 100644
--- a/share/man/man4/atu.4
+++ b/share/man/man4/atu.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: atu.4,v 1.33 2008/04/17 14:01:22 jmc Exp $
+.\" $OpenBSD: atu.4,v 1.34 2008/07/29 17:03:35 jmc Exp $
 .\"
 .\" Copyright (c) 1997, 1998, 1999
 .\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -30,7 +30,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
 .\" THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: April 17 2008 $
+.Dd $Mdocdate: July 29 2008 $
 .Dt ATU 4
 .Os
 .Sh NAME
@@ -71,16 +71,14 @@ Stations associate with a service set.
 However, actual connections between stations are peer-to-peer.
 .El
 .Pp
+The
 .Nm
-supports hardware WEP.
-Wired Equivalent Privacy (WEP) is the de facto encryption standard
-for wireless networks.
-It can be typically configured in one of three modes:
-no encryption; 40-bit encryption; or 104-bit encryption.
-Unfortunately, due to serious weaknesses in WEP protocol
-it is strongly recommended that it not be used as the
-sole mechanism to secure wireless communication.
-WEP is not enabled by default.
+driver can be configured to use hardware
+Wireless Equivalent Privacy (WEP).
+It is strongly recommended that WEP
+not be used as the sole mechanism
+to secure wireless communication,
+due to serious weaknesses in it.
 .Pp
 The
 .Nm
diff --git a/share/man/man4/atw.4 b/share/man/man4/atw.4
index cce4155727b..bd91b053899 100644
--- a/share/man/man4/atw.4
+++ b/share/man/man4/atw.4
@@ -1,4 +1,4 @@
-.\"     $OpenBSD: atw.4,v 1.27 2008/05/23 17:00:52 jmc Exp $
+.\"     $OpenBSD: atw.4,v 1.28 2008/07/29 17:03:35 jmc Exp $
 .\"	$NetBSD: atw.4,v 1.8 2004/06/06 04:05:49 wiz Exp $
 .\"
 .\" Copyright (c) 2003
@@ -28,7 +28,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
 .\" THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: May 23 2008 $
+.Dd $Mdocdate: July 29 2008 $
 .Dt ATW 4
 .Os
 .Sh NAME
@@ -88,18 +88,17 @@ Stations associate with a service set.
 However, actual connections between stations are peer-to-peer.
 .El
 .Pp
+The
 .Nm
-supports hardware WEP (though see
-.Sx BUGS
+driver can be configured to use hardware
+Wireless Equivalent Privacy (WEP)
+(though see
+.Sx BUGS ,
 below).
-Wired Equivalent Privacy (WEP) is the de facto encryption standard
-for wireless networks.
-It can be typically configured in one of three modes:
-no encryption; 40-bit encryption; or 104-bit encryption.
-Unfortunately, due to serious weaknesses in WEP protocol
-it is strongly recommended that it not be used as the
-sole mechanism to secure wireless communication.
-WEP is not enabled by default.
+It is strongly recommended that WEP
+not be used as the sole mechanism
+to secure wireless communication,
+due to serious weaknesses in it.
 .Pp
 The
 .Nm
diff --git a/share/man/man4/ipw.4 b/share/man/man4/ipw.4
index 8821856015f..ad9e17cdf13 100644
--- a/share/man/man4/ipw.4
+++ b/share/man/man4/ipw.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: ipw.4,v 1.26 2008/07/25 18:41:16 damien Exp $
+.\" $OpenBSD: ipw.4,v 1.27 2008/07/29 17:03:35 jmc Exp $
 .\"
 .\" Copyright (c) 2004
 .\"	Damien Bergamini <damien.bergamini@free.fr>. All rights reserved.
@@ -25,7 +25,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: July 25 2008 $
+.Dd $Mdocdate: July 29 2008 $
 .Os
 .Dt IPW 4
 .Sh NAME
@@ -68,16 +68,14 @@ capture packets from networks which it wouldn't normally have access to,
 or to scan for access points.
 .El
 .Pp
+The
 .Nm
-supports software WEP.
-Wired Equivalent Privacy (WEP) is the de facto encryption standard
-for wireless networks.
-It can be typically configured in one of three modes:
-no encryption; 40-bit encryption; or 104-bit encryption.
-Unfortunately, due to serious weaknesses in WEP protocol
-it is strongly recommended that it not be used as the
-sole mechanism to secure wireless communication.
-WEP is not enabled by default.
+driver can be configured to use software
+Wireless Equivalent Privacy (WEP).
+It is strongly recommended that WEP
+not be used as the sole mechanism
+to secure wireless communication,
+due to serious weaknesses in it.
 .Pp
 The
 .Nm
diff --git a/share/man/man4/iwi.4 b/share/man/man4/iwi.4
index 2045fdf81ea..297205fbdaa 100644
--- a/share/man/man4/iwi.4
+++ b/share/man/man4/iwi.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: iwi.4,v 1.31 2008/07/25 18:41:16 damien Exp $
+.\" $OpenBSD: iwi.4,v 1.32 2008/07/29 17:03:35 jmc Exp $
 .\"
 .\" Copyright (c) 2004
 .\"	Damien Bergamini <damien.bergamini@free.fr>. All rights reserved.
@@ -25,7 +25,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: July 25 2008 $
+.Dd $Mdocdate: July 29 2008 $
 .Os
 .Dt IWI 4
 .Sh NAME
@@ -67,16 +67,14 @@ capture packets from networks which it wouldn't normally have access to,
 or to scan for access points.
 .El
 .Pp
+The
 .Nm
-supports hardware WEP.
-Wired Equivalent Privacy (WEP) is the de facto encryption standard
-for wireless networks.
-It can be typically configured in one of three modes:
-no encryption; 40-bit encryption; or 104-bit encryption.
-Unfortunately, due to serious weaknesses in WEP protocol
-it is strongly recommended that it not be used as the
-sole mechanism to secure wireless communication.
-WEP is not enabled by default.
+driver can be configured to use hardware
+Wireless Equivalent Privacy (WEP).
+It is strongly recommended that WEP
+not be used as the sole mechanism
+to secure wireless communication,
+due to serious weaknesses in it.
 .Pp
 The
 .Nm
diff --git a/share/man/man4/pgt.4 b/share/man/man4/pgt.4
index b48c67a33e9..ccc85c68a79 100644
--- a/share/man/man4/pgt.4
+++ b/share/man/man4/pgt.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: pgt.4,v 1.26 2008/04/17 14:01:22 jmc Exp $
+.\"	$OpenBSD: pgt.4,v 1.27 2008/07/29 17:03:35 jmc Exp $
 .\"
 .\" Copyright (c) 2006 Theo de Raadt.
 .\" Copyright (c) 2006 The DragonFly Project.  All rights reserved.
@@ -30,7 +30,7 @@
 .\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: April 17 2008 $
+.Dd $Mdocdate: July 29 2008 $
 .Os
 .Dt PGT 4
 .Sh NAME
@@ -81,16 +81,14 @@ capture packets from networks which it wouldn't normally have access to,
 or to scan for access points.
 .El
 .Pp
+The
 .Nm
-supports hardware WEP.
-Wired Equivalent Privacy (WEP) is the de facto encryption standard
-for wireless networks.
-It can be typically configured in one of three modes:
-no encryption; 40-bit encryption; or 104-bit encryption.
-Unfortunately, due to serious weaknesses in WEP protocol
-it is strongly recommended that it not be used as the
-sole mechanism to secure wireless communication.
-WEP is not enabled by default.
+driver can be configured to use hardware
+Wireless Equivalent Privacy (WEP).
+It is strongly recommended that WEP
+not be used as the sole mechanism
+to secure wireless communication,
+due to serious weaknesses in it.
 .Pp
 The
 .Nm
diff --git a/share/man/man4/rtw.4 b/share/man/man4/rtw.4
index 53a27988c5a..0206d5b906c 100644
--- a/share/man/man4/rtw.4
+++ b/share/man/man4/rtw.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: rtw.4,v 1.32 2008/06/20 06:33:31 jmc Exp $
+.\"	$OpenBSD: rtw.4,v 1.33 2008/07/29 17:03:35 jmc Exp $
 .\"
 .\" Copyright (c) 2004 Jonathan Gray <jsg@openbsd.org>
 .\"
@@ -14,7 +14,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: June 20 2008 $
+.Dd $Mdocdate: July 29 2008 $
 .Dt RTW 4
 .Os
 .Sh NAME
@@ -62,16 +62,14 @@ capture packets from networks which it wouldn't normally have access to,
 or to scan for access points.
 .El
 .Pp
+The
 .Nm
-supports software WEP.
-Wired Equivalent Privacy (WEP) is the de facto encryption standard
-for wireless networks.
-It can be typically configured in one of three modes:
-no encryption; 40-bit encryption; or 104-bit encryption.
-Unfortunately, due to serious weaknesses in WEP protocol
-it is strongly recommended that it not be used as the
-sole mechanism to secure wireless communication.
-WEP is not enabled by default.
+driver can be configured to use software
+Wireless Equivalent Privacy (WEP).
+It is strongly recommended that WEP
+not be used as the sole mechanism
+to secure wireless communication,
+due to serious weaknesses in it.
 .Pp
 The
 .Nm
diff --git a/share/man/man4/wi.4tbl b/share/man/man4/wi.4tbl
index 17952d3cb1d..c5e9a91ea07 100644
--- a/share/man/man4/wi.4tbl
+++ b/share/man/man4/wi.4tbl
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: wi.4tbl,v 1.89 2008/04/17 14:01:22 jmc Exp $
+.\"	$OpenBSD: wi.4tbl,v 1.90 2008/07/29 17:03:35 jmc Exp $
 .\"
 .\" Copyright (c) 1997, 1998, 1999
 .\"	Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -32,7 +32,7 @@
 .\"
 .\"	$FreeBSD: wi.4,v 1.3 1999/05/22 16:12:43 wpaul Exp $
 .\"
-.Dd $Mdocdate: April 17 2008 $
+.Dd $Mdocdate: July 29 2008 $
 .Dt WI 4
 .Os
 .Sh NAME
@@ -104,16 +104,14 @@ This mode is not specified by the IEEE 802.11 standard and there
 may be problems interoperating with adapters manufactured by different vendors.
 .El
 .Pp
+The
 .Nm
-supports both software and hardware WEP.
-Wired Equivalent Privacy (WEP) is the de facto encryption standard
-for wireless networks.
-It can be typically configured in one of three modes:
-no encryption; 40-bit encryption; or 104-bit encryption.
-Unfortunately, due to serious weaknesses in WEP protocol
-it is strongly recommended that it not be used as the
-sole mechanism to secure wireless communication.
-WEP is not enabled by default.
+driver can be configured to use both software and hardware
+Wireless Equivalent Privacy (WEP).
+It is strongly recommended that WEP
+not be used as the sole mechanism
+to secure wireless communication,
+due to serious weaknesses in it.
 .Pp
 The Lucent WaveLAN/IEEE Silver and Gold cards as well as the Intersil
 and Symbol cards have support for WEP encryption.