summaryrefslogtreecommitdiff
path: root/src/lib/libc/stdlib/recallocarray.c (unfollow)
Commit message (Collapse)AuthorFilesLines
2024-10-11Add error regress coverage for ERR_LIB_SYS.jsing1-1/+19
These are dynamically populated based on strerror() values.
2024-10-11Remove params argument from ec_asn1_group2parameters()tb1-13/+8
Its only caller passes NULL, so we can simplify the entry point and the exit of this function a bit. ok jsing
2024-10-11Simplify ec_asn1_group2pkparameters()tb1-15/+8
The parameters argument is always NULL, so we can simplify this helper accordingly. ok jsing
2024-10-11Spell NULL in a simpler fashiontb1-3/+5
priv_key->parameters is always NULL at this point, since its corresponding entry in the ASN.1 template has ASN1_TFLG_OPTIONAL set, so there is no point in pretending to pass it to ec_asn1_group2pkparameters(). ok jsing
2024-10-11Clean up i2d_ECPKParameters()tb1-10/+13
Use better variable names and turn it into single-exit. This changes the behavior slightly in that an error is pushed onto the stack also for i2d_ECPKPARAMETERS() return values < 0. ok jsing
2024-10-10Remove unused CONF_imodule struct members and accessorstb2-69/+2
ok beck jsing
2024-10-09Remove SSL_R_TRIED_TO_USE_UNSUPPORTED_CIPHERtb1-2/+1
Nothing uses this and it collides with ALPN
2024-10-09Add missing alert descriptions (taken from RFC 8446)tb1-2/+11
This is so gross...
2024-10-09Add missing alerts to SSL_alert_desc_string{,_long}()tb1-7/+25
ok beck
2024-10-09Add missing alert errors and error stringstb2-2/+10
For every TLS alert there needs a corresponding error with error code having an offset of SSL_AD_REASON_OFFSET (aka 1000), otherwise the error stack fails to set the reason correctly. ok beck
2024-10-03Remove the unused field_mod_func from EC_GROUPtb1-4/+1
This was only used by the NIST method. For all other group methods it's an uninitialized pointer (as EC_GROUP_new() still uses the malloc + set all members to 0 idiom). ok jsing
2024-10-03Make EC{,PK}PARAMETERS_it statictb1-3/+3
They aren't used outside of this file.
2024-10-03Fix ASN1_INTEGER_to_BN() misusetb1-16/+16
Same issue/leak as for BN_to_ASN1_INTEGER(). Stop reusing the elliptic curve parameters a and b for order and cofacter. It's confusing. ok jsing
2024-10-03Switch field_bits to be an inttb1-3/+3
ok jsing
2024-10-03Fix BN_to_ASN1_INTEGER() misusetb1-7/+6
You can either let this API reuse an existing ASN1_INTEGER or you can let it allocate a new one. If you try to do both at the same time, you'll leak. ok jsing
2024-10-03Provide OPENSSL_INIT_NO_ATEXIT nooptb1-1/+2
The brilliant idea of installing a fragile non-idempotent cleanup atexit handler as a library has bitten many people over time. This gets particularly exciting when you can't control who dlopens the lib first (don't we all love Python bindings) or if you are in a threaded context. Fake OpenSSL clones chose not to do this but now get to carry a noop flag since people start opting out of this madness (there's a good old tradition at work here). ok beck joshua jsing millert miod
2024-10-03X509V3_EXT_get_nid.3: indicate what nid meanstb1-3/+3
2024-10-02Reorder functions.jsing1-297/+286
Reorder functions so that things are somewhat more logical, moving internal functions towards the top (and removing now unnecessary prototypes).
2024-10-02Remove err_fns and associated machinery.jsing1-142/+65
Like all good OpenSSL code, errors was built to be completely extensible. Thankfully, the ERR_{get,set}_implementation() functions were removed in r1.127 of err.c, which means that the extensibility can no longer be used. Take the first of many steps to clean up this code - remove err_fns and associated machinery, calling functions directly. Rename so that we have an 'err_' prefix rather than 'int_' (or nothing). ok joshua@ tb@
2024-10-02Hook up the err regress.jsing1-1/+2
2024-10-02Add initial regress for the error stack and ERR_* APIs.jsing2-0/+210
2024-10-02Enable additional CRYPTO_get_ex_new_index() tests.jsing1-6/+1
It was previously possible to call CRYPTO_get_ex_new_index() with either a negative index or a positive index that equaled or exceeded CRYPTO_EX_INDEX__COUNT. The reimplementation of exdata treats these as error cases.
2024-09-22Reinstate bounds check accidentally disabled when defining OPENSSL_NO_DTLS1tb1-3/+1
From Kenjiro Nakayama Closes https://github.com/libressl/portable/issues/1097
2024-09-20remove unneeded semicolons; checked by millert@jsg1-2/+2
2024-09-18Enable large number of extension tests and stop skippking QUIC transporttb1-8/+3
parameter extension which we now know about
2024-09-17tlsfuzzer: add a start-server convenience target for interactive testingtb1-2/+6
2024-09-17Replace OpenSSL 3.1 (which no longer is in ports) with 3.3tb1-2/+2
2024-09-14tlsfuzzer: grammar fix missed in previoustb1-2/+2
2024-09-13typo: troups -> groupstb1-2/+2
2024-09-11parametes -> parameterstb1-2/+2
2024-09-09Make error 235 resolve to "no application protocol"tb1-2/+1
We accidentally have two errors 235 since we didn't notice that OpenSSL removed the unused SSL_R_TRIED_TO_USE_UNSUPPORTED_CIPHER and later that becamse SSL_R_NO_APPLICATION_PROTOCOL. Getting an "unsupported cipher" error when fiddling with ALPN is confusing, so fix that. ok jsing
2024-09-09Fix alert callback in the QUIC layertb1-2/+12
Only close_notify and user_cancelled are warning alerts. All others should be fatal. In order for the lower layers to behave correctly, the return code for fatal alerts needs to be TLS13_IO_ALERT instead of TLS13_IO_SUCCESS. Failure to signal handshake failure in the public API led to a crash in HAProxy when forcing the tls cipher to TLS_AES_128_CCM_SHA256 as found by haproxyfred while investigating https://github.com/haproxy/haproxy/issues/2569 Kenjiro Nakayama found misbehavior of ngtcp2-based servers, wrote a similar patch and tested this version. Fixes https://github.com/libressl/portable/issues/1093 ok jsing
2024-09-09Add and use tls13_record_layer_alert_sent()tb2-3/+12
This is a small refactoring that wraps a direct call to the record layer's alert_sent() callback into a handler for upcoming reuse in the QUIC code. No functional change. ok jsing
2024-09-07Futhermore -> Furthermoretb1-2/+2
2024-09-06Prepare for an upcoming tlsfuzzer test that expects decode_errortb1-2/+5
when we send illegal_parameter. Shrug.
2024-09-06Reenable AES-NI in libcryptotb4-10/+29
The OPENSSL_cpu_caps() change after the last bump missed a crucial bit: there is more MD mess in the MI code than anticipated, with the result that AES is now used without AES-NI on amd64 and i386, hurting machines that previously greatly benefitted from it. Temporarily add an internal crypto_cpu_caps_ia32() API that returns the OPENSSL_ia32cap_P or 0 like OPENSSL_cpu_caps() previously did. This can be improved after the release. Regression reported and fix tested by Mark Patruck. No impact on public ABI or API. with/ok jsing PS: Next time my pkg_add feels very slow, I should perhaps not mechanically blame IEEE 802.11...
2024-09-06Adjust documentation to work without X509_LOOKUP_by_subject()tb1-52/+5
X509_LOOKUP_by_subject() was made internal a while back. Its documentation was very detailed, so this was a bit of a tangle to undo.
2024-09-03typo in comment; Effectivly -> Effectively; ok gilles@op1-2/+2
2024-09-03wild white spacederaadt1-2/+2
2024-09-02Remove X509_check_trust documentationtb7-226/+11
2024-09-02The X509at_* manuals are no longer neededtb4-299/+4
2024-09-02Also remove .Xr to X509at_*tb1-4/+2
2024-09-02Excise X509at_* from X509_REQ_* documentationtb1-22/+10
2024-09-02Rename lastpos to start_after to match other, similar manualstb1-13/+13
2024-09-02More X509at_* removaltb1-8/+4
2024-09-02Remove mention of the no longer public X509at_* functionstb1-23/+12
2024-09-02Adjust function signatures for const X509_LOOKUP_METHODtb2-8/+8
2024-09-01symbols: remove special case for cpuid_setup and cpu_capstb1-8/+1
The former is gone and the latter is available in crypto.h.
2024-08-31sync x509v3_add_value with x509_utl.ctb1-19/+32
2024-08-31Rewrite X509V3_add_value() to a single exit idiomtb1-19/+32
ok jsing