openbsd/src/lib/libcrypto/crypto.h, branch OPENBSD_6_8_BASEA mirror of https://github.com/libressl/openbsd.git
https://git.lua4.win/openbsd/atom?h=OPENBSD_6_8_BASE2019-01-19T01:07:00+00:00Partial port of EC_KEY_METHOD from OpenSSL 1.1.2019-01-19T01:07:00+00:00tb2019-01-19T01:07:00+00:00urn:sha1:aa769d92fad41004606a446424dde716784d7854
This commit adds init/free, support for signing, setting and
getting the method, engine support as well as extra data.
from markus
Add back a few missing compatibility stubs2018-11-11T16:32:28+00:00bcook2018-11-11T16:32:28+00:00urn:sha1:8a99f7096d5d13dfe9e814a08cb0a206eb8d0bbc
ok beck@
Add automatic threading initialization for libcrypto.2018-11-11T06:41:28+00:00bcook2018-11-11T06:41:28+00:00urn:sha1:3c41ae7ec959c3c608931951c8655a0e1df18696
This implements automatic thread support initialization in libcrypto.
This does not remove any functions from the ABI, but does turn them into
no-ops. Stub implementations of pthread_mutex_(init|lock|unlock) are
provided for ramdisks.
This does not implement the new OpenSSL 1.1 thread API internally,
keeping the original CRYTPO_lock / CRYPTO_add_lock functions for library
locking. For -portable, crypto_lock.c can be reimplemented with
OS-specific primitives as needed.
ok beck@, tb@, looks sane guenther@
Let CRYPTO_mem_leaks{,_fp,_cb}() return -1.2018-08-24T19:16:03+00:00tb2018-08-24T19:16:03+00:00urn:sha1:17fd6127db3f4731a9a58d39b41ce040a426348e
These functions are no-ops. Their signature was changed by OpenSSL
to allow error checking. This way we return an error and do not
indicate the (non-)existence of memory leaks.
tested in a bulk by sthen
ok jsing
Use recallocarray() instead of OPENSSL_realloc_clean().2018-05-13T13:48:08+00:00jsing2018-05-13T13:48:08+00:00urn:sha1:675abe1d8052e9013aafab06d42a244160518f8c
Also place all of the OPENSSL_* memory related prototypes under #ifndef
LIBRESSL_INTERNAL.
ok beck@ tb@
Correct mistake of loading the default openssl.conf by default during autoinit.2018-03-19T03:35:38+00:00beck2018-03-19T03:35:38+00:00urn:sha1:02fd65d9fc788d4e8e18c251840f300031577d70
This brings in the OPENSSL_INIT_LOAD_CONFIG flag with the same semantics as
OpenSSL. As a result, by default the openssl.conf file is not loaded during
autoinit, which makes autoinit safe for pledge(stdio).
ok jsing@
Fix a typo: OPENSSL_INIT_LOAD_CONFIG doesn't have double underbars.2018-03-18T01:39:26+00:00tb2018-03-18T01:39:26+00:00urn:sha1:2552f59ff7bcc95ba306163889c5909fba197582
Found via port build failures reported by sthen.
ok jsing
Bring in compatibility for OpenSSL 1.1 style init functions.2018-03-17T16:20:01+00:00beck2018-03-17T16:20:01+00:00urn:sha1:035770aca4c8c1f0d36f1b8da62c9e1fb9a4f09b
This adds OPENSSL_init_crypto and OPENSSL_init_ssl, as well
thread safety modifications for the existing LibreSSL init
functions. The initialization routines are called automatically
by the normal entry points into the library, as in newer OpenSSL
ok jsing@, nits by tb@ and deraadt@
Start providing parts of the OpenSSL 1.1 API.2018-02-14T16:32:06+00:00jsing2018-02-14T16:32:06+00:00urn:sha1:595ecf011ce6c3ad8ff0cdae736f28693c08ca35
This will ease the burden on ports and others trying to make software
work with LibreSSL, while avoiding #ifdef mazes. Note that we are not
removing 1.0.1 API or making things opaque, hence software written to
use the older APIs will continue to work, as will software written to
use the 1.1 API (as more functionality become available).
Discussed at length with deraadt@ and others.
Stop calling OPENSSL_init() internally, since it is a no-op. Also place2017-04-29T21:48:44+00:00jsing2017-04-29T21:48:44+00:00urn:sha1:1de47e5fe8ef45dc6638449b6a0decdcf07cc840
it under #ifndef LIBRESSL_INTERNAL.
ok beck@