openbsd/src/lib/libcrypto/man/DH_new.3, branch OPENBSD_7_9 A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9 2025-06-08T22:40:31+00:00 .Lb libcrypto ; OK tb@ 2025-06-08T22:40:31+00:00 schwarze 2025-06-08T22:40:31+00:00 urn:sha1:8be86af02fed1bda350c8dd14ee064cb66e3b0f5 add a few .Xr links to new manual pages 2022-07-13T21:51:35+00:00 schwarze 2022-07-13T21:51:35+00:00 urn:sha1:eecf69d021b6c6b9ed968129fcb1281df6b2be03 delete references to ERR pages from SEE ALSO where such 2019-06-10T14:58:48+00:00 schwarze 2019-06-10T14:58:48+00:00 urn:sha1:b783ba28c4b47eb204506e8af355d28ef6e67dec references were already given below RETURN VALUES right above add links back to crypto(3) to function group entry pages 2019-06-10T09:49:48+00:00 schwarze 2019-06-10T09:49:48+00:00 urn:sha1:56ffd9f2668f101af36752838043714323fc3351 and to isolated obsolete pages; OK bcook@ jmc@ Tree structure for manual pages: crypto(3) links to 33 function 2019-06-06T01:06:59+00:00 schwarze 2019-06-06T01:06:59+00:00 urn:sha1:580f04977d3a77664477818e7264e008d1ba5843 group pages, and these link on to all their second-level subpages. Only a handful of second-level pages have third-level subpages. So all crypto pages can now be reached from the www.libressl.org frontpage via at most four clicks, in most cases three clicks. Also link back from leaf pages to their respective group pages and add a couple of additional links between related pages. Triggered by a question from deraadt@. OK jmc@ tb@ * Document DH_up_ref(3), DSA_up_ref(3), and RSA_up_ref(3). 2018-04-18T01:11:45+00:00 schwarze 2018-04-18T01:11:45+00:00 urn:sha1:e8960e346c538349253f699172f417e1317cd5f9 * 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). found a complete archive of SSLeay-0.4 to SSLeay-0.8.1b tarballs 2018-03-27T17:35:50+00:00 schwarze 2018-03-27T17:35:50+00:00 urn:sha1:30d10c511917e0e339dec931667fc4b6eb014430 on the web, so fix up SSLeay HISTORY accordingly dh.h HISTORY up to SSLeay 0.8.1b; researched from OpenSSL git 2018-03-20T22:22:10+00:00 schwarze 2018-03-20T22:22:10+00:00 urn:sha1:306bc5954f38e9ebfc60d8795e4f5f04278a0797 Merge documentation for {DH,DSA}_get0_{key,pqg}(3), 2018-02-17T16:59:48+00:00 schwarze 2018-02-17T16:59:48+00:00 urn:sha1:70379c3810269c29db4c9f6e3dd8c27b7b762ea7 EVP_PKEY_get0_{DH,DSA,RSA}(3), and RSA_{g,s}et0_key(3) that tb@ just provided. Merge one sentence and the references from dh(3) to DH_new(3) and 2016-12-10T22:30:54+00:00 schwarze 2016-12-10T22:30:54+00:00 urn:sha1:54a8ba7738e8087afcb2a55f175d0f772a38754a discard the rest of the text. There is no value in documenting some of the fields of a structure and then going on to say that the structure is intended as opaque. Besides, i doubt that we want such strong marketing of ENGINE support.