Re: [EXTERNAL] Re: Replacement for CRYPTO_thread_id() & ERR_get_error_line_data() for openssl3.0

[Shivakumar Poojari <Shivakumar.Poojari@xxxxxxxx>]

Hi

In the below C file, I'm trying to update eay_sterror(line:1352) function to 3.0, In eay_sterror function deprecated functions are used

CRYPTO_thread_id()

ERR_get_error_line_data()

https://github.com/zoulasc/racoon2/blob/master/iked/crypto_openssl.c

racoon2/crypto_openssl.c at master · zoulasc/racoon2 The Racoon2 project is a joint effort which provides an implementation of key management system for IPsec. The implementation is called Racoon2, a successor of Racoon, which was developed by the KA... github.com

please suggest the replacement,

thanks,

shiva kumar

---

From: Matt Caswell <matt@xxxxxxxxxxx>
Sent: Friday, September 3, 2021 1:25 PM
To: Shivakumar Poojari <Shivakumar.Poojari@xxxxxxxx>; openssl-users@xxxxxxxxxxx <openssl-users@xxxxxxxxxxx>
Cc: Paramashivaiah, Sunil <Sunil.Paramashivaiah@xxxxxxxx>; Bhattacharjee, Debapriyo (c) <dbhattacharjee@xxxxxxxx>
Subject: [EXTERNAL] Re: Replacement for CRYPTO_thread_id() & ERR_get_error_line_data() for openssl3.0

 

On 03/09/2021 05:58, Shivakumar Poojari wrote:
> Hi All,
>
> We are upgrading our code to openssl 3.0. the below function we trying
> to replace, searched in the openssl man pages not found proper information.
>
> CRYPTO_thread_id()

The deprecated implementation of this is a no-op (always returns 0).
What do you need this for? This used to be useful when locking callbacks
existed. But they were removed in 1.1.0.

>
> ERR_get_error_line_data()

You can call ERR_get_error_all() as a replacement (passing a NULL value
for the "func" parameter).


Matt

>
>
> please suggest.
> thanks,
> shivakumar.
>
>
> Notice: This e-mail together with any attachments may contain
> information of Ribbon Communications Inc. and its Affiliates that is
> confidential and/or proprietary for the sole use of the intended
> recipient. Any review, disclosure, reliance or distribution by others or
> forwarding without express permission is strictly prohibited. If you are
> not the intended recipient, please notify the sender immediately and
> then delete all copies, including any attachments.

Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.