Update for OpenSSL 0.9.7. No assembler code at the moment. This

will follow.

1 files changed, 18 insertions, 2 deletions

diff --git a/secure/lib/libcrypto/man/crypto.3 b/secure/lib/libcrypto/man/crypto.3
index 38ef4b6..2152f83 100644
--- a/secure/lib/libcrypto/man/crypto.3
+++ b/secure/lib/libcrypto/man/crypto.3
@@ -1,5 +1,5 @@
 .\" Automatically generated by Pod::Man version 1.15
-.\" Tue Jul 30 09:22:00 2002
+.\" Mon Jan 13 19:28:59 2003
 .\"
 .\" Standard preamble:
 .\" ======================================================================
@@ -138,7 +138,7 @@
 .\" ======================================================================
 .\"
 .IX Title "crypto 3"
-.TH crypto 3 "0.9.6e" "2002-07-30" "OpenSSL"
+.TH crypto 3 "0.9.7" "2003-01-13" "OpenSSL"
 .UC
 .SH "NAME"
 crypto \- OpenSSL cryptographic library
@@ -187,6 +187,22 @@ pkcs7(3), pkcs12(3)
 bn(3), buffer(3), lhash(3),
 objects(3), stack(3),
 txt_db(3) 
+.SH "NOTES"
+.IX Header "NOTES"
+Some of the newer functions follow a naming convention using the numbers
+\&\fB0\fR and \fB1\fR. For example the functions:
+.PP
+.Vb 2
+\& int X509_CRL_add0_revoked(X509_CRL *crl, X509_REVOKED *rev);
+\& int X509_add1_trust_object(X509 *x, ASN1_OBJECT *obj);
+.Ve
+The \fB0\fR version uses the supplied structure pointer directly
+in the parent and it will be freed up when the parent is freed.
+In the above example \fBcrl\fR would be freed but \fBrev\fR would not.
+.PP
+The \fB1\fR function uses a copy of the supplied structure pointer
+(or in some cases increases its link count) in the parent and
+so both (\fBx\fR and \fBobj\fR above) should be freed up.
 .SH "SEE ALSO"
 .IX Header "SEE ALSO"
 openssl(1), ssl(3)