summaryrefslogtreecommitdiff
path: root/src/lib/libc/stdlib/reallocarray.c (unfollow)
Commit message (Collapse)AuthorFilesLines
2020-01-22fix previous: alert_desc needs to be an int.tb1-2/+2
2020-01-22Avoid modifying alert in the success path.tb1-11/+17
ok beck jsing
2020-01-22Enable the TLSv1.3 client in libssl.jsing1-2/+3
This also makes it available to clients that use libtls, including ftp(1) and nc(1). Note that this does not expose additional defines via public headers, which means that any code conditioning on defines like TLS1_3_VERSION or SSL_OP_NO_TLSv1_3 will not enable or use TLSv1.3. This approach is necessary since too many pieces of software assume that if TLS1_3_VERSION is available, other OpenSSL 1.1 API will also be available, which is not necessarily the case. ok beck@ tb@
2020-01-22Correct includes check for libtls.jsing1-2/+2
2020-01-22Add checks to ensure that lib{crypto,ssl,tls} public headers have actuallyjsing3-3/+33
been installed prior to building. Requested by and ok tb@
2020-01-22delete wasteful ;;deraadt1-2/+2
ok tedu
2020-01-22Move guards from public to internal headers, and fix not use values.beck2-8/+7
reverts previous attempt which would have broken ports ok jsing@
2020-01-22Simplify header installation by combining the HDRS and HDRS_GEN loops.jsing1-9/+2
ok beck@
2020-01-22Note in the man page that the default protocols list includes 1.3beck1-4/+4
ok jsing@
2020-01-22Enable TLS version 1.3 in the default protocols for libtls.beck1-2/+2
This will as yet not do anything, until we turn it on in the lower level libraries. ok jsing@
2020-01-22Simplify the peekaboo code.jsing1-35/+6
ok beck@
2020-01-22Implement support for SSL_peek() in the TLSv1.3 record layer.jsing3-14/+39
ok beck@ tb@
2020-01-22After the ClientHello has been sent or received and before the peer'stb4-8/+22
Finished message has been received, a change cipher spec may be received and must be ignored. Add a flag to the record layer struct and set it at the appropriate moments during the handshake so that we will ignore it. ok jsing
2020-01-22Add -peekaboo option to s_client, to test SSL_peekbeck1-4/+66
peeks data before reading, compares to subsequent read. ok jsing@
2020-01-22Correctly set the legacy version when TLSv1.3 is building a client hello.jsing1-4/+11
The legacy version field is capped at TLSv1.2, however it may be lower than this if we are only choosing to use TLSv1.0 or TLSv1.1. ok beck@ tb@
2020-01-22Don't add an extra unknown error if we got a fatal alertbeck1-2/+3
ok jsing@
2020-01-22The legacy_record_version must be set to TLS1_2_VERSION excepttb4-9/+30
in the ClientHello where it may be set to TLS1_VERSION. Use the minimal supported version to decide whether we choose to do so or not. Use a sent hook to set it back TLS1_2_VERSION right after the ClientHello message is on the wire. ok beck jsing
2020-01-22Hook up the TLSv1.3 legacy shutdown code.jsing1-2/+2
Missed in an earlier commit.
2020-01-22Add minimal support for hello retry request for RFC conformance.beck4-11/+71
We currently don't support sending a modified clienthello ok jsing@ tb@
2020-01-22Split the TLSv1.3 guards into separate client and server guards.jsing3-6/+13
ok beck@ tb@
2020-01-22Implement close-notify and SSL_shutdown() handling for the TLSv1.3 client.jsing3-9/+76
ok beck@ inoguchi@ tb@
2020-01-21Correct legacy fallback for TLSv1.3 client.jsing3-9/+30
When falling back to the legacy TLS client, in the case where a server has sent a TLS record that contains more than one handshake message, we also need to stash the unprocessed record data for later processing. Otherwise we end up with missing handshake data. ok beck@ tb@
2020-01-21Remove redundant ASN1_INTEGER_set call in PKCS7_set_typeinoguchi1-2/+1
ok bcook@
2020-01-21Provide SSL_R_UNKNOWN.jsing3-5/+7
This allows us to indicate that the cause of the failure is unknown, rather than implying that it was an internal error when it was not. ok beck@
2020-01-21Clear and free the tls13_ctx that hangs off an SSL *s fromtb2-2/+8
SSL_{clear,free}(3). Make sure the handshake context is cleaned up completely: the hs_tls13 reacharound is taken care of by ssl3_{clear,free}(3). Add a missing tls13_handshake_msg_free() call to tls13_ctx_free(). ok beck jsing
2020-01-21Add alert processing in tls client code, by adding alert to thebeck3-19/+30
tls13 context, and emiting the alert at the upper layers when the lower level code fails ok jsing@, tb@
2020-01-20Add alerts to the tls 1.3 record layer and handshake layerbeck2-49/+29
ok jsing@, inoguchi@, tb@
2020-01-20Provide an error framework for use with the TLSv1.3 code.jsing5-7/+151
This is based on the libtls error handling code, but adds machine readable codes and subcodes. We then map these codes back to libssl error codes. ok beck@ inoguchi@
2020-01-20Update libtls config regress to include TLSv1.3.jsing1-9/+16
2020-01-20Add support for TLSv1.3 as a protocol to libtls.jsing4-11/+20
This makes tls_config_parse_protocols() recognise and handle "tlsv1.3". If TLSv1.3 is enabled libtls will also request libssl to enable it. ok beck@ tb@
2020-01-17Free pss in RSA_freeinoguchi1-1/+2
ok bcook@ ok and "move it down two lines" jsing@
2020-01-16Check fpu functions without setjmp/longjmp before testing the latter.bluhm3-13/+71
Use exit code 2 for setup failure and 1 for test fail. Unfortunately this regress is still failing.
2020-01-14bump to 3.1.0bcook1-3/+3
2020-01-13Document how to make getopt_long(3) process arguments in order and stopstsp1-2/+18
at the first non-option argument. I had to read source code to figure it out.
2020-01-13Make clean should not require SUDO.bluhm1-3/+1
2020-01-13Fix printf compiler warnings in wfp regress. Convert wchar to abluhm1-9/+18
printable error message when failing.
2020-01-13Link forgotten libc tests to the build.bluhm2-6/+10
2020-01-13Split setjmp-fpu regress into separate tests. Use errx(3) to explainbluhm6-32/+69
potential problems. Regress still failing on amd64.
2020-01-12Avoid leak in error path of PKCS5_PBE_keyivgeninoguchi1-1/+2
ok jsing@ tb@
2020-01-11Set "Content-Type: application/ocsp-request" in ocspcheck(1)'s POSTs,sthen1-1/+2
it is required by the RFC and some CAs require it (e.g. sectigo). From daharmasterkor at gmail com, ok jca@
2020-01-09Avoid leak in error path of asn1_parse2inoguchi1-17/+21
ok tb@
2020-01-07If the client provides a TLS certificate and the user specifies abluhm1-5/+6
hash value on the nc(1) server command line, the netcat server must use the TLS context of the accepted socket for verification. As the listening socket was used instead, the verification was always successful. If the peer provides a certificate, there must be a hash. Make the hash verification fail safe. OK tb@
2020-01-06The unveil(2) for nc -U -u -l was wrong. The server cannot unveilbluhm1-4/+23
the file system as it has to connect to the UNIX domain client socket. The path of the latter is determined dynamically. Instead add a restrictive pledge(2) after connect(2). OK tb@
2020-01-06When using UNIX domain sockets, always call report_sock() with thebluhm1-6/+10
path name of the socket. This avoids bad errors from getnameinfo(3). Use the same error check for both calls to getnameinfo(3). OK millert@ tb@
2020-01-04Check CMS API return value in openssl(1) cmsinoguchi1-11/+21
ok jsing@
2020-01-04Avoid leak in error path of dh_priv_decodeinoguchi1-1/+2
ok jsing@ tb@
2020-01-02In ssl.h rev. 1.167 and s3_lib.c rev. 1.188, jsing@ providedschwarze1-4/+21
the new function SSL_CTX_get_extra_chain_certs_only(3) and changed the semantics of the existing SSL_CTX_get_extra_chain_certs(3) API from the former OpenSSL 1.0.1 behaviour to the new, incompatible OpenSSL 1.0.2 behaviour. Adjust the documentation. OK jsing@ beck@ inoguchi@
2020-01-02Revise SSL_CTX_get_extra_chain_certs() to match OpenSSL behaviour.jsing2-8/+23
In OpenSSL, SSL_CTX_get_extra_chain_certs() really means return extra certs, unless there are none, in which case return the chain associated with the certificate. If you really just want the extra certs, including knowing if there are no extra certs, then you need to call SSL_CTX_get_extra_chain_certs_only()! And to make this even more entertaining, these functions are not documented in any OpenSSL release. Reported by sephiroth-j on github, since the difference in behaviour apparently breaks OCSP stapling with nginx. ok beck@ inoguchi@ tb@
2020-01-02Provide TLSEXT_TYPE_* aliases for TLS 1.3.jsing1-1/+10
OpenSSL decided to use their own names for two of the TLS 1.3 extensions, rather than using the names given in the RFC. Provide aliases for these so that code written to work with OpenSSL also works with LibreSSL (otherwise everyone gets to provide their own workarounds). Issue noted by d3x0r on github. ok inoguchi@ tb@
2019-12-20drand48(3) returns values in [0.0, 1.0).tb1-3/+3
From j@bitminer.ca with input from Andras Farkas, deraadt, joerg@netbsd "fix however you feel best!" jmc
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-05-22 06:27:29 +0000