Openssl mismatch with Let's Encrypt

[CaseyR]

Hi,

I am moving from Clarion 10/NT 10 to Clarion 11/NT 11.  I installed NT 11 into the Clarion 11 hierarchy.  For a few weeks, I have to continue with Clarion 10/NT 10.

Now everyday when my Clarion 10/NT 10 app does its Let's Encrypt certificate check, it generates a series of entry point not found errors for the openssl.exe.  These are caused because the app is somehow replacing the 2017 openssl.exe in the application folder with one dated 2018.  The 2017 exe is the in Clarion 10>Accessory>bin folder so it is just a quick copy to fix it for the day.

The application is compiled in Clarion 10/NT 10, but I have used a copy of it trying out Clarion 11/NT 11.   So where is the 2018 exe coming from?  Clarion 11>Accessory>bin? Some outside source? If the latter, will any maintenance release I issue also try to replace the 2017 exe with the one from 2018?

Many thanks.

[Bruce]

>> So where is the 2018 exe coming from?  Clarion 11>Accessory>bin?

yes, it's copied whenever you compile.

cheers
Bruce

[CaseyR]

Thanks, Bruce