summaryrefslogtreecommitdiffstats
path: root/secure/lib/libcrypto/man/engine.3
diff options
context:
space:
mode:
Diffstat (limited to 'secure/lib/libcrypto/man/engine.3')
-rw-r--r--secure/lib/libcrypto/man/engine.310
1 files changed, 5 insertions, 5 deletions
diff --git a/secure/lib/libcrypto/man/engine.3 b/secure/lib/libcrypto/man/engine.3
index 5670516..cdf7a01 100644
--- a/secure/lib/libcrypto/man/engine.3
+++ b/secure/lib/libcrypto/man/engine.3
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.35
+.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.37
.\"
.\" Standard preamble:
.\" ========================================================================
@@ -129,7 +129,7 @@
.\" ========================================================================
.\"
.IX Title "engine 3"
-.TH engine 3 "2007-03-15" "0.9.8e" "OpenSSL"
+.TH engine 3 "2009-06-14" "0.9.8k" "OpenSSL"
.SH "NAME"
engine \- ENGINE cryptographic module support
.SH "SYNOPSIS"
@@ -351,7 +351,7 @@ Due to the modular nature of the \s-1ENGINE\s0 \s-1API\s0, pointers to ENGINEs n
treated as handles \- ie. not only as pointers, but also as references to
the underlying \s-1ENGINE\s0 object. Ie. one should obtain a new reference when
making copies of an \s-1ENGINE\s0 pointer if the copies will be used (and
-released) independantly.
+released) independently.
.PP
\&\s-1ENGINE\s0 objects have two levels of reference-counting to match the way in
which the objects are used. At the most basic level, each \s-1ENGINE\s0 pointer is
@@ -368,7 +368,7 @@ support specialised hardware. To use an \s-1ENGINE\s0's functionality, you need
specialised form of structural reference, because each functional reference
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 independantly. If you have a functional reference to an
+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
until after you have released your reference.
@@ -767,7 +767,7 @@ extension).
The \s-1ENGINE\s0 \s-1API\s0 and internal architecture is currently being reviewed. Slated for
possible release in 0.9.8 is support for transparent loading of \*(L"dynamic\*(R"
ENGINEs (built as self-contained shared\-libraries). This would allow \s-1ENGINE\s0
-implementations to be provided independantly of OpenSSL libraries and/or
+implementations to be provided independently of OpenSSL libraries and/or
OpenSSL-based applications, and would also remove any requirement for
applications to explicitly use the \*(L"dynamic\*(R" \s-1ENGINE\s0 to bind to shared-library
implementations.
OpenPOWER on IntegriCloud