* If your program uses threads, then you *have* to set the thread
functions. Glad you got it fixed.
> Why can't OpenSSL do this automatically? Yes, some applications will need to
> supply specialty functions, but it could supply defaults.
It does in 1.1.0 and later.
--
openssl-users mai
On 2/13/2018 5:31 AM, Salz, Rich via openssl-users wrote:
>
> If your program uses threads, then you **have** to set the thread
> functions. Glad you got it fixed.
>
Why can't OpenSSL do this automatically? Yes, some applications will
need to supply specialty functions, but it could supply defau
> Dear all, very appreciate your reply! We have double check the implementation
> of related > functions, and confirm that the input params for the function
> int rsa_public_encrypt(const uint8_t *rsa_input, const int input_len, uint8_t
> *enc_out,
> uint8_t *public_key, const int key_len)
> are
If your program uses threads, then you *have* to set the thread functions.
Glad you got it fixed.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
On 13/02/2018 12:16, Xiang Ren wrote:
Dear all, very appreciate your reply! We have double check the
implementation of related functions, and confirm that the input params
for the function
int rsa_public_encrypt(const uint8_t *rsa_input, const int input_len,
uint8_t *enc_out, uint8_t *public_ke
Dear all, very appreciate your reply! We have double check the implementation
of related functions, and confirm that the input params for the function int
rsa_public_encrypt(const uint8_t *rsa_input, const int input_len, uint8_t
*enc_out, uint8_t *public_key, const int key_len) are all stack var
