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

we say for those devices which support wpa;

1 files changed, 9 insertions, 11 deletions

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