Shane
Shane
A related question is where EVP_DigestUpdate() should segfault if it is passed NULL as its data..
I cant find where this format is defined, but just using the data you supplied you can do it in code using a custom d2i function.. ```` #include #include static...
There are hex related functions such as OPENSSL_hexstr2buf_ex()
The root of the issue is that EVP_DigestUpdate() allows NULL to get passed to it, and digests dont check for NULL.. ossl_eds22519_sign() gets passed pointers for priv and pub... (which...
@openssl/otc - should EVP_DigestUpdate() behave differently and return early. What would it return 0 or 1 (Possibly breaking code that currently works).
I assume X448 will also break when it does SHAKE256
OTC: This is a breaking change. But using the removed values as supplied is not doing what the user intended. This may force the user to update their code. ~~Note:...
Note that this is correctly documented in the RSA related pod file..
Note also that https://github.com/openssl/openssl/pull/19443 fixes the demo that used this..
As per @t-j-h suggestion, I have left the values in and pointed them to existing values. This will break during runtime as opposed to not compile. Tests added to prove...