aboutsummaryrefslogtreecommitdiffstats
path: root/doc/api.tex
diff options
context:
space:
mode:
authorlloyd <[email protected]>2008-01-24 14:38:03 +0000
committerlloyd <[email protected]>2008-01-24 14:38:03 +0000
commitd8b662914020dfef05411a3fc067659043176020 (patch)
tree64aea7aad02003200c2450f9ba642225462e0888 /doc/api.tex
parentaf07a773cc600d309a4b8cda0fd38006f0796f2d (diff)
Wrap to 80 columns
Diffstat (limited to 'doc/api.tex')
-rw-r--r--doc/api.tex14
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/api.tex b/doc/api.tex
index 212db77bb..7d848c711 100644
--- a/doc/api.tex
+++ b/doc/api.tex
@@ -1941,11 +1941,11 @@ to use is to create (or request) a CA certificate, which can be done by calling
the member function \function{CA\_key}. This should only be used when needed.
Other constraints can be set by calling the member functions
-\function{add\_constraints} and \function{add\_ex\_constraints}. The first takes
-a \type{Key\_Constraints} value, and replaces any previously set value. If no
-value is set, then the certificate key is marked as being valid for any usage.
-You can set it to any of the following (for more than one usage, OR them
-together): \type{DIGITAL\_SIGNATURE}, \type{NON\_REPUDIATION},
+\function{add\_constraints} and \function{add\_ex\_constraints}. The first
+takes a \type{Key\_Constraints} value, and replaces any previously set
+value. If no value is set, then the certificate key is marked as being valid
+for any usage. You can set it to any of the following (for more than one
+usage, OR them together): \type{DIGITAL\_SIGNATURE}, \type{NON\_REPUDIATION},
\type{KEY\_ENCIPHERMENT}, \type{DATA\_ENCIPHERMENT}, \type{KEY\_AGREEMENT},
\type{KEY\_CERT\_SIGN}, \type{CRL\_SIGN}, \type{ENCIPHER\_ONLY},
\type{DECIPHER\_ONLY}. Many of these have quite special semantics, so you
@@ -2704,8 +2704,8 @@ for use by applications.
Here, in a separate list, are the options which control which extension are
included in a newly generated X.509v3 certificate, and if they should be marked
-as critical extensions or not. Each one begins with ``x509/exts/'' (\ie, what is
-referred to as ``basic\_constraints'' below is actually
+as critical extensions or not. Each one begins with ``x509/exts/'' (\ie, what
+is referred to as ``basic\_constraints'' below is actually
``x509/exts/basic\_constraints''), and can take on a value of ``yes'', ``no'',
``noncritical'', or ``critical''. A value of ``no'' means the extension is not
included under any circumstances. A value of ``yes'' or ``noncritical'' (they