Delphi XE7 - IPPeerClient

[imperyal]

Hello,

I installed Indy 17 on Delphi XE7 (version 21) because I need support for recent OpenSSL versions through IndyTLS-OpenSSL.

After updating Indy, my project no longer compiles and I get the following error:

[dcc32 Fatal Error] U_moloni.pas(8): F2051 Unit IPPeerClient was compiled with a different version of IdHash.TIdHashNativeAndIntF

While investigating, I noticed that Indy 17 does not seem to include the IPPeerClient unit, so I suspect there may be a compatibility issue between Indy 17 and Delphi XE7's existing IPPeer units, or perhaps I have a mixture of old and new DCUs/packages.

Could someone please clarify:

• Does Indy 17 require rebuilding any IPPeer-related units?
• Are there additional packages or steps required when upgrading from the Indy version shipped with XE7?
• Has anyone successfully used Indy 17 + IndyTLS-OpenSSL on XE7?

Any guidance would be greatly appreciated.

Thank you.

[rlebeau]

I installed Indy 17

There is no such thing as "Indy 17". What are you referring to, exactly?

on Delphi XE7 (version 21)

Why such an old version? It was released over a decade ago.

I need support for recent OpenSSL versions through IndyTLS-OpenSSL.

IndyTLS-OpenSSL is NOT officially released yet (did you not read the README?). It will be part of a future Indy 10.7 release.

But even then, IndyTLS-OpenSSL DOES NOT support recent OpenSSL versions! It even says so in the README. It's purpose is primarily to provide backwards compatibility for existing legacy user code, as the current OpenSSL code will be removed from the main Indy library in 10.7 and moved to IndyTLS-OpenSSL. MAYBE someday, Indy will update IndyTLS-OpenSSL to newer OpenSSL version, but that is TBD.

In the meantime, to use recent OpenSSL versions with the current Indy, you can use TaurusTLS instead. Except, I don't think it supports all the way back to XE7. So, you are going to have to either make up your own packages for XE7, or else upgrade your Delphi to a modern version.

After updating Indy, my project no longer compiles and I get the following error:

[dcc32 Fatal Error] U_moloni.pas(8): F2051 Unit IPPeerClient was compiled with a different version of IdHash.TIdHashNativeAndIntF

IPPeerClient is part of Embarcadero's technology, not Indy itself. It is an abstraction layer on top of Indy. Embarcadero's technology that uses Indy internally uses the Indy that is bundled with the IDE. They are supposed to use a private copy, but that doesn't always work out. So, if you replace the bundled Indy with an update, you risk breaking Embarcadero's stuff. Hence the error.

While investigating, I noticed that Indy 17 does not seem to include the IPPeerClient unit

Correct, because it is an Embarcadero unit, not an Indy unit.

Does Indy 17 require rebuilding any IPPeer-related units?

Yes, if you are replacing the Indy that is bundled with the IDE.

Are there additional packages or steps required when upgrading from the Indy version shipped with XE7?

Yes. Did you read the install instructions?

Has anyone successfully used Indy 17 + IndyTLS-OpenSSL on XE7?

No, because IndyTLS-OpenSSL is not finalized or released yet. And it will not solve your issue anyway.

[MWASoftware]

You've gone down the wrong path for using Indy with recent versions of OpenSSL.

Delphi XE7 comes with an old version of Indy but I would still start with using the version of Indy that comes with Delphi XE7. To this you should add a package such as TaurusTLS or IndySecOpenSSL - both available on Github. These add alternative components for OpenSSL support. By using these components instead of those provided with Indy, you can use the latest versions of OpenSSL.

It is possible that the Delphi XE7 version of Indy is too old to work with these addon packages. In which case you will need to replace the XE7 version of Indy with the latest version of Indy 10.6 from the IndySockets repo. But I would only do this unless you really have to.

[imperyal]

I meant Indy 10.7, my mistake. I was trying a quick fix by switching to the 10.7 branch and using IndyTLS-OpenSSL.

We still use XE7 only for this internal management application. It has not yet been migrated to a newer Delphi version due to time constraints, as the upgrade would also require changing the database engine we used back then. We use Delphi 13 for all our other projects.

Thank you, @rlebeau, for the explanation. I had assumed that IndyTLS-OpenSSL was intended to provide support for newer OpenSSL versions because of this statement in the README:

This has been split off from the main Indy library so it can be updated independently to the latest version of OpenSSL.

That line led me to believe it would support recent OpenSSL releases.

I will take a look at TaurusTLS and IndySecOpenSSL.
Thank you as well, @MWASoftware. I did try the IndySecOpenSSL repository, but I was unable to compile it under XE7. XE7 is indeed very old.

[rlebeau]

I meant Indy 10.7, my mistake. I was trying a quick fix by switching to the 10.7 branch and using IndyTLS-OpenSSL.

10.7 is not final yet. There are still changes pending for it. You need to go back to the main release. And as stated, IndyTLS-OpenSSL will not address your issue anyway.

I had assumed that IndyTLS-OpenSSL was intended to provide support for newer OpenSSL versions

That was the original plan, but that is not how life worked out.

because of this statement in the README:

I will have to re-write the README to make this clearer.