summaryrefslogtreecommitdiff
path: root/src/lib/libc/stdlib/malloc.c (unfollow)
Commit message (Collapse)AuthorFilesLines
2016-12-13Start RSA_PSS_PARAMS_new(3) stub from scratch. Both functionsschwarze2-1/+54
are listed in <openssl/rsa.h> and OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file. More could probably be said about PSS, but this is a start...
2016-12-13Complete the CBB conversion and cleanup of send_client_key_exchange().jsing1-42/+12
ok doug@
2016-12-13Convert ssl3_send_client_kex_gost() to CBB.jsing1-17/+19
ok doug@
2016-12-13tweak SEE ALSO; in particular,schwarze9-36/+35
make sure that all PKCS7 pages point to PKCS7_new(3)
2016-12-13Write PKCS7_new(3) manual page from scratch. All the functions areschwarze2-1/+247
public: listed in <openssl/pkcs7.h> and OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file.
2016-12-13Convert ssl3_send_client_kex_ecdhe() to CBB. Also check the return value ofjsing1-34/+35
the EC_POINT_point2oct() calls. Feedback from and ok doug@
2016-12-13typo fix; ok schwarzejmc1-3/+3
2016-12-12Write OCSP_CRLID_new(3) and OCSP_SERVICELOC_new(3) from scratch.schwarze5-4/+196
These two and OCSP_CRLID_free(3) and OCSP_SERVICELOC_free(3) are public by being in OpenSSL doc/man3/X509_dup.pod. OCSP_crlID_new(3) and OCSP_url_svcloc_new(3) are related and, even though completely undocumented in OpenSSL, obviously much more important. If you had told me a year ago that i would ever write such text, i would have called you crazy.
2016-12-12various cleanup;jmc4-25/+26
2016-12-12Document OCSP_CERTID_new(3) listed in <openssl/ocsp.h> and in OpenSSLschwarze1-16/+52
doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file. Add some information about what the OCSP_CERTID object actually represents, along with the pertinent STANDARDS reference.
2016-12-12Document OCSP_SINGLERESP_new(3), OCSP_SINGLERESP_free(3),schwarze1-3/+90
OCSP_CERTSTATUS_new(3), OCSP_CERTSTATUS_free(3), OCSP_REVOKEDINFO_new(3), and OCSP_REVOKEDINFO_free(3), all in <openssl/ocsp.h> and in OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file. Add some information about what these objects actually represent, along with the pertinent STANDARDS reference.
2016-12-12Document OCSP_RESPONSE_new(3), OCSP_RESPONSE_free(3),schwarze1-36/+144
OCSP_RESPBYTES_new(3), OCSP_RESPBYTES_free(3), OCSP_BASICRESP_new(3), OCSP_BASICRESP_free(3), OCSP_RESPDATA_new(3), OCSP_RESPDATA_free(3), OCSP_RESPID_new(3), and OCSP_RESPID_free(3), all in <openssl/ocsp.h> and in OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file. Add some information about what these objects actually represent, along with the pertinent STANDARDS reference. Sort functions into a logical order and apply minor wording tweaks.
2016-12-12Document OCSP_SIGNATURE_new(3), OCSP_SIGNATURE_free(3),schwarze1-26/+95
OCSP_REQINFO_new(3), OCSP_REQINFO_free(3), OCSP_ONEREQ_new(3), OCSP_ONEREQ_free(3), all in <openssl/ocsp.h> and in OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file. Add some information about what these objects actually represent, along with the pertinent STANDARDS reference. Minor wording tweaks.
2016-12-12Document DSAparams_dup(3). It is in <openssl/dsa.h> and documentedschwarze1-2/+35
by OpenSSL, so it is clearly public. OpenSSL documents it in doc/man3/X509_dup.pod, but with wrong header file, wrong prototype, and misleading description. While here, fix the wrong d2i_DSA_SIG(3) return type and document those RETURN VALUES that i could easily figure out.
2016-12-12Document DIRECTORYSTRING_new(3), DIRECTORYSTRING_free(3),schwarze1-6/+32
DISPLAYTEXT_new(3), DISPLAYTEXT_free(3). These functions are clearly public because OpenSSL documents them and they are in the public <openssl/asn1.h> header. OpenSSL documents these four functions in doc/man3/X509_dup.pod [sic], but the information given is completely wrong: wrong header file, wrong prototypes, misleading description. Why, oh why do people even bother to write documentation if nothing of what they write is true?
2016-12-11import openssl.cnf(5) and x509v3.cnf(5) from OpenSSL;schwarze6-14/+1259
below OpenBSD quality standards, but better than nothing...
2016-12-11Distribute the text of ec(3) to the individual EC manuals where it belongs.schwarze11-107/+70
Make sure EC_GROUP_new(3) points to all EC manuals and all EC manuals point back to EC_GROUP_new(3), and add some other useful links as well. Change all links to ec(3) to point to EC_GROUP_new(3) instead.
2016-12-11Merge all of rsa(3) into RSA_new(3).schwarze3-93/+86
In this case, keep the text about individual struct fields because it contains some actual information.
2016-12-11Change all references to rsa(3) to point to RSA_new(3) instead.schwarze17-50/+51
Make sure all RSA pages point back to RSA_new(3).
2016-12-11add missing section number to Xr;jmc1-3/+3
2016-12-11some fixes for the dsa.3 -> DSA_new.3 changes;jmc3-9/+8
2016-12-10Merge one sentence and the references from dsa(3) to DSA_new(3) andschwarze3-80/+23
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.
2016-12-10Change all references to dsa(3) to point to DSA_new(3).schwarze12-35/+33
Make sure all DSA pages point back to DSA_new(3).
2016-12-10Merge one sentence and the references from dh(3) to DH_new(3) andschwarze3-67/+12
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.
2016-12-10Replace all references to dh(3) with DH_new(3).schwarze12-34/+30
Make sure that all DH pages point back to DH_new(3).
2016-12-10Add Copyright and license; jmc@ noticed that i forgot this file.schwarze1-30/+53
Correct the header: It's <openssl/ui_compat.h>, not <openssl/des_old.h>. Delete documentation of des_read_password(3) and des_read_2passwords(3) which no longer exist. Probably, the rest of this ought to be deleted as well...
2016-12-10Add Copyright and license; jmc@ noticed that i missed this file.schwarze1-1/+50
2016-12-10Merge bn(3) into BN_new(3).schwarze3-76/+41
OpenSSL removed bn(3) without replacement, but the introductory text does seem helpful, and it is good for a sub-library to have a central page pointing to all other pages and pointed at from all other pages of the sub-library.
2016-12-10replace all references to bn(3) with BN_new(3),schwarze24-70/+74
and make sure all BN*(3) pages point back to BN_new(3)
2016-12-10Add Copyright and license; jmc@ noticed that i missed this file.schwarze1-2/+50
I'm not merging documentation for X509_STORE_set_verify_func(3) from OpenSSL because their documentations does not appear to match the code we have, and i don't understand what the code does.
2016-12-10Copyright and license; jmc@ noticed that is forgot this fileschwarze1-2/+50
2016-12-10Add Copyright and license.schwarze1-1047/+149
Delete all the function prototypes. They are all available from their individual manual pages. Here, they were incomplete and nothing but a maintenance nightmare. Add several missing cross reference, such that this page now references all libssl manual pages. Delete a sentence that said nothing and correct a typo. Now all libssl manuals have proper Copyright notices and licenses, and i have merged all improvements from OpenSSL that i could find.
2016-12-10Write an SSL_get_shared_ciphers(3) manual from scratch; another oneschwarze2-1/+72
where BUGS is longer than DESCRIPTION. The function is listed in ssl(3) and <openssl/ssl.h>, so it's clearly public. The code looks slightly mysterious to me, so it would be welcome if somebody more familiar with TLS protocols could check factual accuracy.
2016-12-10New manual pages SSL_get_certificate(3), SSL_get_state(3), andschwarze5-4/+286
SSL_num_renegotiations(3) written from scratch. These functions are listed in ssl(3) and <openssl/ssl.h>, so they are clearly public.
2016-12-10Document SSL_version(3). It's listed in ssl(3) and <openssl/ssl.h>,schwarze1-7/+20
so it's clearly a public interface.
2016-12-08some Vt fixes;jmc5-18/+18
2016-12-08minor cleanup;jmc5-24/+20
2016-12-08various cleanup;jmc12-61/+58
2016-12-08Fix regressions introduce in the fix for CVE-2016-6559.millert1-6/+5
From FreeBSD (glebius)
2016-12-07Write SSL_renegotiate(3) manual from scratch; this function is listedschwarze2-1/+58
in ssl(3) and <openssl/ssl.h>, so it's clearly a public interface. More could probably be said, the code looks somewhat mysterious to me, but i think this stub is already better than nothing.
2016-12-07add missing .Nm SSL_peek in the NAME sectionschwarze1-3/+4
2016-12-07Write SSL_copy_session_id(3) manual from scratch. This function isschwarze2-1/+78
listed in ssl(3) and <openssl/ssl.h>, so it's clearly a public interface. We might wish to merge the improved code from OpenSSL 1.1.0, but that's major bump, so i'm documenting the BUGS for now.
2016-12-07Write new SSL_dup(3) manual from scratch. This function is listedschwarze2-1/+61
in ssl(3) and <openssl/ssl.h>, so it is clearly public.
2016-12-07New SSL_dup_CA_list(3) manual written from scratch.schwarze2-1/+53
Mentioned in ssl(3) and <openssl/ssl.h>, so it is public.
2016-12-07Add documentation for SSL_add_file_cert_subjects_to_stack(3) andschwarze1-25/+103
SSL_add_dir_cert_subjects_to_stack(3), written from scratch. Both functions are listed in ssl(3) and <openssl/ssl.h> and recommended for the use by browsers in source code comments, so they are clearly public interfaces. Mention deduplication. Purge some duplicate text and improve some wording while here. Two additional cross references instead of the useless ssl(3). Add HISTORY, AUTHORS, and BUGS. It is depressing that BUGS (purely from code inspection) became longer than the DESCRIPTION.
2016-12-07Convert ssl3_send_client_kex_dhe() to CBB.jsing1-14/+23
ok doug@
2016-12-07Ensure that we zero memory that contiansthe ASN.1 encoded session, sincejsing1-26/+29
this contains the session master key. ok deraadt@ doug@
2016-12-07Ensure that we zero memory used to hold the ASN.1 encoded session, sincejsing1-1/+4
this contains the session master key. ok deraadt@ doug@
2016-12-07Fix a typo, decrement rem, don't increment for single digit hex bytes.millert1-2/+2
From Henri Kemppainen
2016-12-06An SSL_SESSION_print(3) manual written from scratch. It's clearlyschwarze2-1/+68
a public interface since it's listed both in ssl(3) and in <openssl/ssl.h>. Nothing to pilfer from OpenSSL in this case...
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-05-02 12:13:33 +0000