summaryrefslogtreecommitdiff
path: root/src/lib/libc/stdlib/recallocarray.c (unfollow)
Commit message (Collapse)AuthorFilesLines
2025-03-15Rename a bunch of confusingly named variablestb1-6/+6
Variables of the type serialized or deserialized are called val_in or val_out in all other manuals, so align this page to using those rather than the confusing X509_CRL **der_out, etc.
2025-03-15Add regress coverage for X509_NAME_oneline and X509_NAME_printtb2-1/+314
2025-03-14const correct d2i_* prototypestb4-13/+13
2025-03-13minor libssl bump (SSL_OP_NO_RENEGOTIATION/SSL_OP_ALLOW_CLIENT_RENEGOTIATION)sthen2-2/+2
code #ifdef'ing these and compiled with new headers won't work as expected on earlier libraries minor libtls bump to match libssl bump ok tb@
2025-03-13pkey_ec_derive: fix call to ECDH_compute_key()tb1-2/+2
The last argument is a pointer to the KDF, so use NULL, not 0.
2025-03-13Simplify field and private key encodingtb1-13/+3
Reach into the group (p and order are always available) and use BN_num_bytes() rather than using clumsy and badly named API. It's shorter and more readable. ok jsing
2025-03-13Make srtp.h self-standing by including ssl.htb1-1/+3
ok miod
2025-03-12Provide an accelerated SHA-512 assembly implementation for aarch64.jsing4-2/+353
This provides a SHA-512 assembly implementation that makes use of the ARM Cryptographic Extension (CE), which is found on many arm64 CPUs. This gives a performance gain of up to 2.5x on an Apple M2 (dependent on block size). If an aarch64 machine does not have SHA512 support, then we'll fall back to using the existing C implementation. ok kettenis@ tb@
2025-03-12Test SSL_OP_NO_RENEGOTIATION and SSL_OP_ALLOW_CLIENT_RENEGOTIATION.jsing1-1/+56
Extend renegotiation tests to cover SSL_OP_NO_RENEGOTIATION and SSL_OP_ALLOW_CLIENT_RENEGOTIATION.
2025-03-12Provide SSL_OP_NO_RENEGOTIATION and SSL_OP_ALLOW_CLIENT_RENEGOTIATION.jsing4-6/+36
In January 2017 we added SSL_OP_NO_CLIENT_RENEGOTIATION, which results in a SSL_AD_NO_RENEGOTIATION fatal alert if a ClientHello message is seen on an active connection (client initiated renegotation). Then in May 2017 OpenSSL added SSL_OP_NO_RENEGOTIATION, which results in a SSL_AD_NO_RENEGOTIATION warning alert if a server receives a ClientHello on an active connection (client initiated renegotation), or a client receives a HelloRequest (server requested renegotation). This option also causes calls to SSL_renegotiate() and SSL_renegotiate_abbreviated() to fail. Then in 2021, OpenSSL also added SSL_OP_ALLOW_CLIENT_RENEGOTIATION, which trumps SSL_OP_NO_RENEGOTIATION but only for incoming ClientHello messages (apparently unsetting SSL_OP_NO_RENEGOTIATION is too hard). Provide SSL_OP_NO_RENEGOTIATION and SSL_OP_ALLOW_CLIENT_RENEGOTIATION, primarily to make life easier for ports. If SSL_OP_NO_CLIENT_RENEGOTIATION is set it will take precedence and render SSL_OP_ALLOW_CLIENT_RENEGOTIATION ineffective. The rest of the behaviour should match OpenSSL, with the exception of ClientHellos triggering fatal alerts instead of warnings. ok tb@
2025-03-12Use .arch rather than .cpu for sha2 instructions.jsing1-2/+2
We have code that targets a specific architecture level, hence .arch makes more sense here than .cpu. Suggested by kettenis@
2025-03-12Streamline X509_VERIFY_PARAM_add0_table()tb1-17/+12
Unindent, use correct type for idx (int rather than size_t) and make this mess a bit more pleasant on the eyes. ok jsing
2025-03-12x509_vpm: remove unnecessary NULL check before sk_pop_free()tb1-4/+2
ok jsing
2025-03-10ec.h: remove last SunPro pragmastb1-13/+1
With the removal of the EC_POINTs_* API, this header features no arrays anymore, so this noise can go away. ok miod
2025-03-09Disambiguate curve commentstb1-21/+21
There are three "X9.62 curve over a 239 bit prime field" and the Brainpool curves are a pair for each field size thanks to their characteristic twist. Just include the curve name for each of the curves. discussed with jsing
2025-03-09X509_NAME_print_ex: zap stray commatb1-2/+2
2025-03-09Give libtls the same bump as libcrypto and libssltb1-2/+2
2025-03-09Give libssl the same bump as libcryptotb1-1/+1
2025-03-09Bump libcrypto major after symbol removaltb1-1/+1
2025-03-09const correct tls_session_secret_cb_fn()tb4-8/+8
Various ports throw a warning since their tls_session_secret_cb's signature doesn't match what we expect. Aligns us with OpenSSL 1.1. This is only useful for RFC 4851 EAP-FAST implementations and surprisingly it's undocumented. ok jsing
2025-03-09Bump LibreSSL versiontb1-3/+3
ok jsing
2025-03-09Reinstate PKCS12_key_gen_uni()tb5-7/+10
Unfortunately, this is used in acsm-calibre-plugin, via oscrypto. Fixes https://github.com/Leseratte10/acsm-calibre-plugin/issues/112 ok jsing
2025-03-09Remove EC_POINTs_* APItb4-34/+3
And another one... Completely overengineered for the sake of academic credentials and only Ruby ever picked this garbage up. Fortunately, it's no longer used with LibreSSL since we defanged this in 2018. The latest version of ruby/openssl has completely removed this as part of their post 1.0.x cleanup. ok jsing
2025-03-09Remove Jprojective_coordinates APItb4-29/+3
There goes another implementation detail that should never have been leaked out of the library. ok jsing
2025-03-09Unexport EC_GROUP_*precompute_mult()tb4-25/+3
These have been noops for a while and as usual some Perl module was the only thing "using" it. ok jsing
2025-03-09Unexport EC_GROUP_copy()tb4-8/+4
Without EC_GROUP_new(), this API is useless. There's EC_GROUP_dup(). ok jsing
2025-03-09Unexport EC_METHOD and all API using ittb6-56/+10
This is an implementation detail and there is no reason to leak it from the library. This removes EC_GFp_{mont,simple}_method(), EC_GROUP_{method_of,new}(), EC_METHOD_get_field_type(), EC_POINT_method_of() from the public API. EC_GROUP_copy() is now quite useless, so it will go as well. ok jsing
2025-03-09Align CRYPTO_set_mem*_functions with OpenSSL 1.1tb4-20/+9
CRYPTO_set_mem_ex_functions() was renamed to CRYPTO_set_mem_functions(), replacing the latter while also correcting the arguments for the free pointer. The backstory is that a commit that was never compiled was fixed the wrong way an hour later (both committed without review, obviously), and here we are, still cleaning up the mess 23 years later. We carry patches in cjose and stunnel for this; dovecot and links+ have autoconf checks and will adapt. Oh, and then there's the mariadb configure time insanity passing wrong function pointers... ok jsing
2025-03-09const correct UI_OpenSSL()tb2-5/+5
ok jsing
2025-03-09Fix documented signature of UI_OpenSSL()tb1-3/+3
2025-03-09Fix documented signature of BN_MONT_CTX_copy()tb1-3/+3
2025-03-09const correct BN_MONT_CTX_copy()tb2-4/+4
ok jsing
2025-03-09Unexport the weird X509_OBJECT_up_ref_count()tb4-8/+6
It's only used in x509_lu.c, so move it there. X509_OBJECT is not itself refcounted. This API bumps the refcount of its cert or CRL member. This isn't really useful outside of the library. ok jsing
2025-03-09Unexport X509_NAME_print()tb4-8/+4
Nothing uses this anymore. M2Crypto has been patched and a fix for opensc has been upstreamed. ok jsing This is the start of a major bump. Don't build the tree until I have synced sets in about 20 commits.
2025-03-09Support OPENSSL_NO_FILENAMEStb18-91/+221
Some people are concerned that leaking a user name is a privacy issue. Allow disabling the __FILE__ and __LINE__ argument in the error stack to avoid this. This can be improved a bit in tree. From Viktor Szakats in https://github.com/libressl/portable/issues/761 ok bcook jsing
2025-03-09X509_NAME_print_ex.3: move s to the proper placetb1-2/+2
2025-03-09Remove mention of X509_NAME_print(3) in the docstb3-46/+13
2025-03-08ec_asn1_test: Prepare for upcoming bumptb2-8/+11
Linking statically, pull in ec_local.h and provide a prototype for EC_GROUP_new(), which will be removed from the public API.
2025-03-08Adjust signature of CRYPTO_set_mem_functions and remove _get_ docstb1-23/+5
2025-03-08Rename CRYPTO_get_mem_functions.3 to CRYPTO_set_mem_functions.3tb2-4/+4
2025-03-08Remove EC_POINT_method_of() docstb1-19/+1
2025-03-08Remove X509_OBJECT_free_contets() docstb1-20/+3
2025-03-08Remove X509_OBJECT_up_ref_count() documentationtb1-23/+2
2025-03-08Remove EC_PIONT_{get,set}_Jprojective_coordinates_GFp docstb1-53/+1
2025-03-08Remove EC_POINTs_{make_affine,mul}() docstb1-67/+2
2025-03-08Remove EC_GROUP_{,have_}precompute_mult() docstb1-31/+4
2025-03-08Remove EC_GROUP_method_of() docstb1-20/+1
2025-03-08Remove EC_GFp_* and EC_METHOD_get_field_type docstb7-156/+12
2025-03-08Inline _CONF_get_section_values() in its last caller and remove ittb3-19/+9
NCONF_get_section() isn't any clearer by using this indirection. ok jsing
2025-03-07Provide an accelerated SHA-256 assembly implementation for aarch64.jsing4-2/+232
This provides a SHA-256 assembly implementation that makes use of the ARM Cryptographic Extension (CE), which is found on many arm64 CPUs. This gives a performance gain of up to 7.5x on an Apple M2 (dependent on block size). If an aarch64 machine does not have SHA2 support, then we'll fall back to using the existing C implementation. ok kettenis@ tb@
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-05-05 15:56:12 +0000