summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Reference the related accessor EVP_PKEY_get0_asn1(3).schwarze2018-05-131-5/+6
| | | | More logical ordering of EVP_PKEY_base_id(3) and EVP_PKEY_id(3) while here.
* Document EVP_PKEY_get0_asn1(3), it is declared in <openssl/evp.h>.schwarze2018-05-131-4/+13
| | | | | | | | | | It makes no sense to have method enumerators public, but the function to retrieve the method of a specific public key undocumented. Besides, it is confusing to have EVP_PKEY_asn1_get0(3) documented without mentioning the very different EVP_PKEY_get0_asn1(3). Remove a duplicate .Xr while here, and reference the related accessor EVP_PKEY_base_id(3). Triggered by tb@ adding a const qualifier to the argument.
* Document EVP_PKEY_bits(3).schwarze2018-05-132-7/+18
| | | | | | | It is clearly public because it is declared in <openssl/evp.h>, refenced from EVP_PKEY_asn1_set_public(3), and similar to the documented functions DH_bits(3) and RSA_bits(3). Triggered by tb@ adding a const qualifier to its argument.
* In pkcs12.h rev. 1.18 2018/05/13 13:46:55, tb@ added const qualifiersschwarze2018-05-131-4/+4
| | | | to the "pass" and "name" arguments of PKCS12_create(3). Adjust the manual.
* In pem.h rev. 1.18 2018/05/13 10:47:54, tb@ added const qualifiersschwarze2018-05-131-7/+7
| | | | | to the "name", "header", and "data" arguments of PEM_write(3) and PEM_write_bio(3). Adjust the manual.
* In ocsp.h rev. 1.15 2018/05/13 10:42:03, tb@ added const qualifiersschwarze2018-05-132-6/+6
| | | | | to the "url" argument of OCSP_crlID_new(3) and to the "urls" argument of OCSP_url_svcloc_new(3). Adjust the manuals.
* In x509.h rev. 1.49 2018/05/13 10:36:35, tb@ added a const qualifierschwarze2018-05-131-4/+4
| | | | | to the argument of X509_get_subject_name(3) and X509_get_issuer_name(3). Adjust the manual.
* In ocsp.h rev. 1.14 2018/05/13 10:30:52, tb@ added const qualifiersschwarze2018-05-131-5/+5
| | | | to the arguments of OCSP_cert_id_new(3). Adjust the manual.
* In x509.h rev. 1.48 2018/05/13 10:25:06, tb@ added a const qualifierschwarze2018-05-131-3/+3
| | | | to the "obj" argument of X509v3_get_ext_by_OBJ(3). Adjust the manual.
* In evp.h rev. 1.60 2018/05/13 06:35:10, tb@ added a const qualifierschwarze2018-05-131-3/+3
| | | | to the "sig" argument of EVP_DigestVerifyFinal(3). Adjust the manual.
* In bio.h rev. 1.43 2018/05/12 18:51:59, tb@ added a const qualifierschwarze2018-05-123-8/+8
| | | | | to the argument of BIO_new_accept(3), BIO_new_connect(3), and BIO_new_mem_buf(3). Update the documentation.
* In bio.h rev. 1.42 2018/05/12 17:47:53, tb@ added a const qualifierschwarze2018-05-121-3/+3
| | | | to return value of BIO_s_mem(3). Update the manual page.
* In evp.h rev. 1.59 2018/05/02 15:51:41, tb@ added a const qualifierschwarze2018-05-023-9/+9
| | | | | to the return value of BIO_f_base64(3), BIO_f_cipher(3), and BIO_f_base64(3). Update the documentation.
* In x509.h rev. 1.46 2018/05/01 19:01:28, tb@ added const qualifiersschwarze2018-05-012-6/+6
| | | | to some function arguments. Update the documentation.
* In bio.h rev. 1.41 2018/05/01 13:29:09, tb@ added const qualifiersschwarze2018-05-019-28/+28
| | | | to the prototypes of several functions. Update the documentation.
* In view of the recent BN_FLG_CONSTTIME vulnerabilities in OpenSSL,schwarze2018-04-294-28/+104
| | | | | | | | | | | | | | | | carefully document constant time vs. non-constant time operation of BN_div(3), BN_mod_exp(3), and BN_mod_inverse(3). Until the work that is required on the ill-designed BN_exp(3) and BN_gcd(3) interfaces can be undertaken, also document the imperfections in their behaviour, for now. Finally, mention BN_mod_exp(3) behaviour for even moduli. Delete the vague statement about some functions automatically setting BN_FLG_CONSTTIME. It created a false sense of security. Do not rely on it: not all relevant functions do that. Topic brought up by beck@, significant feedback and OK jsing@.
* In asn1.h rev. 1.46 2018/04/25 11:48:21, tb@ added const qualifiersschwarze2018-04-257-30/+30
| | | | | to some parameters of some functions. Update the documentation. Add a few additional missing const qualifiers while here.
* Document the "f" callback argument that tb@ asked about.schwarze2018-04-191-2/+16
| | | | | While here, include a patch from tb@ adding the missing return type to ENGINE_ctrl() in the SYNOPSIS.
* tweak previous;jmc2018-04-181-2/+3
|
* SEE ALSO and HISTORYschwarze2018-04-1812-26/+301
|
* delete engine(3); nothing of value left in that pageschwarze2018-04-182-537/+1
|
* link to ENGINE_register_RSA(3) rather than engine(3)schwarze2018-04-181-8/+7
|
* * Document DH_up_ref(3), DSA_up_ref(3), and RSA_up_ref(3).schwarze2018-04-183-16/+73
| | | | | | * Correct documentation of DH_new(3), DH_free(3), DSA_new(3), DSA_free(3), RSA_new(3), and RSA_free(3) with respect to reference counting. * Stop referencing engine(3).
* * Make the description of method selection simpler, more precise,schwarze2018-04-182-128/+67
| | | | | | | and more concise. * Correct the description of the return values of DH_set_method(3) and DSA_set_method(3). * Stop referencing engine(3).
* * Do not document the non-existent function RSA_null_method(3).schwarze2018-04-181-105/+43
| | | | | | | | | | * Add three missing const qualifiers to function prototypes. * Correct the argument type of RSA_new_method(3). * Remove duplicate decsription of RSA_flags(3) and RSA_new_method(3). * Make the description of method selection simpler, more precise, and more concise. * Correct description of the return value of RSA_set_method(3). * Stop referencing engine(3).
* add a few new sentences regarding the big pictureschwarze2018-04-152-2/+15
|
* Rewrite the ENGINE_*(3) documentation from scratch - step 2,schwarze2018-04-158-395/+633
| | | | | | covering the remaining functions that were documented in engine(3), except for seven functions that are completely pointless and that were merely listed but not really documented.
* Rewrite the ENGINE_*(3) documentation from scratch (step 1,schwarze2018-04-1510-530/+1303
| | | | | covering 60% of the documented functions). The old, abominable engine(3) manual page shall die soon.
* In eng_lib.c rev. 1.14 2018/04/14 07:18:37, tb@ allowed ENGINE_free(3)schwarze2018-04-141-53/+46
| | | | | | to accept a NULL argument. Document that. While here, make the related sentences more precise and less verbose. Tweaks and OK tb@.
* sort the list of data structures and add the missing ECDH and ECDSA;schwarze2018-04-081-57/+13
| | | | | triggered by OpenSSL commit a73d990e Feb 27 19:02:24 2018 +0100, but with different content
* tweak previous;jmc2018-04-071-4/+4
|
* Correct man page for OpenSSL_no_config() to indicate that itbeck2018-04-071-4/+8
| | | | | suppresses any future config file loading. ok schwarze@ with a nit from jsing@
* tweak previous;jmc2018-04-071-8/+8
|
* poison for X509_VERIFY_PARAM'sbeck2018-04-061-14/+53
| | | | | | | | | | | | Tighten up checks for various X509_VERIFY_PARAM functions, and allow for the verify param to be poisoned (preculding future successful cert validation) if the setting of host, ip, or email for certificate validation fails. (since many callers do not check the return code in the wild and blunder along anyway) Inspired by some discussions with Adam Langley. ok jsing@
* Typo: typdef -> typedef.tb2018-04-031-3/+3
| | | | From Edgar Pettijohn
* 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
|
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-03-28 18:11:05 +0000