Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c

* The current patch ( PR 5164 ) just changes "can be safely used" to "can generally be used safely". Without enough information for a user of the library to know whether a given usage is safe, this isn't useful documentation. When it comes to threading, "generally safe" is the same as "unsaf

Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c

On 24. jan. 2018, at 6:11 f.h., Benjamin Kaduk via openssl-dev wrote: > On 01/23/2018 07:19 PM, Salz, Rich via openssl-dev wrote: >> Well, the most likely fix is to make the “safely” wording be more vague, >> which I doubt you’ll like. But I doubt anyone on the team has much interest >> in fix

Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c

* Well, the most likely fix is to make the “safely” wording be more vague, which I doubt you’ll like. But I doubt anyone on the team has much interest in fixing 1.0.2 locking issues. https://github.com/openssl/openssl/pull/5164 -- openssl-dev mailing list To unsubscribe: https://mta.op

Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c

* OpenSSL should provide API to retrieve extension by OID. Yes! Can you open a github issue for that? -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c

by OID. Yun From: openssl-dev [mailto:openssl-dev-boun...@openssl.org] On Behalf Of Salz, Rich via openssl-dev Sent: 24 January 2018 14:40 To: openssl-dev@openssl.org Subject: Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c Create the OID at your

Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c

Create the OID at your program startup and store the NID in a global variable. From: Yun Jiang Reply-To: openssl-dev Date: Wednesday, January 24, 2018 at 7:38 AM To: openssl-dev Subject: Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c Thanks! The

Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c

On 01/23/2018 07:19 PM, Salz, Rich via openssl-dev wrote: > > * OpenSSL APIs, which makes the following OpenSSL documentation > statement invalid > (https://www.openssl.org/docs/man1.0.2/crypto/threads.html > >

Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c

January 2018 01:23 To: Salz, Rich ; openssl-dev@openssl.org Subject: Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c It's also not that much of a problem in practice.. If you are using those API's you are adding new crypto. methods. Doing t

Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c

Thanks! Is this issue fixed in 1.1.0? Yun From: openssl-dev [mailto:openssl-dev-boun...@openssl.org] On Behalf Of Salz, Rich via openssl-dev Sent: 24 January 2018 01:19 To: openssl-dev@openssl.org Subject: Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c

Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c

t;openssl-dev@openssl.org" Date: 24/01/2018 11:19 Subject: Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c Sent by:"openssl-dev" OpenSSL APIs, which makes the following OpenSSL documentation statement invalid (http

Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c

* OpenSSL APIs, which makes the following OpenSSL documentation statement invalid (https://www.openssl.org/docs/man1.0.2/crypto/threads.html

[openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c

The APIs defined in the file crypto/objects/obj_dat.c share some static global variables defined in the file without locking, which makes the APIs in this file not multi-thread safe even if the locking callbacks are set. In addition, the APIs in this file are also used by the other OpenSSL APIs,