mirror of
https://github.com/openssl/openssl.git
synced 2024-11-27 05:21:51 +08:00
a047435774
RT1556: doc/crypto/threads.pod
RT2024: Missing pages mentioned in crypto.pod
RT2890: Wrong size in ERR_string_error description.
RT3461: Better description of PEM Encryption
(Jeffrey Walton <noloader@gmail.com>)
Also, fix up formatting and removed some code examples
that encourage unsafe patterns, like unencrypted private
keys (Rich Salz)
RT4240: Document some speed flags (Tomas Mraz <tmraz@redhat.com>)
RT4260: Fix return value doc for X509_REQ_sign and X509_sign
(Laetitia Baudoin <lbaudoin@google.com>)
Reviewed-by: Emilia Käsper <emilia@openssl.org>
50 lines
1.4 KiB
Plaintext
50 lines
1.4 KiB
Plaintext
=pod
|
|
|
|
=head1 NAME
|
|
|
|
crypto - OpenSSL cryptographic library
|
|
|
|
=head1 SYNOPSIS
|
|
|
|
=head1 DESCRIPTION
|
|
|
|
The OpenSSL B<crypto> library implements a wide range of cryptographic
|
|
algorithms used in various Internet standards. The services provided
|
|
by this library are used by the OpenSSL implementations of SSL, TLS
|
|
and S/MIME, and they have also been used to implement SSH, OpenPGP, and
|
|
other cryptographic standards.
|
|
|
|
=head1 OVERVIEW
|
|
|
|
B<libcrypto> consists of a number of sub-libraries that implement the
|
|
individual algorithms.
|
|
|
|
The functionality includes symmetric encryption, public key
|
|
cryptography and key agreement, certificate handling, cryptographic
|
|
hash functions, cryptographic pseudo-random number generator, and
|
|
various utilities.
|
|
|
|
See the individual manual pages for details.
|
|
|
|
=head1 NOTES
|
|
|
|
Some of the newer functions follow a naming convention using the numbers
|
|
B<0> and B<1>. For example the functions:
|
|
|
|
int X509_CRL_add0_revoked(X509_CRL *crl, X509_REVOKED *rev);
|
|
int X509_add1_trust_object(X509 *x, ASN1_OBJECT *obj);
|
|
|
|
The B<0> 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 B<crl> would be freed but B<rev> would not.
|
|
|
|
The B<1> function uses a copy of the supplied structure pointer
|
|
(or in some cases increases its link count) in the parent and
|
|
so both (B<x> and B<obj> above) should be freed up.
|
|
|
|
=head1 SEE ALSO
|
|
|
|
L<openssl(1)>, L<ssl(3)>
|
|
|
|
=cut
|