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/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