FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=stable%2F13 2023-08-23T17:43:30Z 2023-08-23T17:43:30Z Warner Losh imp@FreeBSD.org 2023-08-22T01:32:01Z urn:sha1:023fc80ee38a117fa65b2ccb2abf8bdc7dbd6fd9 Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/ Similar commit in main: (cherry picked from commit d0b2dbfa0ecf) 2022-10-12T08:34:03Z Baptiste Daroussin bapt@FreeBSD.org 2022-08-26T14:02:09Z urn:sha1:41067961b6f3a0b5667e40e768b7b46e4092348e most programs in ports are looking for .pc files in order to get the necessary information on how to compile and link against openssl. The ports now also has a way to hide or force a path for pkgconf. Providing .pc files along with openssl in base will allow (once all the supported version of FreeBSD has it) so improve the framework to deal with openssl in base vs openssl in ports (and libressl) This will also greatly reduce the number of patches necessary to workaround the build systems which only knows how to detect where openssl is installed via pkgconf. PR: 266051 MFC After: 3 weeks Reviewed by: jkim, delphij Exp-run by: antoine Differential Revision: https://reviews.freebsd.org/D36360 (cherry picked from commit b323fa85f15268ac44b8ff90faf90bce5d87b608) 2021-06-30T07:24:31Z Emmanuel Vadot manu@FreeBSD.org 2021-05-02T15:46:17Z urn:sha1:632e3f2f3a66cea437a93169b0f907931348ffb5 This is useful for upgrade and also to make tiny jail so they won't depend on FreeBSD-utilities (where openssl was packaged before). MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D30081 2021-02-05T00:03:20Z John Baldwin jhb@FreeBSD.org 2021-01-16T00:17:31Z urn:sha1:c1c52cd57e8810ca294d02220dfa72607c9a5567 This merges upstream patches from OpenSSL's master branch to add KTLS infrastructure for TLS 1.0-1.3 including both RX and TX offload and SSL_sendfile support on both Linux and FreeBSD. Note that TLS 1.3 only supports TX offload. A new WITH/WITHOUT_OPENSSL_KTLS determines if OpenSSL is built with KTLS support. It defaults to enabled on amd64 and disabled on all other architectures. Sponsored by: Netflix (cherry picked from commit aa906e2a4957db700d9e6cc60857e1afe1aecc85) 2020-08-13T20:28:35Z John Baldwin jhb@FreeBSD.org 2020-08-13T20:28:35Z urn:sha1:1e04d9ff3e2565a402e449eb59b30b826bb2894a In practice this isn't used in OpenSSL outside of some sparc-specific code. Reviewed by: delphij Differential Revision: https://reviews.freebsd.org/D26058 2020-07-01T00:59:28Z Conrad Meyer cem@FreeBSD.org 2020-07-01T00:59:28Z urn:sha1:80a315ffb6053e5e2b1a0d07d7571fad0e0a64bd SSLv3 has been deprecated since 2015 (and broken since 2014: "POODLE"); it should not have shipped in FreeBSD 11 (2016) or 12 (2018). No one should use it, and if they must, they can use some implementation outside of base. There are three symbols removed with OPENSSL_NO_SSL3_METHOD: SSLv3_client_method SSLv3_method SSLv3_server_method These symbols exist to request an explicit SSLv3 connection to a server. There is no good reason for an application to link or invoke these symbols instead of TLS_method(), et al (née SSLv23_method, et al). Applications that do so have broken cryptography. Define these symbols for some pedantic definition of ABI stability, but remove the functionality again (r361392) after r362620. Reviewed by: gordon, jhb (earlier-but-equivalent version both) Discussed with: bjk, kib Differential Revision: https://reviews.freebsd.org/D25493 2018-10-25T13:37:57Z Konstantin Belousov kib@FreeBSD.org 2018-10-25T13:37:57Z urn:sha1:89250cff0c9af8a2c976020468fbe9637b846dd3 Reported by: many Reviewed by: gjb Sponsored by: The FreeBSD Foundation MFC after: 3 hours 2018-09-19T00:24:00Z Jung-uk Kim jkim@FreeBSD.org 2018-09-19T00:24:00Z urn:sha1:85a025545fac7b155662fc534348ed8e326fca90 2018-09-13T23:51:54Z Jung-uk Kim jkim@FreeBSD.org 2018-09-13T23:51:54Z urn:sha1:cec27dca41f49438670a4222883f41d468a2d25b Note the files are not automatically generated for now. 2018-09-13T23:46:27Z Jung-uk Kim jkim@FreeBSD.org 2018-09-13T23:46:27Z urn:sha1:0ea17a70cec7636a6491fa510ab87021204eb18c