• Registered: 2012-02-23
  • Posts: 19

Topic: wolfSSL 2.2.0 names clash in ssl.h

I have successfully compiled and linked wolfSSL 2.2.0 to my project, but lines 421 and 422 of ssl.h do not compile.

The following two identifiers within an anonymous enum object...
OCSP_REQUEST  = 4,
OCSP_RESPONSE = 8,

...clash with these #define's in WinCrypt.h
#define OCSP_REQUEST                        ((LPCSTR) 66)
#define OCSP_RESPONSE                       ((LPCSTR) 67)

My question: Is this a bug in my code or does the wolfSSL API include WinCrypt.h somewhere and thus a bug in wolfSSL?

Share

  • From: Bozeman, MT
  • Registered: 2010-10-20
  • Posts: 650

Re: wolfSSL 2.2.0 names clash in ssl.h

Hi Philhippus,

This was a bug in wolfSSL which we recently fixed in our GitHub repository.  Please reference the most current version of ./cyassl/ssl.h on GitHub as well as the following commits for details:

https://github.com/cyassl/cyassl/commit … 8909647443
https://github.com/cyassl/cyassl/commit … bd4cca15d8

Please let me know if you're still seeing problems after trying this.

Best Regards,
Chris

https://www.wolfssl.com

chrisc's Website

Share

  • Registered: 2012-02-23
  • Posts: 19

Re: wolfSSL 2.2.0 names clash in ssl.h

Hi Chris,

Glad you guys are aware of that. Fyi I downloaded wolfSSL 2.2.0 from the product download page of this website only 2 days ago and this bug was in that package.

Thanks
p

Share

  • From: Bozeman, MT
  • Registered: 2010-10-20
  • Posts: 650

Re: wolfSSL 2.2.0 names clash in ssl.h

The changes we've made to the wolfSSL GitHub repository post-2.2.0 won't roll into a stable release on our download page until the next stable release of wolfSSL embedded ssl.  We usually put out fairly frequent releases of wolfSSL, so it shouldn't be too long before the fix rolls into a stable release.

Best Regards,
Chris

https://www.wolfssl.com

chrisc's Website

Share