From nobody@FreeBSD.org  Thu Aug 23 02:49:45 2001
Return-Path: <nobody@FreeBSD.org>
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 7406D37B416
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 23 Aug 2001 02:49:41 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.11.4/8.11.4) id f7N9nfm28707;
	Thu, 23 Aug 2001 02:49:41 -0700 (PDT)
	(envelope-from nobody)
Message-Id: <200108230949.f7N9nfm28707@freefall.freebsd.org>
Date: Thu, 23 Aug 2001 02:49:41 -0700 (PDT)
From: Joseph Mallett <jmallett@xMach.org>
To: freebsd-gnats-submit@FreeBSD.org
Subject: random(4) manpage has typo
X-Send-Pr-Version: www-1.0

>Number:         29984
>Category:       docs
>Synopsis:       random(4) manpage has typo
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    dd
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Aug 23 02:50:01 PDT 2001
>Closed-Date:    Sat Nov 24 08:14:24 PST 2001
>Last-Modified:  Sat Nov 24 08:14:58 PST 2001
>Originator:     Joseph Mallett
>Release:        4.4-RC
>Organization:
xMach
>Environment:
NA
>Description:
random(4) manpage has the expression "worst case" in it, yet it is written as "worse case". It is common for people to pronounce it this way, yet as far as I know, the expression is 'worst case' as in 'worse case scenario' and 'in the worst case'. A patch is attached.
>How-To-Repeat:
man 4 random
>Fix:
Aphex% diff -u random.orig random.4
--- random.orig Thu Aug 23 09:47:24 2001
+++ random.4    Thu Aug 23 09:47:41 2001
@@ -94,7 +94,7 @@
 and thus have some success in guessing the output of the routine.
 Phil Karn (who devised this mechanism of using MD5 plus a counter
 to extract random numbers from an entropy pool) calls this
-"practical randomness", since in the worse case this is equivalent
+"practical randomness", since in the worst case this is equivalent
 to hashing MD5 with a counter and an undisclosed secret.  If MD5 is
 a strong cryptographic hash, this should be fairly resistant to attack.
 .Ss Exported interfaces \(em output

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->analyzed 
State-Changed-By: dd 
State-Changed-When: Thu Aug 23 14:19:24 PDT 2001 
State-Changed-Why:  
This only affects RELENG_4.  I'll fix it after the freeze. 


Responsible-Changed-From-To: freebsd-doc->dd 
Responsible-Changed-By: dd 
Responsible-Changed-When: Thu Aug 23 14:19:24 PDT 2001 
Responsible-Changed-Why:  

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=29984 
State-Changed-From-To: analyzed->closed 
State-Changed-By: dd 
State-Changed-When: Sat Nov 24 08:14:24 PST 2001 
State-Changed-Why:  
Patch applied, thanks!  (And sorry for the outrageous delay.) 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=29984 
>Unformatted:
