summaryrefslogtreecommitdiff
path: root/src/lib/libc/stdlib/llabs.c (unfollow)
Commit message (Collapse)AuthorFilesLines
2024-07-11Adjust regress to match changes in SSL_select_next_proto() argstb1-123/+99
2024-07-11Adjust documentation for SSL_select_next_proto()tb1-30/+48
Use better argument names, add a link to the relevant standards and add CAVEATS and BUGS sections pointing out a few pitfalls. discussed with davidben ok beck
2024-07-11Follow BoringSSL's nomenclature in SSL_select_next_proto()tb1-28/+30
SSL_select_next_poto() was written with NPN in mind. NPN has a weird fallback mechanism which is baked into the API. This is makes no sense for ALPN, where the API behavior is undesirable since it a server should not end up choosing a protocol it doesn't (want to) support. Arguably, ALPN should simply have had its own API for protocol selection supporting the proper semantics, instead of shoehorning an NPN API into working for ALPN. Commit https://boringssl-review.googlesource.com/c/boringssl/+/17206/ renamed the arguments to work for both NPN and ALPN, with the slight downside of honoring client preference instead of the SHOULD in RFC 7301, section 3.2. This grates for most consumers in the wild, but so be it. The behavior is saner and safer. discussed with davidben ok beck
2024-07-10Zap warning against __findenv usage, it is not exported by libcjca1-3/+1
The comment probably made sense before guenther restricted the symbols exported by libc in 2015.
2024-07-10Remove the static symbols.namespace, and just generate the _libre_beck2-3359/+3
symbols from symbols.list now that we have everything hidden ok tb@
2024-07-10Teach symbols test about the namespacetb2-3/+9
This ensures that when adding public symbols, the magic is not omitted. with/ok beck
2024-07-10forgot to add a history section for the TLS PRF APItb1-1/+4
2024-07-10link EVP_PKEY_CTX_set_tls1_prf_md.3 to buildtb1-1/+2