Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 5 of 5 total
Thread SSL/TLS support is not compiled!
Wed, Apr 11 2018 8:13 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

I'm getting no response from elsewhere (well 1 reply on the emb ngs) so I'm hoping some clevr person here can help.

Its a weird one -I was trying to run my email server app on another PC to test 2.28. The comms is via Synapse.

This application works perfectly on my main notebook, ran for literally years on my server.

Both PCs are W7x64. I've placed a test project which will just logon to Gmail on to the problem PC and it bombs with "SSL/TLS support is not compiled!". Run the same app on my main PC and it works fine.

Just to make sure I'm running the exact same software I moved it onto a memory stick PC A fine, PC B bombs

I think it must be a Windows setting somewhere but I have no idea where. I did sort of think it could be the internet options but I've made sure they're the same and I still have the problem.

Any and all suggestions no matter how bizzare will be well received.


Roy Lambert
Wed, Apr 11 2018 9:02 AMPermanent Link

Raul

Team Elevate Team Elevate

On 4/11/2018 8:13 AM, Roy Lambert wrote:
> This application works perfectly on my main notebook, ran for literally years on my server.
> Both PCs are W7x64. I've placed a test project which will just logon to Gmail on to the problem PC and it bombs with "SSL/TLS support is not compiled!". Run the same app on my main PC and it works fine.

How exactly are you doing SSL/TLS - OpenSSL libraries or something else.

I'm not familiar enough with Synapse so these are generic.

My first guess would be missing or wrong versions of DLLs (libeay32 and
ssleay32).

If it's using OS crypto layer instead then making sure PCs are same
patch levels etc as crypto is something MS has patched in the past few
years quite a bit (mostly to add new TLS 1.x support).

Assuming connection uses TLS 1.2 then i think that is by default
disabled on anything less than windows 8 so you should google the
settings for Win 7.

Quick google found this sample article but not sure if it's best source

https://blogs.msdn.microsoft.com/kaushal/2011/10/02/support-for-ssltls-protocols-on-windows/


Raul
Thu, Apr 12 2018 4:23 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Raul


I'm using libeay32.dll and libssl32.dll.

I'll read through the link you supplied. A quick glance supported my thoughts on internet options so hopefully I'll find the bit I'm missing in there somewhere.


Roy Lambert
Thu, Apr 12 2018 10:16 AMPermanent Link

Raul

Team Elevate Team Elevate

On 4/12/2018 4:23 AM, Roy Lambert wrote:
> I'm using libeay32.dll and libssl32.dll.

Then you are using the OpenSSL and not windows crypto so the link does
not really apply.

First thing i would look for is whether you have any other copies of
those DLLs on that computer that your app tries to load.

I do not know Synapse specifically but for example Indy by default loads
these from system path and not local folder (you need to specifically
override it to use local folder).


Raul
Thu, Apr 12 2018 10:46 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Raul

>First thing i would look for is whether you have any other copies of
>those DLLs on that computer that your app tries to load.

Nice to see your mind works the same way as mine. Unfortunately, whilst there are other copies (eg MalwareBytes) and all different number of bytes non of them are on the system path

>I do not know Synapse specifically but for example Indy by default loads
>these from system path and not local folder (you need to specifically
>override it to use local folder).

The libraries are loaded in the same way as other dlls - which I think means it looks locally first.

Thanks for trying to help - this is driving me round the bend.

Roy
Image