xref: /openbsd-src/lib/libcrypto/man/crypto.3 (revision 7350f337b9e3eb4461d99580e625c7ef148d107c)
1.\"	$OpenBSD: crypto.3,v 1.20 2019/06/06 01:06:59 schwarze Exp $
2.\"	OpenSSL a9c85cea Nov 11 09:33:55 2016 +0100
3.\"
4.\" This file was written by Ulf Moeller <ulf@openssl.org> and
5.\" Dr. Stephen Henson <steve@openssl.org>.
6.\" Copyright (c) 2000, 2002 The OpenSSL Project.  All rights reserved.
7.\"
8.\" Redistribution and use in source and binary forms, with or without
9.\" modification, are permitted provided that the following conditions
10.\" are met:
11.\"
12.\" 1. Redistributions of source code must retain the above copyright
13.\"    notice, this list of conditions and the following disclaimer.
14.\"
15.\" 2. Redistributions in binary form must reproduce the above copyright
16.\"    notice, this list of conditions and the following disclaimer in
17.\"    the documentation and/or other materials provided with the
18.\"    distribution.
19.\"
20.\" 3. All advertising materials mentioning features or use of this
21.\"    software must display the following acknowledgment:
22.\"    "This product includes software developed by the OpenSSL Project
23.\"    for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
24.\"
25.\" 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
26.\"    endorse or promote products derived from this software without
27.\"    prior written permission. For written permission, please contact
28.\"    openssl-core@openssl.org.
29.\"
30.\" 5. Products derived from this software may not be called "OpenSSL"
31.\"    nor may "OpenSSL" appear in their names without prior written
32.\"    permission of the OpenSSL Project.
33.\"
34.\" 6. Redistributions of any form whatsoever must retain the following
35.\"    acknowledgment:
36.\"    "This product includes software developed by the OpenSSL Project
37.\"    for use in the OpenSSL Toolkit (http://www.openssl.org/)"
38.\"
39.\" THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
40.\" EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
41.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
42.\" PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE OpenSSL PROJECT OR
43.\" ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
44.\" SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
45.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
46.\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
47.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
48.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
49.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
50.\" OF THE POSSIBILITY OF SUCH DAMAGE.
51.\"
52.Dd $Mdocdate: June 6 2019 $
53.Dt CRYPTO 3
54.Os
55.Sh NAME
56.Nm crypto
57.Nd OpenSSL cryptographic library
58.Sh DESCRIPTION
59The OpenSSL crypto library implements a wide range of cryptographic
60algorithms used in various Internet standards.
61The services provided by this library are used by the OpenSSL
62implementations of TLS and S/MIME, and they have also been used to
63implement SSH, OpenPGP, and other cryptographic standards.
64.Pp
65.Sy Symmetric ciphers
66including AES, Blowfish, CAST, Chacha20, IDEA, DES, RC2, and RC4
67are provided by the generic interface
68.Xr EVP_EncryptInit 3 .
69Low-level stand-alone interfaces include
70.Xr BF_set_key 3 ,
71.Xr DES_set_key 3 ,
72and
73.Xr RC4 3 .
74.Pp
75.Sy Public key cryptography and key agreement
76are provided by
77.Xr DH_new 3 ,
78.Xr X25519 3 ,
79.Xr DSA_new 3 ,
80.Xr ECDSA_SIG_new 3 ,
81.Xr RSA_new 3 ,
82and
83.Xr EVP_PKEY_new 3 .
84.Pp
85.Sy Certificates
86are handled by
87.Xr X509_new 3
88and
89.Xr X509v3_add_ext 3 .
90.Pp
91.Sy Authentication codes and hash functions
92offered include
93.Xr EVP_DigestInit 3 ,
94.Xr HMAC 3 ,
95.Xr MD4 3 ,
96.Xr MD5 3 ,
97.Xr RIPEMD160 3 ,
98.Xr SHA1 3 ,
99and
100.Xr SHA256 3 .
101.Pp
102.Sy Input, output, and data encoding
103facilities include
104.Xr ASN1_TYPE_get 3 ,
105.Xr BIO_new 3 ,
106.Xr evp 3 ,
107.Xr EVP_EncodeInit 3 ,
108.Xr PEM_read 3 ,
109.Xr PKCS7_encrypt 3 ,
110.Xr PKCS7_sign 3 ,
111.Xr PKCS12_create 3 ,
112and
113.Xr SMIME_write_PKCS7 3 .
114.Pp
115.Sy Auxiliary features include:
116.Bl -dash -compact
117.It
118configuration file handling: see
119.Xr OPENSSL_config 3
120.It
121error reporting: see
122.Xr ERR 3
123.It
124.Xr OCSP_REQUEST_new 3
125.It
126.Xr UI_new 3
127.El
128.Pp
129.Sy Internal utilities
130include
131.Xr BIO_f_buffer 3 ,
132.Xr BN_new 3 ,
133.Xr EC_GROUP_new 3 ,
134.Xr lh_new 3 ,
135and
136.Xr STACK_OF 3 .
137.Pp
138Some of the newer functions follow a naming convention using the numbers
139.Sq 0
140and
141.Sq 1 .
142For example consider the names of these functions:
143.Pp
144.Ft int
145.Fo X509_CRL_add0_revoked
146.Fa "X509_CRL *crl"
147.Fa "X509_REVOKED *rev"
148.Fc
149.br
150.Ft int
151.Fo X509_add1_trust_object
152.Fa "X509 *x"
153.Fa "ASN1_OBJECT *obj"
154.Fc
155.Pp
156The
157.Sq 0
158version uses the supplied structure pointer directly in the parent and
159it will be freed up when the parent is freed.
160In the above example
161.Fa crl
162would be freed but
163.Fa rev
164would not.
165.Pp
166The
167.Sq 1
168function uses a copy of the supplied structure pointer (or in some cases
169increases its link count) in the parent and so both
170.Pf ( Fa x
171and
172.Fa obj
173above) should be freed up.
174.Sh SEE ALSO
175.Xr openssl 1 ,
176.Xr ssl 3
177