From owner-freebsd-doc@FreeBSD.ORG Thu Aug 2 21:40:14 2012 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5095310656FF for ; Thu, 2 Aug 2012 21:40:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2072A8FC19 for ; Thu, 2 Aug 2012 21:40:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q72LeEYR016385 for ; Thu, 2 Aug 2012 21:40:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q72LeDaw016384; Thu, 2 Aug 2012 21:40:13 GMT (envelope-from gnats) Resent-Date: Thu, 2 Aug 2012 21:40:13 GMT Resent-Message-Id: <201208022140.q72LeDaw016384@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Alan Amesbury Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D06C106567A for ; Thu, 2 Aug 2012 21:34:49 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 4F5388FC1A for ; Thu, 2 Aug 2012 21:34:49 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id q72LYm6a064168 for ; Thu, 2 Aug 2012 21:34:48 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id q72LYm5g064167; Thu, 2 Aug 2012 21:34:48 GMT (envelope-from nobody) Message-Id: <201208022134.q72LYm5g064167@red.freebsd.org> Date: Thu, 2 Aug 2012 21:34:48 GMT From: Alan Amesbury To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: docs/170341: [patch] Minor grammatical errors in engine(3) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2012 21:40:14 -0000 >Number: 170341 >Category: docs >Synopsis: [patch] Minor grammatical errors in engine(3) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Thu Aug 02 21:40:13 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Alan Amesbury >Release: FreeBSD 9.0-RELEASE-p1 amd64 >Organization: University of Minnesota >Environment: FreeBSD [REDACTED] 9.0-RELEASE-p1 FreeBSD 9.0-RELEASE-p1 #0: Tue May 15 11:17:43 CDT 2012 root@[REDACTED]:/usr/obj/usr/src/sys/[REDACTED] amd64 >Description: /usr/src/secure/lib/libcrypto/man/engine.3 contains grammatical errors. >How-To-Repeat: Read engine(3). >Fix: Patch. Patch attached with submission follows: --- engine.3 2012-07-03 12:22:17.848305224 -0500 +++ /tmp/engine.3 2012-08-02 16:29:21.000000000 -0500 @@ -321,7 +321,7 @@ that the structure can not be deallocated until the reference is released. .PP However, a structural reference provides no guarantee that the \s-1ENGINE\s0 is -initiliased and able to use any of its cryptographic +initialised and able to use any of its cryptographic implementations. Indeed it's quite possible that most ENGINEs will not initialise at all in typical environments, as ENGINEs are typically used to support specialised hardware. To use an \s-1ENGINE\s0's functionality, you need a @@ -330,8 +330,8 @@ implicitly contains a structural reference as well \- however to avoid difficult-to-find programming bugs, it is recommended to treat the two kinds of reference independently. If you have a functional reference to an -\&\s-1ENGINE\s0, you have a guarantee that the \s-1ENGINE\s0 has been initialised ready to -perform cryptographic operations and will remain uninitialised +\&\s-1ENGINE\s0, you have a guarantee that the \s-1ENGINE\s0 has been initialised and is ready to +perform cryptographic operations, and will remain initialised until after you have released your reference. .PP \&\fIStructural references\fR @@ -534,7 +534,7 @@ .PP Here we'll assume we want to load and register all \s-1ENGINE\s0 implementations bundled with OpenSSL, such that for any cryptographic algorithm required by -OpenSSL \- if there is an \s-1ENGINE\s0 that implements it and can be initialise, +OpenSSL \- if there is an \s-1ENGINE\s0 that implements it and can be initialised, it should be used. The following code illustrates how this can work; .PP .Vb 4 >Release-Note: >Audit-Trail: >Unformatted: