-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for OpenSSL up to 3.1.x #93
Support for OpenSSL up to 3.1.x #93
Conversation
This would actually be quite nice to have. However we tried this with your proposed change and openssl v3 and compilation went successful. However later on when we wantedto use the library, there were some linker errors, that some symbols had been defined multiple times. Honestly I doubt that this would be related to your updates, however I'm not sure. Check the jenkings output where we wanted to link the oss.tpm to one of our apps and use it for testing.
|
BIGNUM struct to version 3.0
@TrinityTonic it's difficult to be 100% sure what is going on with your build. However, if you look for the variables that are are reported as multiply defined, they are in the header file with an EXTERN macro :
And this EXTERN macro maps either to nothing or to the "extern" C keyword depending on whether the macro PLATFORM_DATA_C is defined.
So depending on how you build the TPM library, you will either have one, many or no definitions of these variables in your build of the TPM library. In your case, you seem to have either multiple definitions or at least one with another definition provided with the other components in your link so PLATFORM_DATA_C was defined in your build of the TPM library. I would try first to rebuild the library with PLATFORM_DATA_C undefined. It will either fix the problem (the variables are provided by another component of your build) or you will get an "undefined" or "missing definition" link error. If the latter, then your toolchain treats uninitialized global variables as common symbols (cf. the "Mac OS X build" of the README.md) https://github.com/microsoft/ms-tpm-20-ref/blob/main/README.md#mac-os-x-build and you will need to change your compiler/linker flags. I hope this helps. |
Now the ms-tpm-20-ref is not support openssl3.1.1, we need to add the patch, that is refer to the PR:microsoft/ms-tpm-20-ref#93 If the ms-tpm-20-ref done it, the commit need drop. Signed-off-by: Sun, Ceping <cepingx.sun@intel.com>
Now the ms-tpm-20-ref is not support openssl3.1.1, we need to add the patch, that is refer to the PR:microsoft/ms-tpm-20-ref#93 If the ms-tpm-20-ref done it, the commit need drop. Signed-off-by: Sun, Ceping <cepingx.sun@intel.com>
Now the ms-tpm-20-ref is not support openssl3.1.1, we need to add the patch, that is refer to the PR:microsoft/ms-tpm-20-ref#93 If the ms-tpm-20-ref done it, the commit need drop. Signed-off-by: Sun, Ceping <cepingx.sun@intel.com>
Refer to the PR:microsoft/ms-tpm-20-ref#93 If the PR was merged, this commit would be dropped. Signed-off-by: Sun, Ceping <cepingx.sun@intel.com>
Refer to the PR:microsoft/ms-tpm-20-ref#93 If the PR is merged, this commit will be dropped. Signed-off-by: Ceping Sun <cepingx.sun@intel.com>
Refer to the PR:microsoft/ms-tpm-20-ref#93 If the PR is merged, this commit will be dropped. Signed-off-by: Ceping Sun <cepingx.sun@intel.com>
Refer to the PR:microsoft/ms-tpm-20-ref#93 If the PR is merged, this commit will be dropped. Signed-off-by: Ceping Sun <cepingx.sun@intel.com>
Refer to the PR:microsoft/ms-tpm-20-ref#93 If the PR is merged, this commit will be dropped. Signed-off-by: Ceping Sun <cepingx.sun@intel.com>
Any plan to accept this PR? |
Our plan is to update this repo with the next public version of the code which is currently being worked on which has a similar change. |
Any estimated timeframe for this public release? |
No description provided.