summaryrefslogtreecommitdiff
path: root/lib/libcrypto/man/d2i_X509.3
diff options
context:
space:
mode:
authorJason McIntyre <jmc@cvs.openbsd.org>2016-12-08 20:22:09 +0000
committerJason McIntyre <jmc@cvs.openbsd.org>2016-12-08 20:22:09 +0000
commit8dae1b2eb5b30a3f6708b94afff464da52fee92a (patch)
tree6deeae29690471a393d58700922d2e16c9c396c1 /lib/libcrypto/man/d2i_X509.3
parentb08c1b4d87c8aa59c445608d38f4a51ee3945550 (diff)
various cleanup;
Diffstat (limited to 'lib/libcrypto/man/d2i_X509.3')
-rw-r--r--lib/libcrypto/man/d2i_X509.318
1 files changed, 10 insertions, 8 deletions
diff --git a/lib/libcrypto/man/d2i_X509.3 b/lib/libcrypto/man/d2i_X509.3
index 916fdb80051..7ca3abf2d96 100644
--- a/lib/libcrypto/man/d2i_X509.3
+++ b/lib/libcrypto/man/d2i_X509.3
@@ -1,4 +1,4 @@
-.\" $OpenBSD: d2i_X509.3,v 1.3 2016/12/05 20:39:08 schwarze Exp $
+.\" $OpenBSD: d2i_X509.3,v 1.4 2016/12/08 20:22:08 jmc Exp $
.\" OpenSSL 94480b57 Sep 12 23:34:41 2009 +0000
.\"
.\" This file was written by Dr. Stephen Henson <steve@openssl.org>.
@@ -49,12 +49,14 @@
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
.\" OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
-.Dd $Mdocdate: December 5 2016 $
+.Dd $Mdocdate: December 8 2016 $
.Dt D2I_X509 3
.Os
.Sh NAME
.Nm d2i_X509 ,
+.Nm d2i_X509_AUX ,
.Nm i2d_X509 ,
+.Nm i2d_X509_AUX ,
.Nm d2i_X509_bio ,
.Nm d2i_X509_fp ,
.Nm i2d_X509_bio ,
@@ -136,7 +138,7 @@ contains a valid
.Vt X509
structure and an attempt is made to reuse it.
This "reuse" capability is present for historical compatibility,
-but its use is strongly discouraged, see the
+but its use is strongly discouraged; see the
.Sx BUGS
and
.Sx RETURN VALUES
@@ -223,7 +225,7 @@ The letters
.Sy i
and
.Sy d
-in for example
+in, for example,
.Fn i2d_X509
stand for "internal" (that is an internal C structure) and "DER",
so that
@@ -264,8 +266,8 @@ See the
section for some common errors.
.Pp
The reason for the auto increment behaviour is to reflect a typical
-usage of ASN1 functions: after one structure is encoded or decoded,
-another will processed after it.
+usage of ASN.1 functions: after one structure is encoded or decoded,
+another will be processed after it.
.Sh RETURN VALUES
.Fn d2i_X509 ,
.Fn d2i_X509_bio ,
@@ -308,7 +310,7 @@ p = buf;
i2d_X509(x, &p);
.Ed
.Pp
-If you are using OpenSSL 0.9.7 or later then this can be simplified to:
+Using OpenSSL 0.9.7 or later this can be simplified to:
.Bd -literal -offset indent
int len;
unsigned char *buf;
@@ -386,7 +388,7 @@ may well crash.
The auto allocation feature (setting
.Fa buf
to
-.Dv NULL
+.Dv NULL )
only works on OpenSSL 0.9.7 and later.
Attempts to use it on earlier versions will typically cause a
segmentation violation.