[EXTERNAL] Re: OSSL_PROVIDER reference issue

[kgoudra at ups.com]

Hi,

No, I am not defining OPENSSL_API_COMPAT anywhere and OPENSSL_CONFIGURED_API in include/openssl/configuration.h is,

# define OPENSSL_CONFIGURED_API 30000

Thanks

-----Original Message-----
From: openssl-users <openssl-users-bounces at openssl.org> On Behalf Of Matt Caswell
Sent: Monday, August 7, 2023 3:49 AM
To: openssl-users at openssl.org
Subject: Re: [EXTERNAL] Re: OSSL_PROVIDER reference issue

Note: Please post to openssl-users - not to me directly.

On 07/08/2023 10:20, kgoudra at ups.com wrote:
> If I try to specify specific types.h (#include "openssl/types.h") in source file then below error is observed.
> 
> /usr/include/openssl/macros.h:155:4: error: #error "OPENSSL_API_COMPAT expresses an impossible API compatibility level"
>   #  error "OPENSSL_API_COMPAT expresses an impossible API compatibility level"
>      ^~~~~
> 

That comes from this code in the header file:

/* Below 0.9.8 is unacceptably low */
# if OPENSSL_API_LEVEL < 908
#  error "OPENSSL_API_COMPAT expresses an impossible API compatibility level"
# endif

So, for some reason, it believes you are attempting to get compatibility with OpenSSL API before 0.9.8.

Do you define the OPENSSL_API_COMPAT macro anywhere - and if so with what value?

What is the value of OPENSSL_CONFIGURED_API in include/openssl/configuration.h?

This looks like an environmental issue somewhere


Matt


> -----Original Message-----
> From: Kirtikumar Goudra
> Sent: Monday, August 7, 2023 3:15 AM
> To: Matt Caswell <matt at openssl.org>
> Subject: RE: [EXTERNAL] Re: OSSL_PROVIDER reference issue
> 
> All the 3.0.8 available headers present in include/openssl directory 
> like types.h, provider.h etc
> 
> -----Original Message-----
> From: openssl-users <openssl-users-bounces at openssl.org> On Behalf Of 
> Matt Caswell
> Sent: Monday, August 7, 2023 3:08 AM
> To: openssl-users at openssl.org
> Subject: [EXTERNAL] Re: OSSL_PROVIDER reference issue
> 
> CAUTION! This email originated outside of the organization. Please do not open attachments or click links from an unknown or suspicious origin.
> 
> ======================================================================
> What OpenSSL header files are you including in your application?
> 
> Matt
> 
> On 07/08/2023 08:40, Kirtikumar via openssl-users wrote:
>> Using Openssl-3.0.8 version and my application is built with 3.0.8 
>> headers only.
>>
>> Please share any inputs which help to solve this issue.
>>
>> *From:* Kirtikumar Goudra
>> *Sent:* Sunday, August 6, 2023 11:10 PM
>> *To:* openssl-users at openssl.org
>> *Subject:* OSSL_PROVIDER reference issue
>>
>> Hello Team,
>>
>> We are getting below error specifically in linux RHEL8 environment 
>> and the same is working perfect on windows.
>>
>> error: ‘OSSL_PROVIDER’ does not name a type; did you mean ‘SSL_TXT_IDEA’?
>>
>>     static OSSL_PROVIDER *legacy;
>>
>>            ^~~~~~~~~~~~~
>>
>>            SSL_TXT_IDEA
>>
>> error: ‘OSSL_PROVIDER’ does not name a type; did you mean ‘SSL_TXT_IDEA’?
>>
>>     static OSSL_PROVIDER *deflt;
>>
>> Code is as below:
>>
>>                   static OSSL_PROVIDER *legacy;
>>
>>                   static OSSL_PROVIDER *deflt;
>>
>> Trying to use them as below:
>>
>>                   OSSL_PROVIDER * SSLSocket::legacy;
>>
>>                   OSSL_PROVIDER * SSLSocket::deflt;
>>
>> We are trying to use provider functionalities like
>> OSSL_PROVIDER_load() and OSSL_PROVIDER_unload() in our app and only 
>> on linux it is not able to reference although we have included openssl headers.
>>
>> Please suggest what could be the problem here?
>>
>> Thanks,
>>
>> Kirtikumar
>>