summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Don't add an extra unknown error if we got a fatal alertbeck2020-01-221-2/+3
| | | | ok jsing@
* The legacy_record_version must be set to TLS1_2_VERSION excepttb2020-01-224-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
* Hook up the TLSv1.3 legacy shutdown code.jsing2020-01-221-2/+2
| | | | Missed in an earlier commit.
* Add minimal support for hello retry request for RFC conformance.beck2020-01-224-11/+71
| | | | | | We currently don't support sending a modified clienthello ok jsing@ tb@
* Split the TLSv1.3 guards into separate client and server guards.jsing2020-01-223-6/+13
| | | | ok beck@ tb@
* Implement close-notify and SSL_shutdown() handling for the TLSv1.3 client.jsing2020-01-223-9/+76
| | | | ok beck@ inoguchi@ tb@
* Correct legacy fallback for TLSv1.3 client.jsing2020-01-213-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@
* Remove redundant ASN1_INTEGER_set call in PKCS7_set_typeinoguchi2020-01-211-2/+1
| | | | ok bcook@
* Provide SSL_R_UNKNOWN.jsing2020-01-213-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@
* Clear and free the tls13_ctx that hangs off an SSL *s fromtb2020-01-212-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
* Add alert processing in tls client code, by adding alert to thebeck2020-01-213-19/+30
| | | | | | | tls13 context, and emiting the alert at the upper layers when the lower level code fails ok jsing@, tb@
* Add alerts to the tls 1.3 record layer and handshake layerbeck2020-01-202-49/+29
| | | | ok jsing@, inoguchi@, tb@
* Provide an error framework for use with the TLSv1.3 code.jsing2020-01-205-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@
* Update libtls config regress to include TLSv1.3.jsing2020-01-201-9/+16
|
* Add support for TLSv1.3 as a protocol to libtls.jsing2020-01-204-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@
* Free pss in RSA_freeinoguchi2020-01-171-1/+2
| | | | | ok bcook@ ok and "move it down two lines" jsing@
* Check fpu functions without setjmp/longjmp before testing the latter.bluhm2020-01-163-13/+71
| | | | | Use exit code 2 for setup failure and 1 for test fail. Unfortunately this regress is still failing.
* bump to 3.1.0bcook2020-01-141-3/+3
|
* Document how to make getopt_long(3) process arguments in order and stopstsp2020-01-131-2/+18
| | | | | at the first non-option argument. I had to read source code to figure it out.
* Make clean should not require SUDO.bluhm2020-01-131-3/+1
|
* Fix printf compiler warnings in wfp regress. Convert wchar to abluhm2020-01-131-9/+18
| | | | printable error message when failing.
* Link forgotten libc tests to the build.bluhm2020-01-132-6/+10
|
* Split setjmp-fpu regress into separate tests. Use errx(3) to explainbluhm2020-01-136-32/+69
| | | | potential problems. Regress still failing on amd64.
* Avoid leak in error path of PKCS5_PBE_keyivgeninoguchi2020-01-121-1/+2
| | | | ok jsing@ tb@
* Set "Content-Type: application/ocsp-request" in ocspcheck(1)'s POSTs,sthen2020-01-111-1/+2
| | | | | it is required by the RFC and some CAs require it (e.g. sectigo). From daharmasterkor at gmail com, ok jca@
* Avoid leak in error path of asn1_parse2inoguchi2020-01-091-17/+21
| | | | ok tb@
* If the client provides a TLS certificate and the user specifies abluhm2020-01-071-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@
* The unveil(2) for nc -U -u -l was wrong. The server cannot unveilbluhm2020-01-061-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@
* When using UNIX domain sockets, always call report_sock() with thebluhm2020-01-061-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@
* Check CMS API return value in openssl(1) cmsinoguchi2020-01-041-11/+21
| | | | ok jsing@
* Avoid leak in error path of dh_priv_decodeinoguchi2020-01-041-1/+2
| | | | ok jsing@ tb@
* In ssl.h rev. 1.167 and s3_lib.c rev. 1.188, jsing@ providedschwarze2020-01-021-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@
* Revise SSL_CTX_get_extra_chain_certs() to match OpenSSL behaviour.jsing2020-01-022-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@
* Provide TLSEXT_TYPE_* aliases for TLS 1.3.jsing2020-01-021-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@
* drand48(3) returns values in [0.0, 1.0).tb2019-12-201-3/+3
| | | | | | From j@bitminer.ca with input from Andras Farkas, deraadt, joerg@netbsd "fix however you feel best!" jmc
* spelling; from bryan stensonjmc2019-12-191-3/+3
|
* use "Currently" in the doc for "openssl enc" when talking about defaultsthen2019-12-181-2/+2
| | | | | md, to hint that it might not always be the case (e.g. if dealing with files from a different version of the tool). ok tb@
* In January, the default digest used in the openssl enc command wastb2019-12-181-7/+4
| | | | | | | | changed from md5 to sha256. Update manual to reflect that. From Fabio Scotoni ok jmc
* whitespace from go fmt + update a commenttb2019-12-141-4/+4
|
* Run Wycheproof HMAC test vectors against libcrypto.tb2019-12-141-1/+96
|
* Fix documented signatures of HMAC(3) and HMAC_Update(3). The n and lentb2019-12-141-4/+4
| | | | | arguments were changed from int to size_t with the import of OpenSSL 0.9.8h in 2008.
* The file passed to realpath(3) must exists, adjust man page to newbluhm2019-12-111-3/+3
| | | | | behavior. noticed by hshoexer@; OK beck@
* update to-do listtb2019-12-091-2/+1
|
* Run Wycheproof DSA P1363 test vectors against libcrypto.tb2019-12-091-19/+71
|
* Document X509_STORE_CTX_set_flags() which is a handy way to change theclaudio2019-12-051-3/+18
| | | | | | | verification param flags of a context. While this function is marked as likely to be deprecated in OpenSSL it seems that this may not happen. This is why we decided to still document it. OK and input from ingo@ tb@
* update to-do listtb2019-12-031-2/+2
|
* Run Wycheproof ECDSA P1363 test vectors against libcrypto.tb2019-12-031-8/+8
|
* Add an EcPoint variant and pass it to the ECDH test runner.tb2019-12-031-20/+31
|
* Annotate test vector files with an enum which we can then pass to thetb2019-12-031-27/+48
| | | | run*Test programs as needed.
* Add missing RCS tag.tb2019-12-031-0/+1
|
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-03-22 18:24:05 +0000