summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* In x509_vfy.h rev. 1.26 2018/03/17 15:43:32, tb@ providedschwarze2018-04-021-6/+14
| | | | X509_STORE_get0_param(3); write the documentation from scratch.
* In x509_vfy.h rev. 1.25 2018/03/17 15:39:43, tb@ providedschwarze2018-04-021-4/+21
| | | | | X509_OBJECT_get_type(3). It is undocumented in OpenSSL, so write some documentation from scratch.
* When you replace an element in a sorted array with somethingschwarze2018-04-011-12/+4
| | | | | | | | | | | | | | | | arbitrarily different, the array is in general no longer sorted. This commit copies a small hidden bugfix from the OpenSSL commit https://github.com/openssl/openssl/commit/fbb7b33b the rest of which is merely cosmetics. I discovered the bug independently while documenting sk_find(3). Keep the library's idea of when an empty stack or a one-element stack is sorted and when it is not bug-compatible with OpenSSL, even though in fact, empty and one-element stacks are of course always sorted. OK beck@
* jsing@ points out to me that our X25519 interface was copied fromschwarze2018-03-301-98/+85
| | | | | | | | | | | | BoringSSL rather than from OpenSSL and that it is not hooked into evp(3). So delete all text from OpenSSL including the Copyright and license and replace it by some text assembled from comments in BoringSSL code and headers and some text written myself, all under ISC license. In particular, also describe X25519_keypair(3), add SYNOPSIS, RETURN VALUES, STANDARDS, and a reference to D. J. Bernsteins instructions on how to use the algorithm. Delete the text related to EVP_PKEY describing features we do not support.
* include more information about how to create keys;schwarze2018-03-301-6/+19
| | | | | from Matt Caswell <matt at openssl dot org> via OpenSSL commit f929439f Mar 15 12:19:16 2018 +0000
* Add one short sentence each from the new OpenSSL X509_STORE_add_cert(3)schwarze2018-03-302-4/+10
| | | | | | manual page, which is below the threshold of originality, so there is no need to change the Copyright headers. The rest of that page is less clear and less precise than what we already have in our various pages.
* Remove mention of link between message digests and public key algorithms.schwarze2018-03-292-16/+8
| | | | | | | | | | | | | The comment in EVP_DigestInit.pod is: "EVP_MD_pkey_type() returns the NID of the public key signing algorithm associated with this digest. For example EVP_sha1() is associated with RSA so this will return NID_sha1WithRSAEncryption. Since digests and signature algorithms are no longer linked this function is only retained for compatibility reasons." So there is no link anymore. From <paul dot dale at oracle dot com> via OpenSSL commit 79b49fb0 Mar 20 10:03:10 2018 +1000
* missing "const" in seven prototypes;schwarze2018-03-291-16/+16
| | | | | from Kurt Roeckx <kurt at roeckx dot be> via OpenSSL commit b38fa985 Mar 10 16:32:55 2018 +0100
* describe EC_POINT_get_affine_coordinates_GFp(3) andschwarze2018-03-291-3/+15
| | | | | | EC_POINT_get_affine_coordinates_GF2m(3); from David Benjamin <davidben at google dot com> via OpenSSL commit ddc1caac Mar 6 14:00:24 2018 -0500
* correct callback argument for BIO_puts(3);schwarze2018-03-291-4/+4
| | | | | from <Bernd dot Edlinger at hotmail dot de> via OpenSSL commit c911e5da Mar 19 14:20:53 2018 +0100
* BIO_get_mem_data(3) and BIO_get_mem_ptr(3) assign to *pp, not to pp;schwarze2018-03-291-5/+5
| | | | | from <Matthias dot St dot Pierre at ncp dash e dot com> via OpenSSL commit 36359cec Mar 7 14:37:23 2018 +0100
* spelling; from <Alex dot Gaynor at gmail dot com>schwarze2018-03-291-5/+5
| | | | via OpenSSL commit d47eaaf4 Mar 9 07:11:13 2018 -0500
* missing words; from Ivan Filenko <ivan dot filenko at protonmail dot com>schwarze2018-03-291-5/+5
| | | | via OpenSSL commit 4a56d2a3 Feb 25 16:49:27 2018 +0300
* found a complete archive of SSLeay-0.4 to SSLeay-0.8.1b tarballsschwarze2018-03-27150-647/+837
| | | | on the web, so fix up SSLeay HISTORY accordingly
* finish crypto HISTORY; mostly 1.1.0/6.3, but also various other fixesschwarze2018-03-2352-155/+289
|
* crypto HISTORY up to 1.0.2; researched from OpenSSL git and OpenBSD CVSschwarze2018-03-236-12/+41
|
* crypto HISTORY up to 1.0.1; researched from OpenSSL gitschwarze2018-03-2310-16/+79
|
* crypto HISTORY up to 1.0.0; researched from OpenSSL gitschwarze2018-03-2343-114/+299
|
* crypto HISTORY up to 0.9.8zh; researched from OpenSSL gitschwarze2018-03-233-4/+18
|
* crypto HISTORY up to 0.9.8h; researched from OpenSSL gitschwarze2018-03-237-14/+59
|
* crypto HISTORY up to 0.9.8; researched from OpenSSL gitschwarze2018-03-2329-68/+329
|
* crypto HISTORY up to 0.9.7h; researched from OpenSSL gitschwarze2018-03-226-10/+34
|
* crypto HISTORY up to 0.9.7; researched from OpenSSL gitschwarze2018-03-2251-134/+383
|
* crypto HISTORY up to 0.9.6h; researched from OpenSSL gitschwarze2018-03-221-2/+6
|
* crypto HISTORY up to 0.9.6c; researched from OpenSSL gitschwarze2018-03-222-5/+7
|
* crypto HISTORY up to 0.9.6a; researched from OpenSSL gitschwarze2018-03-221-2/+4
|
* crypto HISTORY up to 0.9.6; researched from OpenSSL gitschwarze2018-03-2219-36/+141
|
* crypto HISTORY up to 0.9.5; researched from OpenSSL gitschwarze2018-03-2248-140/+362
|
* Catch up after beck@ fixed autoconfiguration:schwarze2018-03-213-62/+55
| | | | | | | | | * Say more precisely what OPENSSL_config(3) and OPENSSL_no_config(3) do. * Revert the deprecation notice for them, nothing wrong with them. * Document OPENSSL_INIT_LOAD_CONFIG. * Deprecate OpenSSL_add_all_algorithms(3), it's now automatic. * Add OpenSSL_add_all_algorithms(3) HISTORY. Substantial feedback and OK beck@.
* crypto HISTORY up to 0.9.4; researched from OpenSSL gitschwarze2018-03-2112-25/+92
|
* crypto HISTORY up to 0.9.3; researched from OpenSSL gitschwarze2018-03-2121-43/+178
|
* crypto HISTORY up to OpenSSL 0.9.2b; researched from OpenSSL gitschwarze2018-03-2118-30/+134
|
* crypto HISTORY up to OpenSSL 0.9.1c; researched from OpenSSL gitschwarze2018-03-211-3/+6
|
* crypto HISTORY up to SSLeay 0.9.1; researched from OpenSSL gitschwarze2018-03-2117-34/+101
|
* x509_vfy.h HISTORY up to SSLeay 0.9.0; researched from OpenSSL gitschwarze2018-03-213-7/+14
|
* rsa.h HISTORY up to SSLeay 0.9.0; researched from OpenSSL gitschwarze2018-03-215-16/+20
|
* ripemd.h HISTORY up to SSLeay 0.9.0; researched from OpenSSL gitschwarze2018-03-211-3/+4
|
* objects.h HISTORY up to SSLeay 0.9.0; researched from OpenSSL gitschwarze2018-03-211-1/+3
|
* hmac.h HISTORY up to SSLeay 0.9.0; researched from OpenSSL gitschwarze2018-03-211-4/+6
|
* evp.h HISTORY up to SSLeay 0.9.0; researched from OpenSSL gitschwarze2018-03-213-10/+27
|
* err.h HISTORY up to SSLeay 0.9.0; researched from OpenSSL gitschwarze2018-03-213-18/+19
|
* dsa.h HISTORY up to SSLeay 0.9.0; researched from OpenSSL gitschwarze2018-03-211-6/+6
|
* crypto.c HISTORY up to SSLeay 0.9.0; researched from OpenSSL gitschwarze2018-03-211-5/+9
|
* bn.h HISTORY up to SSLeay 0.9.0; researched from OpenSSL gitschwarze2018-03-215-28/+32
|
* bio.h HISTORY up to SSLeay 0.9.0; researched from OpenSSL gitschwarze2018-03-215-15/+45
|
* blowfish.h HISTORY up to SSLeay 0.9.0; researched from OpenSSL gitschwarze2018-03-211-2/+6
|
* asn1.h HISTORY up to SSLeay 0.9.0; researched from OpenSSL gitschwarze2018-03-214-11/+27
|
* x509_vfy.h HISTORY up to SSLeay 0.8.1b; researched from OpenSSL gitschwarze2018-03-216-12/+49
|
* x509.h HISTORY up to SSLeay 0.8.1b; researched from OpenSSL gitschwarze2018-03-2135-77/+297
|
* stack.h HISTORY up to SSLeay 0.8.1b; researched from OpenSSL gitschwarze2018-03-211-6/+28
|
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-03-26 12:53:59 +0000