diff options
author | schwarze <> | 2018-03-17 18:52:42 +0000 |
---|---|---|
committer | schwarze <> | 2018-03-17 18:52:42 +0000 |
commit | 1df6e36c9d7eff0320ef36b1b8f08614c168f15f (patch) | |
tree | b78b9cffdc705671413f909986fcefbd779b7c4b /src/lib/libcrypto/man/OPENSSL_init_crypto.3 | |
parent | 6f8df959b6c5413c67db6629ba3ad7806ac55138 (diff) | |
download | openbsd-1df6e36c9d7eff0320ef36b1b8f08614c168f15f.tar.gz openbsd-1df6e36c9d7eff0320ef36b1b8f08614c168f15f.tar.bz2 openbsd-1df6e36c9d7eff0320ef36b1b8f08614c168f15f.zip |
In crypto.h rev. 1.43 and ssl.h rev. 1.153 2018/03/17 16:20:01, beck@
provided OPENSSL_init_crypto(3) and OPENSSL_init_ssl(3).
Write the documentation from scratch
because the text OpenSSL provides is full of bloat.
Diffstat (limited to 'src/lib/libcrypto/man/OPENSSL_init_crypto.3')
-rw-r--r-- | src/lib/libcrypto/man/OPENSSL_init_crypto.3 | 77 |
1 files changed, 77 insertions, 0 deletions
diff --git a/src/lib/libcrypto/man/OPENSSL_init_crypto.3 b/src/lib/libcrypto/man/OPENSSL_init_crypto.3 new file mode 100644 index 0000000000..27c60561fe --- /dev/null +++ b/src/lib/libcrypto/man/OPENSSL_init_crypto.3 | |||
@@ -0,0 +1,77 @@ | |||
1 | .\" $OpenBSD: OPENSSL_init_crypto.3,v 1.1 2018/03/17 18:52:42 schwarze Exp $ | ||
2 | .\" Copyright (c) 2018 Ingo Schwarze <schwarze@openbsd.org> | ||
3 | .\" | ||
4 | .\" Permission to use, copy, modify, and distribute this software for any | ||
5 | .\" purpose with or without fee is hereby granted, provided that the above | ||
6 | .\" copyright notice and this permission notice appear in all copies. | ||
7 | .\" | ||
8 | .\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES | ||
9 | .\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF | ||
10 | .\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR | ||
11 | .\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES | ||
12 | .\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN | ||
13 | .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF | ||
14 | .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. | ||
15 | .\" | ||
16 | .Dd $Mdocdate: March 17 2018 $ | ||
17 | .Dt OPENSSL_INIT_CRYPTO 3 | ||
18 | .Os | ||
19 | .Sh NAME | ||
20 | .Nm OPENSSL_init_crypto | ||
21 | .Nd initialise the crypto library | ||
22 | .Sh SYNOPSIS | ||
23 | .In openssl/crypto.h | ||
24 | .Ft int | ||
25 | .Fo OPENSSL_init_crypto | ||
26 | .Fa "uint64_t options" | ||
27 | .Fa "const void *dummy" | ||
28 | .Fc | ||
29 | .Sh DESCRIPTION | ||
30 | If | ||
31 | .Fn OPENSSL_init_crypto | ||
32 | is called before any other crypto or ssl functions, the crypto | ||
33 | library is initialised by allocating various internal resources. | ||
34 | Unless the | ||
35 | .Dv OPENSSL_INIT_NO_LOAD_CONFIG | ||
36 | bit is set in the | ||
37 | .Fa options | ||
38 | argument, the default | ||
39 | .Xr openssl.cnf 5 | ||
40 | configuration file is also loaded as documented in | ||
41 | .Xr OPENSSL_config 3 . | ||
42 | .Pp | ||
43 | The other | ||
44 | .Fa options | ||
45 | flags defined by OpenSSL are all ignored by LibreSSL. | ||
46 | The | ||
47 | .Fa dummy | ||
48 | argument has no effect. | ||
49 | .Pp | ||
50 | Calling this function is almost never useful because it is internally | ||
51 | called with an | ||
52 | .Fa options | ||
53 | argument of 0 by those functions in the crypto and ssl libraries | ||
54 | that require it. | ||
55 | It is safest to assume that any function may do so. | ||
56 | .Pp | ||
57 | If this function is called more than once, none of the calls except | ||
58 | the first one have any effect. | ||
59 | .Sh RETURN VALUES | ||
60 | .Fn OPENSSL_init_crypto | ||
61 | is intended to return 1 on success or 0 on error. | ||
62 | .Sh SEE ALSO | ||
63 | .Xr CONF_modules_load_file 3 , | ||
64 | .Xr OPENSSL_init_ssl 3 , | ||
65 | .Xr openssl.cnf 5 | ||
66 | .Sh HISTORY | ||
67 | .Fn OPENSSL_init_crypto | ||
68 | first appeared in OpenSSL 1.1.0. | ||
69 | .Sh BUGS | ||
70 | .Fn OPENSSL_init_crypto | ||
71 | silently ignores almost all kinds of errors. | ||
72 | In particular, if memory allocation fails, initialisation is likely | ||
73 | to remain incomplete, the library may be in an inconsistent internal | ||
74 | state, but the return value will usually indicate success anyway. | ||
75 | There is no way for the application program to find out whether | ||
76 | library initialisation is actually complete, nor to get back to a | ||
77 | consistent state if it isn't. | ||